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."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."
"Having an option to view dependencies between projects and teams is great."
"Jira Portfolio is useful for tracking time and hours. It's easy to manage, create tickets, and change the status of delivery reports. It's not complicated."
"The tool helps us achieve more within the stipulated timeline and budget."
"We have found the solution to be stable."
"With JIRA, you can do amazing things by developing connectors, embedding features, and adding new fields to create new things."
"Its stability is very reliable."
"JIRA Portfolio has many wonderful features."
"The CI/CD pipeline setup is more user-friendly. You can manage various stages, and there are over 400+ plugins available for each stage."
"The most valuable feature of the solution is task management."
"Some of the valuable features are the functionality and the wide range of capabilities."
"The installation is straightforward. We can create a whole new organization in less than a day."
"The solution integrates well with other Azure services and third-party tools."
"Version control practices have been perfect for us. It maintains a detailed history and is integrated with GitHub, which is also a Microsoft product. It is quite a game-changer."
"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."
"One of the main features is the user interface is very good."
"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."
"In the next release, Portfolio should include more metrics and develop their portfolio planning."
"The initial setup could use improvement."
"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."
"When I want to embed Jira Portfolio in a complete HLI cycle, I'm missing things to evaluate my ethic into my value stream."
"There should be an integration of efforts between the cloud service providers' side and JIRA Portfolio."
"We had to use assistance for the initial setup."
"Portfolio is easy to scale, but we've had some difficulties with it regarding compliance and support."
"The tutorials for building pipelines are an area that is a bit technical for a beginner."
"When comparing with Jira, I find that the task management capabilities in Azure DevOps are not yet fully comprehensive and should be enhanced."
"They have to add more features such as schedules and more flexibility in the platform."
"With Microsoft, I would prefer to have more test plans. It's very difficult to find individual test plan module training."
"It's too technical sometimes because it's meant for network developers. The CI/CD pipelines are not very easy to manage because it requires a lot of input. So it could be easier to manage."
"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."
"The only downside is that the deployment could be a little challenging but it is manageable."
"Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 51 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.