We performed a comparison between Atlassian ALM and OpenText ALM Octane based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature is the Scrum board."
"The main power of this tool is the integration between the different products of the Atlassian suite. We have good integration with work management with Java. This is the major strength from this provider."
"This solution fits very well into our agile product management environment."
"It is a very stable tool. The tool has been in the industry for so many years. Stability-wise, I rate the solution a nine out of ten."
"It's brought our entire team into a single tool. We're all looking at the same real-time data. Our project management office has been able to set up dashboards for individual teams, and do comparisons by teams, of integration, and cross-team integration, burn-up, burn-down, and cumulative flow..."
"Current version of the solution is fairly stable."
"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."
"The platform's most valuable feature is pipeline integration or continuous integration services."
"We like Micro Focus ALM Octane because its performance is okay, and its stability is okay, so we use it a lot. The platform is easy to use."
"On the user side, what I like a lot is the reporting capabilities. There's no tool, to my knowledge, that gets anywhere close to Octane at the moment when it comes to the reporting capabilities. I can do everything with the reporting. There's nothing missing. I have all the options. I can create graphs, including graphs of several types and looks."
"The way testing is closely tied into the product Backlog has made it more intuitive, or easier to manage the relationship between building out an application and testing it. In other tools, that is more segregated. The way it's designed in Octane, people have said it makes more sense to them, and that it's easier for them to understand their data and to maintain and test their solutions."
"The automation for scheduling software and doing software tests should be simplified because it's complex and too rigid."
"There is room for improvement in the high-level project management."
"The reports are not really customizable, which is something that they should improve on."
"It could use just some small improvements. I would like additional features, like planning features, user story mapping, or connection to collaboration tools."
"The reporting is lacking from a requirements matrix and a traceability perspective."
"Updating items, sorting, bulk updates—these things could have a bit more flexibility, but it's still possible to do them."
"When I manage projects that are being created in ALM, I have a standard template, but I don't have a template for them in Octane. I literally have to create the project from the ground up every time, which for an administrator, is a nightmare solution"
"Globally, I don't see many major points of improvement. It's mostly plenty of little things, and it's weird to me that they are not in the product yet. They are really details, but they're annoying details... Today, in the tool, we've got plenty of assets we can handle, like requirements, user storage, defects, tasks and so on. And to all of those elements, we can add comments. We can add comments to any asset in Octane but not to tasks. It's just impossible to understand why it's not available for the tasks because it's available everywhere else. Similarly, for attachments, you can attach files absolutely everywhere except on automated runs, which is, again, awkward. I don't understand why on this element, in particular, you cannot do it. It's little touches like that."
"The elements in filtering need to be improved, meaning the number of filters I can use in widgets or in the grid views in parallel. There's a limitation which bothers a lot of our users. Filtering in text, or having a complex filter is limited. In a given field, for example, I can use a filter only once. I cannot say, 'Include the values 1, 2, and 3, and exclude value 17.' This is not possible but we have requested it often."
"I think the area of release management in the tool is an area of concern where improvements are required."
"Because JIRA is a leading tool for both development and requirements management - everybody is using JIRA - I'm pretty there will be a use case where people are trying to connect between ALM Octane and JIRA. The back-end configuration of the synchronization with JIRA could be simplified. The architecture is really complicated. We required a lot of machines to build the cluster and the configuration was not really clearly described within the documentation. This may have something to do with the fact that the software is pretty new."
Atlassian ALM is ranked 17th in Application Lifecycle Management (ALM) Suites with 6 reviews while OpenText ALM Octane is ranked 7th in Application Lifecycle Management (ALM) Suites with 38 reviews. Atlassian ALM is rated 7.6, while OpenText ALM Octane is rated 8.2. The top reviewer of Atlassian ALM writes "Scrum board feature is highly valuable and handles different user volumes". 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". Atlassian ALM is most compared with Jira, Microsoft Azure DevOps, IBM Rational ALM, Polarion ALM and TFS, whereas OpenText ALM Octane is most compared with Jira, OpenText ALM / Quality Center, Microsoft Azure DevOps, Rally Software and GitLab. See our Atlassian ALM vs. OpenText ALM Octane report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites 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.