We performed a comparison between Codebeamer 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."It is a stable solution."
"Codebeamer's API-based integration and many other integration aspects with other solutions are very powerful."
"One of the most valuable features of Codebeamer is its strong performance."
"The platform provided the flexibility to expand our business processes, accommodating or altering them to suit the requirements of a changing environment."
"The traceability is so simple that I don't need to do any additional configurations related to traceability."
"The solution easily replaces IBM DOORS, which no longer offers maintenance in China."
"CodeBeamer provides full traceability, excellent collaboration, regulatory compliance, and instant reporting with its holistic approach from requirement management to testing."
"You can track the metrics in the Agile dashboard very easily."
"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."
"The platform's most valuable feature is pipeline integration or continuous integration services."
"Octane creates a gentle approach to Agile-based projects."
"The most useful feature of Micro Focus ALM Octane is the dashboards, they are easy to use."
"We looked at all the market-leading tools, but we did not find anything quite as comprehensive as ALM Octane. When I say comprehensive, it's not just a single tool for Agile planning, backlog management release, sprint planning, etc., but it also has a built-in, comprehensive quality management module. It also has pipelines where we can hook up with our DevOps ecosystem/toolchain."
"With an Octane project, we have our automation, our requirements, our tests, our pipeline into build-and-deploy, and the ability to identify problem areas. It makes things quicker because it's more along the lines of an automated process."
"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’s easy to set up."
"It would be helpful if Codebeamer's overall processing and integration with software like Jira could be improved."
"The search and replace feature within the tool itself could be improved."
"Usability needs to be improved."
"The product's UI is an area of concern where improvements are required."
"It's still a fairly new tool that lacks maturity right now."
"Certain areas in Codebeamer could be improved, like addressing small issues, glitches, or bugs."
"I would like to see more, easily trackable reports."
"During migrations from other platforms to CodeBeamer, there have been instances where we encountered issues that required redoing certain tasks."
"I like their smart analytics; perhaps they should continue to expand and improve there because it's a fantastic start."
"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 reporting needs to be improved and allow for customization. I want to build my own widgets, but I don't want to use the ones already in the system. I want to build mine from scratch."
"The cluster architecture that we implemented was server to server communication: Octane application to Elasticsearch and Elasticsearch to another Elasticsearch service. Recently, we found this is a security gap. The Octane application is interacting with Elasticsearch server, but that was missing from the requirements and prerequisites in the setup. The Micro Focus team has not given advice on how to implement authentication-based communication between Octane to Elasticsearch, and we found it as a gap later, then our security team asked us to fix that gap. So, there was a lot of time spent on rework."
"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"
"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 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."
"Also, while there is a Requirements Module in Octane, it is very plain. It's okay to have some requirements described there, but it's not really following the whole BDD approach. I would like to have more features for requirements in there."
Codebeamer is ranked 9th in Application Lifecycle Management (ALM) Suites with 10 reviews while OpenText ALM Octane is ranked 5th in Application Lifecycle Management (ALM) Suites with 38 reviews. Codebeamer is rated 7.8, while OpenText ALM Octane is rated 8.2. The top reviewer of Codebeamer writes "Has good technical support services, but the migration process needs improvement". 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". Codebeamer is most compared with PTC Integrity, Polarion ALM, Microsoft Azure DevOps, Jira and OpenText ALM / Quality Center, whereas OpenText ALM Octane is most compared with Jira, OpenText ALM / Quality Center, Microsoft Azure DevOps, Rally Software and ServiceNow Strategic Portfolio Management. See our Codebeamer 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.