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.
"In terms of scrum teams, I find that usually, the product backlog depends on charts and especially reports like Sprint Reports. I find the reports to be very useful."
"You no longer need to email people. You can mention them right in Jira and have conversations there."
"I feel the strongest feature of Jira is its workflow engine. It helps us automate our workflows within our organization. It's the one characteristic of Jira which I think can help any organization, be it in any domain."
"The timeline management is great."
"The links between tickets are very valuable and the boards I found to be configurable and usable. The boards allow some level of extended configuration and they can be customized according to our project needs. Additionally, it is easy to use."
"All of the tracking features are the most valuable because it allows me to see where we stand today and every day."
"We have around 2000 plus users, so scale wise, there are no issues. We can easily scale up with multiple users."
"It's easy to deploy."
"Provides us with user histories."
"I like the cloud infrastructure of Microsoft Azure DevOps."
"Provides agile management of projects."
"It's a complete solution that has everything you need."
"Most developers and project managers choose the Microsoft tools to begin with because of familiarity, and these new tools are almost an extension of the tools you're already familiar with. There's a lot of knowledge transfer, which helps, rather than bringing in a new product line."
"This platform provides a large span of tools and technologies."
"Microsoft Azure DevOps integrates well with other components, such as Synapse, which is a data warehouse tool of Azure. It is a framework platform for BI and integrated with other tools, such as Power BI."
"We are able to generate many different types of reports from Azure."
"Because I am a developer, I would like integration with Git Source Code Management so that for tickets, we can reference the code where the change has happened and where the issue is. This feature might be there, and I probably haven't discovered it."
"The reporting part is a little bit difficult for me. It is not so easy. There should be a simpler way to track the efforts of our team. For example, in an Excel sheet, there is a feature for filtering. It would be much better if we can use something like that. Currently, for a complex query, we need to use Jira Query Language. Using Jira Query Language every time is not efficient for me."
"In terms of the general Jira software, one element that is missing is budget management. Perhaps such functionality exists in add-ons, however."
"Stability is an area of concern and it needs improvement, otherwise, it's a good product."
"If you're not a technical person, it might not be very user-friendly."
"If Jira would be interested in offering a SharePoint version, it would be beneficial."
"I don't know if it's the way it's deployed in the organization, but the interface we are provided is not as customizable as other tools. The multi-language report is not enabled in our installation. I don't really know if it's something related to the tool or our installation."
"Jira can improve by making user management better. It is not easy to have visibility of who has the right to do what. Only the administrator has this visibility but there should be the option for other users too."
"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."
"Not all companies use the same methodology which could limit the use of this solution."
"The tool has a logical link between epic feature, user story, and task, but when you try to generate a report to show the delivery progress against a feature, it is not easy. To see the percentage completion for a feature or progress of any delivery, it is not easy to draw a report."
"Azure has not yet advanced to the performance level of the other major competitors and is missing integration with important technologies."
"I would like to see a bit more project tracking."
"Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials."
"I think that the integration is to some extent, immature."
"The UI, the user experience, is challenging for newcomers."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 165 reviews while Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 94 reviews. Jira is rated 8.0, while Microsoft Azure DevOps is rated 8.0. 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, TFS, Rally Software and Polarion ALM, whereas Microsoft Azure DevOps is most compared with GitLab, TFS, ServiceNow IT Business Management, Red Hat Ansible Automation Platform and Rally Software. 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.
