JIRA Portfolio vs Microsoft Azure DevOps comparison

Cancel
You must select at least 2 products to compare!
Atlassian Logo
1,029 views|826 comparisons
97% willing to recommend
Microsoft Logo
21,017 views|15,998 comparisons
95% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between JIRA Portfolio and Microsoft Azure DevOps based on real PeerSpot user reviews.

Find out in this report how the two Enterprise Agile Planning Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed JIRA Portfolio vs. Microsoft Azure DevOps Report (Updated: March 2024).
771,157 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"The most valuable feature for me is the visualization and organizing of the tasks. We can have a pick, and then we can stick the multiple issues under that, and then we can again have a sort of hierarchical installation, and that's very useful.""The documentation is very well done.""The tool helps us achieve more within the stipulated timeline and budget.""In general, the valuable features of the tool are its capabilities concerning dependency reports and task status.""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 valuable features of the JIRA Portfolio are the customization it provides which is very useful and the Agile project management capability.""The solution has good reporting and is very user-friendly."

More JIRA Portfolio Pros →

"The work items option is incredibly flexible.""Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development.""The extensibility of the work item forms and customizations as well as the backend API to query the data, et cetera, and manipulate the data programmatically are all very valuable aspects of the product.""The product is easy to use and very stable.""Some of the most valuable features are the ease of use and the ability to monitor a lot of things. It has a lot of applications and facilities that meet all the developers' requirements. For example, we can use application insights to get an idea of our application's performance. Since it's cloud-based, it's really good for collaboration and working as a team.""The solution is good for everything, including end-to-end planning and its deployment and testing.""I found the Kanban board to be the most useful for my needs.""The installation is straightforward. We can create a whole new organization in less than a day."

More Microsoft Azure DevOps Pros →

Cons
"It would be really nice if the solution provided a heads-up every time they enhance something or add new features.""The workflow needs improvement.""Converting a task into an epic is very troublesome.""JIRA Portfolio could improve new implementation because if I want integration for the complete wide frame tools it cannot provide any wide frame tools.""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. 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.""There is room for improvement in terms of scalability.""It would be nice if it could provide an end-to-end solution for a project.""We are based in India; I would like the product to integrate local pricing. We earn in rupees but spend in dollars. Its pricing could also be lowered."

More JIRA Portfolio Cons →

"We are currently in the process of moving all of our on-prem to the cloud platform. We are trying to make that move and host the majority of our DevOps services in the cloud because the cloud is where most of the things are going nowadays. However, the process of this transfer is not straightforward, and it could be a lot easier. Microsoft hasn't provided the maturity for migration tools. It could be a lot easier in that respect. I want to see them continue to advance the API capabilities. They could add some more robust functionality to the administrative layer within ADO services. There are a lot of configuration elements that you need to take care of at the organization level and the project configuration level from an administrative capacity. When you're dealing with process templates and things of that nature, you have to do them all manually. Being able to automate some of that using scripts or API functionality would be really nice.""Compared to JIRA, I think Azure DevOps is missing some management elements, like some reporting features. It would be helpful if some things were clearer when we're adding attributes. For instance, sometimes we want to add some categories or attributes, and it's not so easy.""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.""Being more technology-agnostic through ease of integration would be beneficial.""Project management could be improved.""With the query feature, we have to group items, so it becomes difficult for everyone to understand it. It's easier in JIRA, which has filters and other query options.""They have brought a lot of new collaboration features in the latest version. We haven't used those features, but they should continue to expand it more on the collaboration front so that two developers can look at the code and work at the same time. It will be helpful for working from home.""When we don't have some permissions, we have to research how to get them."

More Microsoft Azure DevOps Cons →

