Try our new research platform with insights from 80,000+ expert users

Jira vs Microsoft Azure DevOps comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 8, 2024
 

Categories and Ranking

Jira
Ranking in Application Lifecycle Management (ALM) Suites
1st
Average Rating
8.0
Number of Reviews
266
Ranking in other categories
Application Requirements Management (2nd), Project Management Software (4th)
Microsoft Azure DevOps
Ranking in Application Lifecycle Management (ALM) Suites
2nd
Average Rating
8.2
Number of Reviews
130
Ranking in other categories
Release Automation (1st), Enterprise Agile Planning Tools (1st)
 

Mindshare comparison

As of November 2024, in the Application Lifecycle Management (ALM) Suites category, the mindshare of Jira is 23.5%, down from 23.9% compared to the previous year. The mindshare of Microsoft Azure DevOps is 21.8%, down from 26.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

Saroj Ekka - PeerSpot reviewer
Apr 10, 2024
Offers good repository integration, sprint board and easy to set up
There are some features and reports we need that are not there. For example, if I have to find out the capacity of the current sprint by user and compare it with the previous sprint, that visibility isn't there. We can know the capacity and what happened with the whole sprint, but not for an individual person to see where it's falling and how it's tracking. Report and analytics capabilities are important for a product manager. That visibility is important, so we use Jira. Some of the features are there, and I use my own Excels or other data things to compensate for that.
Akshat Prakash - PeerSpot reviewer
Apr 10, 2024
Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling
My company has experienced benefits from using it or from recent updates in Azure Pipelines. For instance, we can manage different code versions from the same repository across different environments. We also use feature flags; the code is deployed, but the feature can be made visible to the end user at a later time. Additionally, as part of the deployment, we integrate automated and regression testing, which stops the deployment if testing fails, thus preventing regression bugs. This saves time and increases productivity by reducing the need for manual testing. Lastly, it integrates with the project management aspects, allowing us to link code deployments with project milestones. Azure DevOps supported our shift towards DevOps culture or practices. We shifted to the cloud environment and started migrating from our data centers about eight or nine years back. It has been a long journey. However, we have used Azure DevOps for almost five to six years in every project. We also use automation testing in Azure, so we have an integrated test suite that allows us to perform functional and regression testing effectively via the Azure DevOps system.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It allows you to do a lot of stuff, and the functionality is pretty rich. It integrates well with other products, like GitLab, that we are currently intensely using at the company."
"Jira can track projects, time management of assignments, and keep everything on schedule. The performance of the solution is good."
"It is user-friendly, and you can manage your project according to the methodology you want. It is also easy to configure."
"Jira's collaborative features, such as comments, notifications, and real-time updates, facilitate better communication."
"I'm working in the IT department, and the ticketing system is the most important service for us. We are also using some automation add-ons. It a very good product for handling tickets and tasks and managing processes. It is also very useful and easy to use."
"The task management aspect of Jira is pretty pure. They have a lot of great plugins that really expand your options."
"The solution is easy to use and user-friendly."
"The most valuable feature is its flexibility."
"It's got something that you won't find in other products."
"The pricing seems to be reasonable."
"The features that have a significant impact on us include CI/CD, where we have full integration with the source code repository and Azure Pipelines."
"Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting."
"Azure DevOps is effective for repository management and code collaboration. We can create branches, differentiate between code versions, save and review code later, get PR approvals, and more. All these features are valuable."
"The build and release management features are valuable."
"The solution is easy to implement and easy to use."
"There are great automation tools."
 

Cons

