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

JIRA Portfolio vs Microsoft Azure DevOps comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

JIRA Portfolio
Ranking in Enterprise Agile Planning Tools
4th
Average Rating
8.2
Reviews Sentiment
7.3
Number of Reviews
57
Ranking in other categories
No ranking in other categories
Microsoft Azure DevOps
Ranking in Enterprise Agile Planning Tools
1st
Average Rating
8.2
Reviews Sentiment
7.6
Number of Reviews
130
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Release Automation (1st)
 

Mindshare comparison

As of November 2024, in the Enterprise Agile Planning Tools category, the mindshare of JIRA Portfolio is 1.2%, down from 2.6% compared to the previous year. The mindshare of Microsoft Azure DevOps is 42.3%, up from 38.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Agile Planning Tools
 

Featured Reviews

Gary Craven - PeerSpot reviewer
Powerful, flexible solution with a bit of a learning curve
The weakness of the solution is that the interface is a little nonstandard, meaning it's very flexible. It's got a lot of power and gives the user the ability to combine different projects into the portfolio and move user stories between projects and link them. What I have found in a couple of organizations that I've used it with, is that the uptake tends to be a little slow because it's got a bit of a learning curve. It can dump data out to Excel and those programs, but it also has a big ecosystem of plugins and add-ons that you can get. I guess it has some strength in that regard, but if you're going to run it on-prem, you have to have people that are pretty well-versed in the program and have the time and capabilities to handle integration and make sure they're adding those modules correctly. Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. Now they are moving into these new use cases, including systems development, business projects, business processes, and redevelopment projects, but there is a problem with the nomenclature that they use, and some of the documentation is a little techy for moving it into those more business-focused use cases. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up.
Akshat Prakash - PeerSpot reviewer
Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling
My company has experienced benefits from using it or from recent updates in Azure Pipelines. For instance, we can manage different code versions from the same repository across different environments. We also use feature flags; the code is deployed, but the feature can be made visible to the end user at a later time. Additionally, as part of the deployment, we integrate automated and regression testing, which stops the deployment if testing fails, thus preventing regression bugs. This saves time and increases productivity by reducing the need for manual testing. Lastly, it integrates with the project management aspects, allowing us to link code deployments with project milestones. Azure DevOps supported our shift towards DevOps culture or practices. We shifted to the cloud environment and started migrating from our data centers about eight or nine years back. It has been a long journey. However, we have used Azure DevOps for almost five to six years in every project. We also use automation testing in Azure, so we have an integrated test suite that allows us to perform functional and regression testing effectively via the Azure DevOps system.

Quotes from Members

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

Pros

"In a PC environment, it is quite stable."
"Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company."
"The product's centralized database creates a single source of data for working groups so no data needs to be reconciled."
"I use it to plan and schedule the things I take care of. I can create and share a document if I want to discuss new ideas with my team remotely."
"The way to manage cards as a KANBAN, is really easy but when you need to track hundreds of projects, you need to be very clear in which way the things must be completed."
"The most valuable feature of the JIRA Portfolio is for managing teams of 10 or more. It can track the program level and portfolio. There are plenty of beneficial features, such as the hierarchy-level view, customization, and structure plugin."
"JIRA Portfolio has many wonderful features."
"The product's integration capabilities work pretty well, especially considering that more tools are always needed in enterprise-sized businesses."
"Azure Port is considered the most valuable feature."
"If someone is considering developing and deploying the infrastructure in this solution, then using this tool is perfect because it's fully integrated with the pipelines and with a server core repository."
"The build and release management features are valuable."
"The product is easy to use and very stable."
"The most valuable feature is the ease of use and performance."
"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."
"Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check-in/check-out activity, and developer/tester productivity."
"We are able to generate many different types of reports from Azure."
 

Cons

"Currently lacks AWS integration."
"The product presently lacks visualization capabilities"
"We would love to be able to have direct contact with Atlassian. Currently, they are not working directly with West African countries. We are considering using JIRA Align, but when we contact them, they say that as we are in West Africa, they don't directly work with West Africa."
"The workflow needs improvement."
"We are using the on-premise deployment, but it is slower and not as easy to manage as the cloud version."
"As there are no perfect solutions and considering that I rate JIRA Portfolio's stability an eight out of ten, I feel it is an area with certain shortcomings where improvements are required."
"Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights."
"The automation in JIRA Portfolio could improve, it takes some time. We have to do some other tactics to have the same integration. Manually integrating something will take more work than if it was automated, but the automation scripting in the solution is not simple."
"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."
"Something that could be improved is the initial setup with the integration of ReadyAPI."
"As for room for improvement, more features need to be added to the classic pipeline. The build and release pipelines are present, but there has not been much improvement there."
"Incorporating security tools directly into DevOps is crucial, as many existing DevOps solutions lack robust security features."
"Microsoft Azure DevOps doesn't have an ITSM tool compared to its competitors."
"I can't think of anything I would like to improve, since I don't have complete knowledge of the platform yet. I'm sure that as I gain more experience, I will understand it better. The price could maybe be cheaper, but I'm sure I'll have more ideas as to improvements and additional features once I've used it more."
"They could provide clearer guidance on deployment practices for the product."
"Some of the queries, the way they're built, need to be looked at. We need better query tools."
 

Pricing and Cost Advice

"The price is reasonable"
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing an eight."
"We have a license to use JIRA Portfolio, we are not using the free version."
"The pricing of the solution is expensive."
"Given the solution’s significant functionality, benefits, and value, you get more than you pay for."
"Portfolio is well-priced - a license for ten users costs $100 or $150 a month."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a six."
"There are free plugins available, but most of them are at an additional cost. Additionally, other services are an extra cost."
"The cost is quite affordable."
"The reason that customers are going to the cloud is that it provides the ability to reduce the license cost. For example, when purchasing Office 365 it is bundled with Word, Excel, PowerPoint, Access, and many other applications. In the past, purchasing a license was approximately $600. Today it's only $35 or $45 per customer, per client, or per user, plus the storage. It's less expensive for companies today, to use something, such as Microsoft Azure DevOps, and provide the software to all the employees needing a license. It's better to go with the cloud than just to buy the licenses by themselves."
"It is relatively inexpensive compared to other solutions that necessitate servers and physical hardware."
"The solution costs $5 or $10 per user, per month."
"There are other solutions available that are open source and free, such as GitLab."
"The licensing structure is good."
"It is a subscription model and I only pay for what I use."
"As a Microsoft Partner, you get a discount on the pricing. Licensing costs are around $80 a month for DevOps, but for Azure, it is about $200 a month."
report
Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
17%
Manufacturing Company
11%
Government
6%
Manufacturing Company
13%
Computer Software Company
12%
Financial Services Firm
12%
Government
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about JIRA Portfolio?
The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work.
What is your experience regarding pricing and costs for JIRA Portfolio?
When we first got the tool, it cost 3,000 euros a year for unlimited users, which was a great deal. But the prices kept going up over the years. I'm not involved with pricing anymore, but I heard t...
What needs improvement with JIRA Portfolio?
The tool needs to improve its speed and response time.
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 and work logs. It is easy to implement and navigate, and it is stable and scalabl...
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 improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
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-in/check-out activity, and developer/tester productivity.
 

Also Known As

Portfolio for JIRA
Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
 

Overview

 

Sample Customers

Rosetta Stone, Sprint, UBS, Workday, Expedia, J.P. Morgan
Alaska Airlines, Iberia Airlines, Columbia, Skype
Find out what your peers are saying about JIRA Portfolio vs. Microsoft Azure DevOps and other solutions. Updated: November 2024.
816,406 professionals have used our research since 2012.