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.
"Kanban boards are most valuable"
"Scaling the product wouldn't be difficult."
"Jira's collaborative features, such as comments, notifications, and real-time updates, facilitate better communication."
"Overall, it is very intuitive. It is so lightweight and easy to use. It is easy to manage our product backlog and user stories, and it produces great reports."
"Jira is designed for issue tracking, making the process much easier than traditional methods like paper-based tracking. It is number one for agile management."
"Integrates with other components."
"When combining Jira with Bitbucket, you have the possibility to ensure continuous integration and other functions which is highly appreciated by our software development team."
"This is our way of communicating with different teams. We are a global company. I am based in San Diego, for example. A lot of the BAs are based in Paris. The development team is based in Minsk. We absolutely need to be in constant communication and on the same page."
"Some of the valuable features are the interface and the workflows are easy to learn and to manage."
"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."
"Some of the valuable features are the functionality and the wide range of capabilities."
"Monitoring is most valuable."
"It is a well-integrated product in terms of the development lifecycle."
"Microsoft Azure DevOps has been very good for creating pipelines, and all the solutions for creating task management for developers and for the business."
"This solution works with other Microsoft solutions pretty easily. It was easy to integrate everything into all the other tools that we were using. It integrates very seamlessly."
"It's a great product for the CI/CD process."
"I have noticed a problem with Jira in the Philippines. In the Philippines, there are only a few companies that offer local support, which is alarming."
"Some of the customizations are definitely a little challenging."
"Although it covers the overall requirements and measurements, it'll help if they had their own test execution feature."
"I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira."
"We would like to see integration between Tempo and Jira."
"I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA."
"Jira can improve by making methodologies better, such as scrum and agile. Additionally, improvements in Kanban boards are needed."
"I want the tool to integrate connectors."
"The main issue that I have is the connection speed. Sometimes, the response is too slow. I am based in Taiwan, and I am not sure if it is because of broadband or something else. Its initial configuration is also a little bit difficult."
"Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it."
"The interface is very bad."
"The dashboards need bigger with better extensions and layouts. There isn't a workflow related to the statuses on the dashboard. It only lists the statuses. You can have one started, and once done, but everything in between is only in progress and could be in any order you want, it lacks flow."
"There is only one key area of improvement for me. The new imaging thing is that there is DevOps, where security is important because it is always lasting. So, to integrate security in our DevOps, that would be nice."
"I would like to see DevOps have the ability to give us something with a compatibility or traceability matrix."
"There could more integration with other platforms."
"There are some areas that need improvement such as tracking."
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.