"The only thing that JIRA doesn't for us is release management in a way that I can create a list of versions easily."
"There are no fields to search or to filter by, mainly the ones which use a data around a date and time when something changes."
"We're doing PI planning, Program Increment planning, and that kind of stuff, and it's not always a good facilitator for that. We tend to pull it out and put it into other tools to manage that, and then we get it back into Jira as that's our system of record for where all the stories are kept. That's probably the biggest headache with it."
"From a very software-centric or a lead developer standpoint, there should be the ability to work at multiple levels. You have epic stories and use cases or epic stories and tasks. It would be nice to be able to have multiple levels of stories and multiple levels of epics work with it. It's lacking a little bit there, and this is the big thing for me because it makes it difficult to do a real sprint when you're limited to one story per epic. It's really hard to isolate tasks at multiple levels to match the type of use cases you normally do. That's the biggest difficulty. Other than that, they've been improving year to year, and every version seems to have a level of improvement."
"I would like to see more integration available with more tools."
"Once the solution is deployed, it's not easy to configure."
"Backlog pruning and visualization are poor."
"It would be ideal if Jira had future functionalities to integrate more easily with various aspects of code reviews."
"Some things like project management, tasks, progress, and having work progress views require us to use some external tools, or to create our own internal tools. These are not native to DevOps. It would be ideal if, instead of searching for third-party solutions, they had these feature sets or capabilities included under DevOps."
"The administrative capabilities of the tool need a huge improvement. Its Wiki and reporting also need a lot of improvement. Their support can also be better."
"I think that the integration is to some extent, immature."
"Right now, they tend to have a limit of 1,000 tasks per sprint, and some of their web-based boards, such as the Kanban boards, no longer display tasks. Once you hit over a certain number of task limits, you need to increase those limits."
"Proper Gantt charting should be a feature that is included because as it is now, we have to create it ourselves."
"Microsoft Azure DevOps could improve by providing better integration with other tools. It is very easy to integrate with Azure, but when you need to integrate with other solutions, such as Amazon Web Services, is difficult."
"The communication could work better, especially for the development team."
"The only downside is that the deployment could be a little challenging but it is manageable."
 

Pricing and Cost Advice

"The cost is about $10 per user, per month."
"If I compare Jira's licensing model with that of other products, I think that the other products have a much better licensing model."
"Its price is fine, but we would like it to be less expensive. We are paying on a yearly basis."
"There is a monthly license required for this solution and it is expensive."
"It depends on the type of license. In terms of subscription, it is cheap, and it works pretty well."
"Worth the extra cost."
"The tool is expensive."
"It is subscription-based, and we probably pay yearly. I would rate it a four out of five in terms of price."
"We pay a monthly license for Microsoft Azure DevOps."
"For the basic license, it is around five euros per month."
"The price is reasonable, but of course, you can find others that are cheaper such as Atlassian."
"It has an annual subscription. It can be cheaper for partners. Many open-source products are available in the market, and it would be great if they can be a little bit more competitive in terms of pricing. A lot of startups are looking for an open-source, free, or cheap solution. If they can accommodate such requirements, it will be good for the product in the long run."
"Compared to other tools, Microsoft Azure DevOps is a cheap solution."
"For Microsoft, it can get expensive when you need heavy-duty machines."
"The main agile features are very expensive."
"This product could maybe be cheaper. My organization handled licensing, so I'm not aware of which subscription they have."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
815,854 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
50%
Manufacturing Company
8%
Financial Services Firm
7%
Computer Software Company
6%
Manufacturing Company
13%
Computer Software Company
12%
Financial Services Firm
12%
Government
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Is Jira better or would you go with Micro Focus ALM Octane?
Hi Netanya, Basically , it all depends on the use cases for your environment and the business needs. Hope the below data may be relevant to you for identifying your needs and deciding on the approp...
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
What is your experience regarding pricing and costs for Jira?
The product is quite expensive. It costs approximately 1.2 million rand per year. It's a fixed price, depending on the modules that you get. You have specific tools, that's what you pay for. I rate...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
What do you like most about Microsoft Azure DevOps?
Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check-in/check-out activity, and developer/tester productivity.
 

Also Known As

Jira Software
Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
 

Overview

 

Sample Customers

Square, Nasa, eBay, Cisco, SalesForce, Adobe, BNP Paribas, BMW and LinkedIn, Pfizer, Citi.
Alaska Airlines, Iberia Airlines, Columbia, Skype
Find out what your peers are saying about Jira vs. Microsoft Azure DevOps and other solutions. Updated: October 2024.
815,854 professionals have used our research since 2012.