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 of Jira is the project package for development."
"It is easy to integrate Jira within our current IT environment. Jira has connectors and supports various integration."
"The way we can define and customize the search queries for the tickets in Jira is most valuable."
"In our organization, we use Jira for project management and usually use the Scrum project type. We might adjust the workflows and stages to better suit our needs, but we mostly use the default functionalities it offers to manage our projects."
"The ability to design your own workflows is a great feature."
"The solution offers a lot of plugins."
"I think one of the most powerful features in Jira is the customization of fields and workflow."
"The most valuable features of Jira are the dashboards and user interface. The processes within Jira to monitor, maintain and release are beneficial. It is a continuous development solution."
"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."
"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."
"The product is easy to use...It is a stable solution."
"The integration of the whole cycle is the main strength of the tool. If I want to control the cycle with other tools on the market, I would have to use several tools. However, this is not the case with Azure DevOps or TFS."
"What I like the most is the DevOps Boards. It's easy to create a hierarchical project structure, assign tasks to people, and to track their tasks."
"Some of the valuable features are the interface and the workflows are easy to learn and to manage."
"The most valuable aspect of Azure DevOps for me is its robust version control functionality, which is critical for our workflow."
"The most valuable feature is that we can run integrations with DevOps. From a QA perspective and a testing perspective, we can run those tests and integrate automation tools. Then we can run those tests as part of the deployment process. Every time we are deploying something, it automatically runs all the tests."
"The user interface and views on different devices should be improved."
"I'd like the solution to be more secure."
"Some of the interfaces, especially on the administrator side and for permissions, are not so clear. They aren't very user-friendly."
"This solution would be improved with the inclusion of integration with SVN, and auto-sync with the build release number."
"The integration could be better in Jira."
"It would be very useful to have drag and drop time tracking."
"Jira could improve by making the user interface easier to use and the functionality could be better. While we are managing multiple sprints and other elements of the projects, it's very difficult to manage the labels and other aspects."
"We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product."
"It would be very useful if it had better integration with Microsoft Word because we would like to be able to define the priority requirement document and add it to different stages of the backlog."
"As for room for improvement, more features need to be added to the classic pipeline. The build and release pipelines are present, but there has not been much improvement there."
"We would like some bidirectional synchronization. It's the requirement if you want to analyze it to software requirements, et cetera. That's something that most of the tools aren't that good at."
"When you compare with Jira, there is a lack of progress features."
"There are certain features, and reporting that can only be used in PowerBI, but not directly in DevOps."
"Some of the queries, the way they're built, need to be looked at. We need better query tools."
"The tutorials for building pipelines are an area that is a bit technical for a beginner."
"I would like to see DevOps have the ability to give us something with a compatibility or traceability matrix."
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.