We performed a comparison between JIRA Portfolio and OpenText ALM Octane 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 best features of JIRA are its flexibility and configurability, allowing us to tailor it to our specific needs."
"Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company."
"In a PC environment, it is quite stable."
"The product's centralized database creates a single source of data for working groups so no data needs to be reconciled."
"The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects."
"Portfolio's most valuable features are that it's user-friendly and customer-centric."
"The most valuable feature of JIRA Portfolio is the visuals it provides rather than Kanban boarded tickets."
"Portfolio's best feature is integration with other JIRA products."
"The user experience is a lot better than any tool that I have used before. Overall, it is great. It has a smooth interface, which is very user-friendly. It makes it easier to work together and have more transparency and customization, which is very good."
"Micro Focus' technical support is good."
"We are seeing some real improvements in the way we do things. We are becoming more agile in the way we do it because of that and in a way that stories are managed. Stories are given lifecycles as opposed to just being entities within a tool."
"Octane works well with the Jira portfolio to track the project with two methods: Agile and Waterfall. We can track all the testing in Waterfall or Agile and synchronize it with Agile tools."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"A valuable feature is the pipeline, so that we can now connect to Jenkins and then have all the results from testing, from external, in the tool, so that we can see the whole approach from there. Also, We can work with labels so we have better filtering solutions than in ALM. And it's much smarter and leaner to use than ALM."
"Its end-to-end traceability is one of the big advantages. Most of our agile projects work in a closed team structure. We are seeing what is the flow, where we are, and what is the project milestone. So, it provides end-to-end traceability and good visibility of project milestones."
"The solution natively supports Agile-Waterfall hybrid software development at an enterprise scale. This is very important to us. Because even though the company wishes to go Agile, we still have projects which follow a Waterfall methodology. In order for us to accommodate both, we needed some sort of hybrid system. Because if we are using a fully Agile system, then the reporting might not be correctly extracted."
"It would be nice if it could provide an end-to-end solution for a project."
"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."
"JIRA Portfolio could improve new implementation because if I want integration for the complete wide frame tools it cannot provide any wide frame tools."
"The workflow needs improvement."
"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."
"There should be an integration of efforts between the cloud service providers' side and JIRA Portfolio."
"The reporting and dashboard capabilities have room for improvement."
"Converting a task into an epic is very troublesome."
"The Requirements Module could be better, to build up a better requirements process. There's a huge improvement from ALM.NET to Octane, but it's still not really facilitating all the needs of the product owners, to set up their requirements in Octane."
"The solution should improve by adding scrum board-like functionality."
"The reporting is lacking from a requirements matrix and a traceability perspective."
"Improvements could be made by way of additional integrations across the lifecycle."
"I have yet to experience the CI/CD part of Micro Focus ALM Octane but as demonstrated by the team who is providing the services, I see that the CI/CD could improve. When we check in the code, for the code snippet that has been checked in by a particular user, you need to open a separate file. When comparing Micro Focus ALM Octane to Jira, they have a separate window in which you can click on the ID and the code is visible in the snippet. It's a two-step process in Micro Focus ALM Octane and it's a single-step process in Jira. It's essential for the developers to think about this difference."
"We have some requests to beef up the manual testing abilities and the ability to report on testing progress. All the basics are there, but there's an issue of maintainability. For example... once you plan a test and it creates a run, more particularly a suite run, you can't edit the suite run afterward... That that is not realistic with how people work. Mistakes are made and people are humans and we change our minds about things. So the tool needs to allow for a bit more flexibility in that testing area, as well as some better widgets to report on progress."
"Currently, Micro Focus ALM Octane is considered an old-world tool in the industry and lacks the perception of being a new-age tool among its customers."
"I like their smart analytics; perhaps they should continue to expand and improve there because it's a fantastic start."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 47 reviews while OpenText ALM Octane is ranked 7th in Enterprise Agile Planning Tools with 38 reviews. JIRA Portfolio is rated 8.2, while OpenText ALM Octane 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 OpenText ALM Octane writes "Reporting engine, widgets, and dashboards are a huge plus, and powerful REST interface means we can interact with other tools". JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Project Server, Adobe Workfront and Microsoft Azure DevOps, whereas OpenText ALM Octane is most compared with Jira, OpenText ALM / Quality Center, Microsoft Azure DevOps, Rally Software and GitLab. See our JIRA Portfolio vs. OpenText ALM Octane 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.