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.
"Issue linking has enabled teams to trace issues."
"The monitoring, flexibility and tracking are really good in Jira."
"I think one of the most powerful features in Jira is the customization of fields and workflow."
"There are a couple of things that I find valuable about Jira, the first being its architecture. For instance, I like that you can create dashboards easily, which makes it very user-friendly. You don't need much training on that. You can just get right to it and people are able to use almost all of Jira's features with little training."
"The product's initial setup phase was straightforward."
"Scaling the product wouldn't be difficult."
"All departments can work with the same platform."
"JIRA's technical support is absolutely fantabulous. I had used it in the past when I was working at my previous organization. And when we wanted to link it with a framework, they helped us out with the API we were looking for."
"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."
"There are a lot of helpful features available for tracking dependencies."
"I like the fact that there is built-in Power BI. Both are Microsoft tools. So, you can incorporate dashboard capabilities."
"It is stable, and we have had no issues with it."
"Our technical sales staff and business development people need to know how far the developers are on any product that we're developing. DevOps makes it easier for you to see how far along they are with the work because they have a repository where they store everything. There is a portal where you can see what has been done, what has been tested, what is working, and what isn't. I have a huge dashboard with an overview of what the development team is doing from an executive point of view."
"Provides us with user histories."
"My team likes the integration that Microsoft Azure DevOps has with GitHub and Microsoft Teams. The solution is well integrated with other Microsoft tools in one place, it is very good."
"The product is easy to use and very stable."
"The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes."
"Some of the customizations are definitely a little challenging."
"I find the dashboard to be Jira's most problematic feature."
"The thing I don't like is that it is hard to decide which dropdown options should be selected. When we try and submit it, it will state that there are certain mandates in place. It won't allow us to submit the form unless we fill out all the details."
"I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it."
"In general, although we use JIRA, we never really learned how to use it properly. The learning curve of the solution is high. It has a lot of power, and yet we don't understand its capabilities."
"The history with Jira is that it is a bit complex for many users."
"The reporting needs to be improved."
"At times, our development work encounters issues, particularly when executing numerous CI/CD processes."
"They have to add more features such as schedules and more flexibility in the platform."
"I can't think of anything I would like to improve, since I don't have complete knowledge of the platform yet. I'm sure that as I gain more experience, I will understand it better. The price could maybe be cheaper, but I'm sure I'll have more ideas as to improvements and additional features once I've used it more."
"The UI, the user experience, is challenging for newcomers."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
"The solution can improve by adding integration with on-premise tools. The only built-in repository options are GitHub and DevOps."
"Not all companies use the same methodology which could limit the use of this solution."
"Its price can also be reduced. It would be great if they are a little bit more competitive in terms of pricing because many open-source products are currently available in the market."
Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 259 reviews while Microsoft Azure DevOps is ranked 1st in Application Lifecycle Management (ALM) Suites with 124 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 "Good support, helpful management capabilities, and great Kanban boards". 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.