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.
"It's really smart how they connected third-party vendors into their own marketplace. You can create and add apps. Anybody can do it."
"The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily."
"The solution has been very stable overall."
"The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations."
"I like that all of the team members on an agile team can use it. No one is in a separate application."
"You can record your unit testing, regression testing, UATs, et cetera."
"Scaling the product wouldn't be difficult."
"The initial setup isn't too complicated."
"Monitoring is most valuable."
"One of the main features is the user interface is very good."
"Azure Port is considered the most valuable feature."
"The solution is good for everything, including end-to-end planning and its deployment and testing."
"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."
"The product is easy to use...It is a stable solution."
"It is a really easy way to define all of the features that you need to deliver. You can link those features to epics and break them down into user stories. You can also assign the user stories into sprints for doing your product improvement planning."
"All of the features related to release management are very good."
"I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA."
"It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins."
"The initial setup was a bit problematic in terms of getting access to Jira. That goes for a few users, including me."
"Sometimes, we create the same bug with two or three different Jira tickets in my company, which leads to duplication, making it an area where improvements are required."
"I am not sure if Jira can be integrated with our ERP. We have our ERP for the cost estimates or measurements. It would be nice if we can check or view a plan with the real cost. Currently, we have to do a double check of costs. It would be better to be able to integrate it with Jira."
"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."
"They are not supporting in-house servers anymore and I think I've got until January to port this to something else."
"Nowadays, many organizations are moving toward the Objectives and Key Results (OKR) framework, and this is something that Jira should be able to accommodate."
"The user management in the solution could improve."
"Microsoft Azure DevOps could improve by providing better integration with other tools. It is very easy to integrate with Azure, but when you need to integrate with other solutions, such as Amazon Web Services, is difficult."
"In comparison to JIRA, I believe DevOps has very poor reporting and metrics support."
"The tool was developed for Agile project methodology, but I've noticed that there has also been a try to incorporate what is typically done in MS Project, which is for more sequential Waterfall projects. The problem with that is that it is half-baked for Waterfall projects. If you're going to do it, then either go all the way and allow us to use the tool for both or don't do it at all."
"I would like to see a bit more project tracking."
"There is room for improvement on the UI side, especially with merge requests. If we compare Azure DevOps to GitLab when it comes to branches and PRs (pull requests), GitLab has a better interface."
"When you compare with Jira, there is a lack of progress features."
"Incorporating security tools directly into DevOps is crucial, as many existing DevOps solutions lack robust security features."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 265 reviews while Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 126 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.
