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.
"Jira's most valuable features are ease of use, simple to understand, and highly flexible. Additionally, you can use kanban or scrum which is a benefit."
"The initial setup isn't too complicated."
"The most valuable feature of Jira is the reporting feature, which allows us to track our team's tasks."
"The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily."
"Jira has been a good l tool for collaborating across large groups of people. The JQL feature is powerful and easy to use."
"The JIRA user interface looks great. It's an overall good experience. It's very intuitive in the sense that you understand how it's going to work. It's very self-explanatory, and it's beneficial overall."
"It is very configurable, and we can do whatever we want. Jira dashboards are also good, and we use them extensively. We also use the tracking mechanism extensively."
"Issue linking has enabled teams to trace issues."
"We can track everything from the requirements stage to the production stage."
"There are great automation tools."
"I like the tracking and that we can monitor our velocity."
"It's a pretty problem-free solution."
"What I like most about Azure DevOps is how easy it is to manage projects and control deployments."
"The CI/CD pipeline setup is more user-friendly. You can manage various stages, and there are over 400+ plugins available for each stage."
"Monitoring is most valuable."
"We use all the DevOps features and services, like reports, Boards, Pipelines, Artifactory, etc. The interface is interactive and intuitive. The platform visuals and workflow are straightforward in Azure DevOps."
"I would like to see visualization of release planning. I can list the releases and I can give dates to releases, but to show how they are happening on a timeline, I would need to order the Portfolio part. But just for this, it may be too much to use the Portfolio for that."
"The reporting part is a little bit difficult for me. It is not so easy. There should be a simpler way to track the efforts of our team. For example, in an Excel sheet, there is a feature for filtering. It would be much better if we can use something like that. Currently, for a complex query, we need to use Jira Query Language. Using Jira Query Language every time is not efficient for me."
"The plugin management needs a lot of work."
"I find the dashboard to be Jira's most problematic feature."
"Having more seamless integration with Confluence would really help us track our product management activity and other product details in one place."
"Jira could provide more insight into sprints such as how did we perform in the last sprint compared to other sprints. It would be helpful to have metrics and a dashboard feature for others to see."
"It should be connected to ServiceNow."
"The user interface is very detailed right now. It could be simplified if they consider targeting the user experience."
"Another area is the Azure monitoring agent for Citrix machines. There's room for improvement there too."
"There could more integration with other platforms."
"If they could build up requirement traceability metrics, then it would be great."
"Non-functional testing such as security testing, log testing, and performance testing can be improved with a better visualization."
"They have to add more features such as schedules and more flexibility in the platform."
"The solution could be made faster because it can be a little unnerving to browse through too many pages and press too many buttons."
"The documentation isn't straightforward."
"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 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.