Try our new research platform with insights from 80,000+ expert users

Digital.ai Agility vs Jira vs Microsoft Azure DevOps comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Mindshare comparison

As of October 2025, in the Application Lifecycle Management (ALM) Suites category, the mindshare of Digital.ai Agility is 2.0%, up from 1.4% compared to the previous year. The mindshare of Jira is 17.4%, down from 23.2% compared to the previous year. The mindshare of Microsoft Azure DevOps is 12.9%, down from 21.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites Market Share Distribution
ProductMarket Share (%)
Jira17.4%
Microsoft Azure DevOps12.9%
Digital.ai Agility2.0%
Other67.7%
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

Debbie Brey - PeerSpot reviewer
A scalable, full-package solution with a tech support team that bends over backwards to help
There is room for improvement in getting the analytics portion of the solution more integrated with the rest of it. The feature I would like to see is already in their newer licensing structure, and that's the live integration between Agility, Jira and Azure DevOps. That's the piece that I think is really valuable.
AmitUbale - PeerSpot reviewer
Efficient project management that's comprehensive and and helps with time efficiency
We use Jira primarily for project management within the organization. It helps us manage tasks, bug management, and tracking tickets effectively. We assign tickets to individual team members and track them easily For project management, Jira has helped facilitate efficient task segregation and…
Ivan Angelov - PeerSpot reviewer
Facilitates agile transformation with potential for enhanced intuitiveness
What I liked about the solution is that it offers numerous features that are not available by default unless you are agile. Transitioning from the traditional Waterfall model to an agile methodology was challenging for us. Until 2020, our team predominantly worked with the Waterfall approach, using local tools like ServiceNow. We had a few team members who were familiar with Agile ISO, but none had experience with Azure. Therefore, we pursued Azure certification at the AZ-900 level. Our company organized a training session with a certified Azure expert, which was extremely beneficial for adopting best practices during the initial three months. This preparation helped us get accustomed to the new tool, as transitioning to a new system invariably requires time. Managing a pipeline of deliverables became significantly easier with this solution. We utilized it for stories and integrated change management with Azure DevOps. Eventually, everything related to the environment was organized there, enabling us to follow up and track progress with our technical engineers on an hourly, daily, or weekly basis. Reports were automatically generated and sent to management, offering them insights into our progress concerning the predefined roadmap.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It allows my clients to have one central tool to manage their agile projects."
"It can generate reports showing a burndown chart, burnup chart, and the planned vs actual velocity."
"With some of the other tools, you have to buy 20 different plugins to get to the same capability that comes with the basic Agility capability."
"Agility is highly flexible. It can do much more than what our client is doing with it. They use it in a defined way. Some at that company have a much broader knowledge of agile and SAFe, but they're given applications and a mandated way to work. We had to work within their parameters and provide an accurate transition so the data would be mapped and pushed through."
"For visualization capabilities, the automation capabilities make it possible to support the different personas. The features and capabilities are excellent and come with excellent support."
"I think one of the most powerful features in Jira is the customization of fields and workflow."
"The solution has been very stable overall."
"Kanban boards are most valuable"
"The most valuable features are that it is good for tracking the issues and it provides for the usage of Confluence."
"Great for tracking my development team's productivity."
"The initial setup was pretty straightforward."
"We use Jira for project management and tracking."
"The solution is easy to use and user-friendly."
"The most valuable feature is automation with version control."
"Azure Pipeline and Azure Release are most valuable. I use Azure DevOps through pipeline and release."
"The solution integrates well with other Azure services and third-party tools."
"There are great automation tools."
"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."
"You can have test cases in DevOps but not in JIRA. And, DevOps has advantages in terms of executing those test cases."
"It's a great product for the CI/CD process."
"Some of the valuable features are the interface and the workflows are easy to learn and to manage."
 

Cons

"Improve how to create and track releases. Currently, I have to create child projects."
"In my work as a contractor, it's always frustrating when a client has multiple software applications that don't talk to each other and they all perform the same function. That presents a huge challenge between their IT groups."
"There is room for improvement in getting the analytics portion of the solution more integrated with the rest of it."
"The user interface can be improved by adding Save, Edit, Add, Cancel, and Return buttons to the popup windows that are displayed when you click on a child item."
"The machine learning features are a new capability but could be improved. This is being worked by Digital.ai currently. Multicolor simulation, specifically, could be improved."
"It was not supporting some plugins. We wanted to migrate data that we were already using."
"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."
"An area for improvement in Jira is that it's not designed for test management. To use it for test management, you need an add-on or several add-ons, e.g. Xray or Zephyr."
"Performance is something that can always be improved upon in a feature release. Additionally, it would be a benefit to add Markdown in Jira because sometimes it might be better to describe everything in Markdown because it is a common language structure."
"I want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting."
"The performance is not so good sometimes. I know that fully depends on the implementation and the IT environment of Jira or the version of Jira installed. The performance is sometimes not so good. I would like to have a better response time from the Jira server. And it fully depends on the administration side of the Jira."
"It should be connected to ServiceNow."
"As the solution is highly configurable, it has very poor governance."
"Lacks some common building block approaches to certain things."
"The UI, the user experience, is challenging for newcomers."
"Reporting could be better. We would like to see how many applications are onboarded in DevOps and in which phase they are. We would like to know for how many applications we have done only the repository, but we have not yet done the build pipeline or deploy pipeline. Currently, there is no such report. We have to figure it out ourselves. There is no way to check how many applications are completing their build pipelines, how many applications are completing their deploy pipeline, how many are ready to use, and how many pipelines are working."
"Azure DevOps is set up more for development and less for testing. If it is set up correctly, everyone can use it better, but it was set up from a development point of view, which means it is lacking in what I need from a testing perspective. Just like any other tool, it depends on how it is configured. I am not happy with the way it is set up. It is configured more from a development side, and it doesn't necessarily cater to all the other areas that probably need to use it, such as testing data, etc."
"The active directory password system needs some improvement because many times the password for the active directory expires before the set time."
"When we don't have some permissions, we have to research how to get them."
"The UI could be improved."
"The communication could work better, especially for the development team."
"Incorporating security tools directly into DevOps is crucial, as many existing DevOps solutions lack robust security features."
 

