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.
"Its integration with Bitbucket, Confluence, and other things is most valuable."
"There are a lot of plugins in Jira and we purchase the ones we need."
"The task management aspect of Jira is pretty pure. They have a lot of great plugins that really expand your options."
"What I find valuable about Jira is that it's an ecosystem. Sometimes, it does not provide the best in class solutions, but it's so well integrated. You will not have many problems with integration."
"Jira as a structure has Confluence for documentation, and for what it is offering it is a strong suit with Atlassian."
"The product's initial setup phase is easy."
"The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components."
"The timeline management is great."
"The simplicity and ease of use are two features that we have found to be most valuable."
"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."
"The solution integrates well with other Azure services and third-party tools."
"If someone is considering developing and deploying the infrastructure in this solution, then using this tool is perfect because it's fully integrated with the pipelines and with a server core repository."
"Two of the most valuable features include the integrated project management suite, which consolidates source code and project management in a single location, and its powerful reporting capabilities."
"We are able to generate many different types of reports from Azure."
"Monitoring is most valuable."
"Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development."
"I would like to have a future-proof idea of the cost and the roadmap for my class."
"There needs to be more integration and connectivity."
"The performance and stability are visibly degrading since the database has been growing every year."
"It lacks features to cover all testing aspects, so we often integrate it with other plugins or tools like X-ray."
"I'd like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile."
"Ease of administration and customization. It is really clunky in this area."
"If I'm comparing it to ALM Octane, the documentation is not as robust as ALM Octane's documentation. So, they can improve on the documentation side."
"The CACD solutions on JIRA has some plugins, but they are not easily understandable or workable."
"Improving the metrics that are readily available on the dashboard would be very helpful."
"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."
"One thing I would note is that it's hard to know what is included or not in the product. Especially when you begin to try and compare it to other solutions. When you go to a site like VersionOne, they tell you Azure DevOps doesn't have this or that, and when you go to Microsoft, it says VersionOne doesn't have this or that. They could do a better job of laying out exactly what is on offer so customers know going in exactly what they'll get."
"One potential enhancement in Azure DevOps could be integrating more customizable reporting features, particularly for Power BI integration."
"It should be easier to manage Licenses especially because it's in the cloud."
"This product would be improved if the helpdesk were included."
"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."
"Incorporating security tools directly into DevOps is crucial, as many existing DevOps solutions lack robust security features."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 reviews while Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 127 reviews. Jira is rated 8.2, while Microsoft Azure DevOps is rated 8.2. The top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". On the other hand, the top reviewer of Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". Jira is most compared with IBM Rational DOORS, OpenText ALM Octane, Rally Software, Polarion ALM and TFS, whereas Microsoft Azure DevOps is most compared with GitLab, TFS, Rally Software, ServiceNow Strategic Portfolio Management and OpenText ALM / Quality Center. 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.