Pricing and Cost Advice
  • "This solution has a comparable pricing in comparison to other similar products on the market."
  • "The pricing of the solution is expensive."
  • "We only have nine people using it so we have a standard cost of $150 dollar per year. There are only additional costs if you exceed the limit of users, then you start paying by user. The cost is significantly higher."
  • "The pricing continues to get higher."
  • "The product is really not very expensive."
  • "We pay our fees annually, although monthly payments are also available."
  • "The price could be improved."
  • "We have a license to use JIRA Portfolio, we are not using the free version."
  • More JIRA Portfolio Pricing and Cost Advice →

  • "It's a good tool, quite rich, it has a lot of features, and quite a lot of analytical capabilities which are built on top of it so that you can see how your projects are going and all that stuff. It's a good tool."
  • "There is a licensing fee of $6/user per month."
  • "The price is cheaper than Jira and some of the other competing tools."
  • "It is the least expensive product in this class."
  • "I find that the pricing is good, and it is competitive with the other vendors in the market."
  • "Microsoft Azure DevOps is free for up to five users and allows you to track a maximum of three projects."
  • "It is a subscription model and I only pay for what I use."
  • "The price of this solution is fair."
  • More Microsoft Azure DevOps Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
    771,157 professionals have used our research since 2012.
    Questions from the Community
    Top Answer:The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work.
    Top Answer:Given the solution’s significant functionality, benefits, and value, you get more than you pay for.
    Top Answer:The solution’s pricing could be reduced.
    Top Answer: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 scalable… more »
    Top Answer: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… more »
    Top Answer:We can track everything from the requirements stage to the production stage.
    Ranking
    Views
    1,029
    Comparisons
    826
    Reviews
    27
    Average Words per Review
    488
    Rating
    8.3
    Views
    21,017
    Comparisons
    15,998
    Reviews
    21
    Average Words per Review
    597
    Rating
    8.3
    Comparisons
    Also Known As
    Portfolio for JIRA
    Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
    Learn More
    Overview

    Jira Portfolio is an agile roadmapping tool designed to help teams build plans, envision the big picture, track progress, and share the process with stakeholders.

    Jira Portfolio is planned based. A plan in Portfolio is a complete view of the tasks, teams, and release dates for your Jira projects.

    Once you start to create a plan, there are three main factors you need to define: 

    • Scope: A list of tasks that need to be carried out in order to complete the plan.
    • Teams: Who will be implementing the work? With the correct data in place, Portfolio can estimate how long it will take for the team to complete their tasks.
    • Releases: Your scheduled release date.

    With Jira Portfolio, you can create a visual timeline to gain visibility across each of your teams and projects in a single place from a granular level and review cross-team and cross-project dependencies to prevent bottlenecks. This visibility can help you plan realistic release dates and manage your team’s capacity. The solution allows you to try out different scenarios with your roadmap and resources to help guide your decision making. Once you have a solid plan, you can easily integrate with Jira Software and commit your changes.

    Jira Portfolio allows managers to easily add team members. The tool’s powerful scheduling algorithm assigns tasks to teams while taking priorities and dependencies into account so it can create a realistic forecast for project completion. 

    Jira Portfolio Benefits

    Some of the top benefits of using Jira Portfolio include:

    • Roadmaps and roadmaps dependencies: Roadmaps list details about the tasks that need to be executed in order to complete a project, as well as predictions for when they will be completed, which teams are in charge of the task, and a list of resources they require. By setting dependencies on your team’s roadmaps, unnecessary bottlenecks are avoided.  
    • Integration with Jira: Jira Portfolio is dynamically integrated with your Jira Software project data and constantly pulls your latest data from Jira Software, allowing you to plan your projects with updated information.
    • Envision scenarios: Create what-if scenarios and save them to Jira if you decide to adopt them.
    • Reporting: Share capacity reports and more to allow team members and stakeholders to gain visibility and insights into the process.
    • Task completion estimation methods: Estimate how long a specific task will take and compare these estimations with the actual time to completion to help assess team performance and efficiency and improve the accuracy of estimation calculations over time. 

    Reviews from Real Users

    Jira Portfolio stands out among its competitors for a number of reasons. Two major ones are its roadmap creation tools and its flexibility.

    Meeta L., a lead product manager at a tech vendor, says, “The valuable features of the JIRA Portfolio are the customization it provides which is very useful and the Agile project management capability.”

    Juan P., a senior IT project manager at Avantica, writes, “Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company.”

    Microsoft Azure DevOps is a cloud service that enables developers to collaborate on code development projects and create and deploy applications quicker than ever before. The service helps unite developers, project managers, and software development experts through a collaborative experience while using the application. For the users' convenience, Azure DevOps offers the user cloud services through Azure DevOps Services or an on-premises service using Azure DevOps Server. In addition, it supports integration with additional services and adding extensions, including the ability for the user to create their own custom extensions. 

    Azure DevOps provides a variety of unified features that can be accessed through their web browser or IDE client, such as:

    • Azure Pipelines - Develop and deploy services to support ongoing application integration and delivery. Azure pipelines, which work with almost every project type and most languages, will automatically test code projects in order to make them available to others.

    • Azure Artifacts - Share packages and integrate package sharing between teams. Packages include NuGet, npm, and Maven, in addition to other private and public sources. Developers can now share and consume packages with other developers from different public registries.

    • Azure Repos - Offers source control of your code through Team Foundation Version Control (TFVC) or Git repositories. Developers can now keep track of any changes that are made in their code over the course of their project.

    • Azure Test Plans - Offers continuous and manual/exploratory app testing through several tools. Test Suites, or a collection of Test Cases, are grouped together in a container called a Test Plan.

    • Azure Boards - Provides a suite of Agile tools to track work, support planning, code defects, and general issues while using Kanban and Scrum software. Teams are in need of tools that are flexible and will help them grow. Azure Boards is a service that helps developers manage their software projects. 

    Benefits of Microsoft Azure DevOps

    Microsoft Azure DevOps offers many benefits, including:

    • A quick setup and easy deployment
    • An elastic scale
    • Exceptional security
    • No-maintenance operations
    • Effortless collaboration through domains
    • The ability to create and deploy products faster than traditional software

    Reviews from Real Users

    Microsoft Azure DevOps stands out among its competitors for a variety of reasons. Two major ones are its ability to forecast how long each task will take and the ability for users to follow the entire development process.

    PeerSpot viewers note the effectiveness of this solution. An executive chief operating officer for a cloud provider notes, “We can forecast tasks and the number of hours a task will take and can compare it with how long a task actually takes.” 

    Carlos H., a product and system director at SPCM, writes, “I think the most usable thing is that you can follow the whole progress of the development process. This makes it very useful for us.”

    Sample Customers
    Rosetta Stone, Sprint, UBS, Workday, Expedia, J.P. Morgan
    Alaska Airlines, Iberia Airlines, Columbia, Skype
    Top Industries
    REVIEWERS
    Computer Software Company33%
    Manufacturing Company15%
    Educational Organization11%
    Comms Service Provider7%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company15%
    Manufacturing Company10%
    Government7%
    REVIEWERS
    Computer Software Company23%
    Financial Services Firm15%
    Energy/Utilities Company11%
    Manufacturing Company8%
    VISITORS READING REVIEWS
    Computer Software Company13%
    Manufacturing Company11%
    Financial Services Firm11%
    Government9%
    Company Size
    REVIEWERS
    Small Business23%
    Midsize Enterprise21%
    Large Enterprise56%
    VISITORS READING REVIEWS
    Small Business16%
    Midsize Enterprise10%
    Large Enterprise74%
    REVIEWERS
    Small Business31%
    Midsize Enterprise18%
    Large Enterprise51%
    VISITORS READING REVIEWS
    Small Business18%
    Midsize Enterprise14%
    Large Enterprise68%
    Buyer's Guide
    JIRA Portfolio vs. Microsoft Azure DevOps
    March 2024
    Find out what your peers are saying about JIRA Portfolio vs. Microsoft Azure DevOps and other solutions. Updated: March 2024.
    771,157 professionals have used our research since 2012.

    JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 49 reviews while Microsoft Azure DevOps is ranked 1st in Enterprise Agile Planning Tools with 127 reviews. JIRA Portfolio is rated 8.2, while Microsoft Azure DevOps is rated 8.2. The top reviewer of JIRA Portfolio writes "Powerful, flexible solution with a bit of a learning curve". 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 Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Project Server, Adobe Workfront and Broadcom Clarity , whereas Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, Rally Software and ServiceNow Strategic Portfolio Management. See our JIRA Portfolio vs. Microsoft Azure DevOps report.

    See our list of best Enterprise Agile Planning Tools vendors.

    We monitor all Enterprise Agile Planning Tools 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.