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."The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it."
"The most valuable features of Jira are the dashboards where we see all the features lined up with the release dates in the portfolio view, it is very good."
"In general, the valuable features of the tool are its capabilities concerning dependency reports and task status."
"The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized."
"JIRA has helped us reduce the rate of unseen or undetectable issues in the future. It has also helped us understand the demand overload across the defense team, including capacity and availability, and how we can leverage different teams to ensure overall success."
"The product makes it easy to collaborate even though it can use some improvement in that area."
"Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company."
"We have found the solution to be stable."
"There are a lot of helpful features available for tracking dependencies."
"Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting."
"It is stable, and we have had no issues with it."
"It is stable. I like Azure a lot. All our guys are Microsoft certified."
"The product is easy to use...It is a stable solution."
"The solution integrates well with other Azure services and third-party tools."
"It's got something that you won't find in other products."
"It is possible to add third-party extensions to increase the usability of the product."
"It would be really nice if the solution provided a heads-up every time they enhance something or add new features."
"I think that front-end development is a little bit buggy in some cases. Some of the features take a while to respond and some need to be more clear."
"Requires some effort to insert functionalities and that could be simplified."
"We are using the on-premise deployment, but it is slower and not as easy to manage as the cloud version."
"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."
"Converting a task into an epic is very troublesome."
"If you want to generate a report for individual usage, it's difficult."
"JIRA and Confluence must be linked automatically."
"The portfolio is one area where DevOps has room for improvement. Built-in reporting and visualization also could be better. We're using Power BI and Tableau to compile more complex reports and dashboards. Azure DevOps has some out-of-the-box reporting capabilities, but they're very simple. It's usually okay on the team level, but if you have to run a complex report, it's difficult and insufficient, so we use Power BI as an extension."
"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."
"I can't think of any specific things at the moment, but I've run into things that I didn't like. I came across something that I wanted to be changed in DevOps, but I can't remember what it was. It was a particular feature I was looking for that I couldn't find."
"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."
"Something that could be improved is the initial setup with the integration of ReadyAPI."
"The ability to integrate Microsoft Azure DevOps with other platforms and Microsoft products can be improved."
"When you compare with Jira, there is a lack of progress features."
"Microsoft Azure DevOps should create some training materials."
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.