Pricing and Cost Advice

"You get what you pay for. Don't let your development teams dictate what the portfolio management team should use as the main tool."
"Comparing the pricing to other products, I think this solution is in the middle."
"Jira is expensive and a lot of people are choosing DevOps because they are cheaper, open-source, easy to use, and have basic licenses. Jira should decrease its price to be more competitive."
"Compared to the value Jira provides, it’s not that expensive. It has an yearly licensing cost."
"Almost everybody uses JIRA nowadays because it is the most cost-effective solution."
"There is a monthly license required for this solution and it is expensive."
"To try this solution, use their cloud offering to get familiar. After that, it's in my view worth the money."
"It's not very cheap. It's also not very costly. I'd rate it a five out of ten in terms of pricing."
"Our client handles the licensing aspect. They have not yet purchased the premium version."
"If you are using just Jira, it is cheap, but if you start to use it and you feel you need some more services or more functions, then you have to buy add-ons, which can make it expensive."
"The price of the solution is expensive."
"Licensing cost per user is approximately $11 to $15. We have about 400 users, but not all are active. We have around 200 to 300 active users."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"I don't know the pricing of DevOps. It would be much cheaper than ALM because ALM came out as a software product initially. Now they are moving into a cloud and subscription model. In that case, Microsoft is coming from Azure and the cloud and DevOps and software as a service, so it would be much cheaper, but the catch would be that they are trying to get money on all the sides, like an operating system, Microsoft Office, or Microsoft Azure DevOps."
"The licensing structure is good."
"The main agile features are very expensive."
"I find that the pricing is good, and it is competitive with the other vendors in the market."
"There are additional costs for some functionality, such as increased scalability."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
868,706 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
20%
Insurance Company
18%
Computer Software Company
11%
Financial Services Firm
8%
Manufacturing Company
16%
Financial Services Firm
11%
Computer Software Company
10%
Government
8%
Manufacturing Company
14%
Computer Software Company
12%
Financial Services Firm
11%
Government
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business103
Midsize Enterprise56
Large Enterprise149
By reviewers
Company SizeCount
Small Business42
Midsize Enterprise26
Large Enterprise69
 

Questions from the Community

What needs improvement with Digital.ai Agility?
It was not supporting some plugins. We wanted to migrate data that we were already using. The migration of data and g...
What is your primary use case for Digital.ai Agility?
We were explaining how to set up the project itself, which describes the main use cases for Digital.ai Agility. This ...
What advice do you have for others considering Digital.ai Agility?
Digital.ai Agility has a bigger reach because it has many good integration points. It can be a one-stop solution for ...
Is Jira better or would you go with Micro Focus ALM Octane?
Hi Netanya, Basically , it all depends on the use cases for your environment and the business needs. Hope the below d...
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products a...
What is your experience regarding pricing and costs for Jira?
We operate under a nonlimited license with Jira, allowing a number of users to access it with a single enterprise lic...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvement...
What do you like most about Microsoft Azure DevOps?
Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check...
 

Also Known As

VersionOne Lifecycle, VersionOne, CollabNet VersionOne, Digital.ai Continuum
Jira Software
Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
 

Overview

 

Sample Customers

Siemens Health Services (HS), Cerner Corporation, Aaron's, Federal Home Loan Bank of Atlanta, Kelley Blue Book, AOL, Axway, Tideworks, bwin Interactive Entertainment, AG, Intergraph, Eos Group, PeopleCube, Liquid Machines
Square, Nasa, eBay, Cisco, SalesForce, Adobe, BNP Paribas, BMW and LinkedIn, Pfizer, Citi.
Alaska Airlines, Iberia Airlines, Columbia, Skype
Find out what your peers are saying about Atlassian, Microsoft, Nutanix and others in Application Lifecycle Management (ALM) Suites. Updated: September 2025.
868,706 professionals have used our research since 2012.