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.
"The most valuable feature is working with sprints and having the ability to create sprints."
"The initial setup isn't too complicated."
"Jira is flexible and accessible for the end-user. It lets users track their requests. The look and feel are good for our purposes."
"It is a complete solution. It has more features as compared to other tools, especially the open-source one that we use. It is also easy to administer."
"Being able to automatize the deployment of the solution has been great."
"We use Jira mostly for task coordination and assignment. Additionally, scrum methodologies defined work items and bug issues. If we create any bugs all of them are fixed."
"There are many good things about Atlassian."
"Overall, the solution is very nice and has a variety of great features."
"You get a complete solution with Azure DevOps. You can do everything in one place, starting from requirement gathering until you release the product. It is a reliable, scalable, and handy product."
"Setting up Azure DevOps was straightforward. It's easy to use the default templates. Everything is under our control, so it's simple to implement new requirements."
"Overall, so far we have no major issues to report."
"We can eliminate some of the middleman processes."
"What I like the most about this product is that it's free and it's secure."
"The extensibility of the work item forms and customizations as well as the backend API to query the data, et cetera, and manipulate the data programmatically are all very valuable aspects of the product."
"It has a good GUI, and it's very user-friendly."
"The reports have been most valuable. We have created some dashboards allowing us to be able to check our teams, their progress, and mission plans."
"Jira is raising their prices for the license, which is like a trap because many other providers offer services like Jira but for much cheaper."
"One thing that I don't like about Jira is that when you do an export, it only allows a thousand issues. So the export feature needs to be better."
"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."
"I would like to see more robust release management within the tool."
"We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product."
"There's a really steep learning curve for configuration."
"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."
"There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported."
"Project management could be improved."
"Not all companies use the same methodology which could limit the use of this solution."
"I'd like to have something better for the test plan."
"Being more technology-agnostic through ease of integration would be beneficial."
"Definitely, there should be more integration between GitHub and Azure DevOps."
"The testing environment and different pipelining concepts can be improved."
"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."
"As for improvement, the first one is pricing. For us, luckily because we are partners, it's free. Microsoft gold partners do not have to pay, but if you're not a partner, the product is very expensive."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 162 reviews while Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 93 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, Polarion ALM and Rally Software, 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.
