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."Its stability is very reliable."
"I think the solution's most important and valuable feature is its ability to track the issues."
"In a PC environment, it is quite stable."
"The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects."
"Having an option to view dependencies between projects and teams is great."
"The solution is stable and reliable."
"Version management is the most valuable feature of JIRA Portfolio."
"The product makes it easy to collaborate even though it can use some improvement in that area."
"The most valuable features of this solution are the CI/CD pipeline, and the testing automation."
"Two of the most valuable features include the integrated project management suite, which consolidates source code and project management in a single location, and its powerful reporting capabilities."
"The initial setup is very easy."
"The solution is easy to implement and easy to use."
"Azure DevOps is effective for repository management and code collaboration. We can create branches, differentiate between code versions, save and review code later, get PR approvals, and more. All these features are valuable."
"It is stable. I like Azure a lot. All our guys are Microsoft certified."
"All features are good. Pipelines feature is great, and Boards and Artifacts features are also really good. It is really good at what it does. It is very comprehensive, and it has some really great aspects to it. It is very easy. It is probably one of the easiest to use DevOps tools in the industry, and it is well integrated."
"The most valuable feature in automating our build and release processes with Azure DevOps is the scheduling capability."
"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 product could do with more flexible reporting."
"The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise."
"This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing."
"JIRA Portfolio could improve new implementation because if I want integration for the complete wide frame tools it cannot provide any wide frame tools."
"Converting a task into an epic is very troublesome."
"In the next release, Portfolio should include more metrics and develop their portfolio planning."
"JIra is very poor at reporting."
"The administrative capabilities of the tool need a huge improvement. Its Wiki and reporting also need a lot of improvement. Their support can also be better."
"Microsoft Azure DevOps should create some training materials."
"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."
"The tutorials for building pipelines are an area that is a bit technical for a beginner."
"I would like to see new features added."
"The user interface could be improved."
"With Microsoft, I would prefer to have more test plans. It's very difficult to find individual test plan module training."
"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."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 46 reviews while Microsoft Azure DevOps is ranked 1st in Enterprise Agile Planning Tools with 122 reviews. JIRA Portfolio is rated 8.0, 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 "High level protection, scales well, but more customer feedback updates needed". JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Adobe Workfront, Microsoft Project Server 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.