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."Has good analysis integration capabilities."
"Having an option to view dependencies between projects and teams is great."
"JIRA Portfolio has many wonderful features."
"The workflow and bucket features are most helpful."
"Managing product development and managing inter-team communications are also valuable features."
"The solution helps you organize projects"
"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 integration is very good. We've more or less integrated with everything including reporting and registering."
"The solution is good for everything, including end-to-end planning and its deployment and testing."
"The solution is scalable."
"The solution is easy to implement and easy to use."
"In Microsoft Azure DevOps, you have a one shop to get everything."
"Overall, so far we have no major issues to report."
"They have been lately adding features to the services on a regular basis. Every two weeks, they are adding functionality to Azure DevOps Services to match it with what Azure DevOps Server or on-prem would offer. So, we continue to get more robust functionality. My favorite right now is that they are starting to open up the API availability within Azure DevOps Services. Another thing that I like about Azure DevOps is that you can use it with any of the products that are on the market. You can integrate it with Jenkins and other open-source products to complete that fully functional CI, CD, CT, CM, and CS pipeline. It continues to enhance."
"It is a well-integrated product in terms of the development lifecycle."
"Setting up Azure DevOps was straightforward. It's easy to use the default templates. Everything is under our control, so it's simple to implement new requirements."
"I think their view needs to be more user friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using."
"We are using the on-premise deployment, but it is slower and not as easy to manage as the cloud version."
"The data query language needs improvement."
"With Jira, an issue that arises is the length of time it takes to show certain data."
"Learning JIRA is not so easy. There is a learning curve."
"The workflow needs improvement."
"Our major team does not control or manage JIRA server well since sometimes there is trouble using the solution, which is a problem. The solution's speed needs to be improved."
"There should be an integration of efforts between the cloud service providers' side and JIRA Portfolio."
"We would like some bidirectional synchronization. It's the requirement if you want to analyze it to software requirements, et cetera. That's something that most of the tools aren't that good at."
"At times, our development work encounters issues, particularly when executing numerous CI/CD processes."
"The solution is generally stable but not entirely issue-free."
"The dashboards need bigger with better extensions and layouts. There isn't a workflow related to the statuses on the dashboard. It only lists the statuses. You can have one started, and once done, but everything in between is only in progress and could be in any order you want, it lacks flow."
"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."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
"The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project."
"The price could be lowered. It would be nice if it was cheaper."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 55 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.