We performed a comparison between Jira and Microsoft Azure Devops based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Overall, users of both products seem to be satisfied with the solutions. Microsoft Azure Devops has slightly higher ratings because it is easy to deploy.
"It also works well with all the integrated tools that you buy."
"The UI is good. It's simple and not very complicated. It's very good for tracking."
"This product provides you a good view of the status of your projects."
"We like team collaboration and cross-functional collaboration."
"The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily."
"It is very configurable, and we can do whatever we want. Jira dashboards are also good, and we use them extensively. We also use the tracking mechanism extensively."
"The solution is stable and reliable."
"You no longer need to email people. You can mention them right in Jira and have conversations there."
"The simplicity and ease of use are two features that we have found to be most valuable."
"It is stable. I like Azure a lot. All our guys are Microsoft certified."
"It's a great product for the CI/CD process."
"I like the fact that there is built-in Power BI. Both are Microsoft tools. So, you can incorporate dashboard capabilities."
"Some of the valuable features are the interface and the workflows are easy to learn and to manage."
"It has a good GUI, and it's very user-friendly."
"Azure Pipeline and Azure Release are most valuable. I use Azure DevOps through pipeline and release."
"Some of the most valuable features are the ease of use and the ability to monitor a lot of things. It has a lot of applications and facilities that meet all the developers' requirements. For example, we can use application insights to get an idea of our application's performance. Since it's cloud-based, it's really good for collaboration and working as a team."
"Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon."
"There needs to be more integration and connectivity."
"If you're not a technical person, it might not be very user-friendly."
"The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes."
"Jira is a project management tracking tool, and it would be great to see integration with the source front or Azure DevOps, etc."
"The solution could be more user-friendly."
"Could be more stable with more integrations."
"Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira."
"Reporting could be better. We would like to see how many applications are onboarded in DevOps and in which phase they are. We would like to know for how many applications we have done only the repository, but we have not yet done the build pipeline or deploy pipeline. Currently, there is no such report. We have to figure it out ourselves. There is no way to check how many applications are completing their build pipelines, how many applications are completing their deploy pipeline, how many are ready to use, and how many pipelines are working."
"The UI could be improved."
"The tool was developed for Agile project methodology, but I've noticed that there has also been a try to incorporate what is typically done in MS Project, which is for more sequential Waterfall projects. The problem with that is that it is half-baked for Waterfall projects. If you're going to do it, then either go all the way and allow us to use the tool for both or don't do it at all."
"The UI, the user experience, is challenging for newcomers."
"I can't think of any specific things at the moment, but I've run into things that I didn't like. I came across something that I wanted to be changed in DevOps, but I can't remember what it was. It was a particular feature I was looking for that I couldn't find."
"I think Azure DevOps could improve the traceability or business intelligence about the execution of DevOps processes."
"I would like to see improvement in the metrics and the dependencies."
"When you compare with Jira, there is a lack of progress features."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 131 reviews while Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 76 reviews. Jira is rated 8.0, while Microsoft Azure DevOps is rated 8.2. The top reviewer of Jira writes "Great for collaboration, very stable, and extracting data is straightforward". On the other hand, the top reviewer of Microsoft Azure DevOps writes "Robust functionality, good integration, continually enhanced, and easy to scale". Jira is most compared with Micro Focus ALM Octane, IBM Rational DOORS, Polarion ALM, Rally Software and TFS, whereas Microsoft Azure DevOps is most compared with GitLab, TFS, ServiceNow Strategic Portfolio Management, Rally Software and Red Hat Ansible Automation Platform. See our Jira vs. Microsoft Azure DevOps report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
