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 offers tools for managing projects using Agile methodology. I think it is good to encourage the development team to use Jira, so that the organization benefits from the proper execution of projects on time. Basically, it helps our organization to execute in a better way."
"Jira has been a good l tool for collaborating across large groups of people. The JQL feature is powerful and easy to use."
"The UI is good. It's simple and not very complicated. It's very good for tracking."
"The board has been a very valuable feature because it can be very simple for teams that are not technical. It can also be highly technical and have lots of data for teams that are technical. So we use it for both instances."
"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."
"For QA, the most interesting for me are boards, backlog, and filters."
"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."
"I liked the flexibility of the application. It was pretty user-friendly."
"Some of the valuable features are the interface and the workflows are easy to learn and to manage."
"The nice thing about Visual Studio Code is that it's a modular design. So if you're working on a strange language that has a different syntax, you can just get a plugin that'll format your code for you based on the language it's in."
"What I like the most about this product is that it's free and it's secure."
"The most valuable features of Microsoft Azure DevOps are high-level protection. The protection is very important to the customers to prevent eavesdropping. eavesdropping is when a hacker tries to get into the solution. With this solution is it difficult for them to do it."
"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."
"The creation of test plans is valuable and I like the reporting features."
"We can forecast tasks and the number of hours a task will take and can compare it with how long a task actually takes."
"It is stable, and we have had no issues with it."
"The plugin management needs a lot of work."
"The user interface is very detailed right now. It could be simplified if they consider targeting the user experience."
"In JIRA, it's a bit complex in terms of what advanced search queries we use. Sharing them is also a problem. Because TFS is on the cloud, we can easily save that query and share it with our team members."
"There could be an improvement in loading files and images for more than 50 MB. It would be good if it allowed more than 100 MB."
"Lacks field-level permission in the cloud version."
"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."
"The solution could be more user-friendly."
"While it's very powerful, it's very complex sometimes."
"It would be great if I could integrate with a human resource type of software that could control timesheets."
"They could provide clearer guidance on deployment practices for the product."
"I would like to automate notifications on sprint planning. When we are getting to the end of sprint planning, we would be automatically notified."
"When comparing with Jira, I find that the task management capabilities in Azure DevOps are not yet fully comprehensive and should be enhanced."
"Another area is the Azure monitoring agent for Citrix machines. There's room for improvement there too."
"Something that could be improved is the initial setup with the integration of ReadyAPI."
"The solution could work to improve their reporting."
"Azure has not yet advanced to the performance level of the other major competitors and is missing integration with important technologies."
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.
