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 customization and tailoring of the workflows have proven to be very useful."
"The solution offers up great transparency that makes it possible for everyone inside the departmental organization to see what's happening."
"It's a Scrum tool, so it's very easy to use."
"The most valuable feature is managing software development."
"Being able to automatize the deployment of the solution has been great."
"The most valuable feature is that it has different APIs available, with good services, and it is completely by the books."
"The UI is good. It's simple and not very complicated. It's very good for tracking."
"I like seeing which tickets are open and what our response rate is. They have a lot of good metrics in their system to see what's going on."
"Overall, so far we have no major issues to report."
"It's very user-friendly, and the documentation is good. The most valuable feature is backlog item creation, where we pick features and other things. The burndown chart created for projects to be maintained by the development teams is also useful."
"Some of the valuable features are the interface and the workflows are easy to learn and to manage."
"The most valuable feature is the ease of use and performance."
"The creation of test plans is valuable and I like the reporting features."
"It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues."
"Great project management feature and Git-based repository."
"The most valuable feature is that it's fully integrated, where we have a single place to do everything that we need."
"The user interface and views on different devices should be improved."
"The integration of Jira could improve. The solution should be able to integrate easily with other solutions, such as ERPs. There are times the solution can be slow and we have to reset it over and over again."
"They can maybe dumb down the directions for building the automation a little bit because to be able to build out the automation, I had to play around with it and learn what all the fields meant and what they were referencing. I don't have an IT background originally. My background is in biology, and I got into project management by chance. I am good at it, but I haven't really worked with coding languages. In terms of writing automation, it is easier for devs because they intuitively know what they're being asked, but as a PM who originally didn't have IT experience, it was a little bit daunting at first. It could also have an extra hierarchy to be able to allow tasks under stories. It could be the way it is set up at our organization, but currently, under stories, you can have sub-tasks, but you can't create a task. Being able to customize your hierarchy a little bit more would be beneficial because sometimes, the devs would say, "Well, here's a story, and now we need sub-tasks," but as we were building out the sub-tasks, sometimes we had to go a step lower to dig in a little bit more, and we couldn't do that."
"The biggest complaint industry-wide about JIRA is they need to purchase additional extensions, such as reporting automation. If they could provide some additional extensions from the initial purchase it would be a huge benefit."
"Grid: It is really strange that there is no possibility to edit an item in the grid. You need to go inside, and even then, not all items are editable, so you need to switch to edit mode. That's too many clicks and switches."
"Lacks some common building block approaches to certain things."
"End-to-end management from product backlog to test completion could be improved."
"The pricing is quite high."
"Microsoft Azure DevOps could improve by having better integration with other email servers."
"Not all companies use the same methodology which could limit the use of this solution."
"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."
"With Microsoft, I would prefer to have more test plans. It's very difficult to find individual test plan module training."
"When we don't have some permissions, we have to research how to get them."
"Its testing features are limited and can be improved a little more. They should provide more options from the testing and build perspective. Currently, we have to use a third-party product for testing. It would be great if it has more than one testing tool."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
"It would be great if I could integrate with a human resource type of software that could control timesheets."
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.