We performed a comparison between Jira and Micro Focus Alm Octane based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Based on the parameters we compared, Jira is a bit ahead of Micro Focus. Our reviewers found Micro Focus to be more complex to install and to have weaker security integrations. Its price point is more pleasing than Jira’s however.
"One of the most valuable features is querying because the jQuery function is very good. Additionally, we can create good designs very easily."
"Perfect for keeping track of large amounts of bugs, tasks queries and releases for fixes."
"The most valuable aspect of this solution is its ability to connect everything together."
"The dashboards are useful."
"A very comprehensive product; easy to set up and is very user-friendly."
"It's an open-sourced product that is easy to customize."
"Jira has a good reporting system. It also has an API, so we can do all sorts of reporting."
"I like the test cases in Jira. The orange dash items view was great, and I like the features and layout of the data. It's quite different, and people are now getting their items so quickly."
"The defect management gives us full-fledged capabilities for handling defects, including capturing the details of the defects and even screenshotting the defect cases. The defect management is comprehensive."
"There are a lot of predefined reports. We can attach additional reports for users, like who worked on what defect and when, as well as what is the status of the release compared to the previous release. It is really endless. All the data is really linked together. Then, if all the data is linked together, there is an option to prepare reports out of it. We are very impressed with its reporting capabilities."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"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."
"Octane creates a gentle approach to Agile-based projects."
"Current version of the solution is fairly stable."
"Backlog management is the most valuable feature. This was a capability that was missing or difficult to achieve in ALM Quality Center."
"The interface is user-friendly."
"So at one point in time, they did a huge UI upgrade. At that time, I felt like they had changed something, so it was hard to figure out. Now that we are habituated, it's not an issue now."
"Jira is a project management tracking tool, and it would be great to see integration with the source front or Azure DevOps, etc."
"The tool should improve its pricing."
"What could be improved is the migration between the testing and production environments. This could be automated somehow as the manual transfer of certain workflows and functionalities is very time consuming right now."
"Ease of administration and customization. It is really clunky in this area."
"The biggest complaint industry-wide about JIRA is they need to purchase additional extensions, such as reporting automation. If they could provide some additional extensions from the initial purchase it would be a huge benefit."
"We have gone through several version changes and some of those changes have not been intuitive. There was a learning curve and we had some complaints internally about the changes, such as the new interface."
"There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported."
"There's a trend in our requests to have the ability to export data, en masse, out of Octane. There are capabilities within Octane to export data, but there are specifics around test suites and requirements and relations, as well as certain attributes, that we would like to be able to export easily out of Octane and into a database or Excel."
"The solution should improve by adding scrum board-like functionality."
"We've only had a few stability issues. Generally, we have issues following any deployment they do, so if they do a deployment on a Sunday, then we may have a couple of issues on a Monday or Tuesday."
"It would help us if ALM Octane got FedRAMP-certified, so our government departments could use the cloud solution. That way our external consultants could access it. We've created a URL to get to it, but if it were FedRAMP-certified and service and had support in the continental United States, that would be better."
"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."
"I would like to see the mobile testing improved so that we can simply select a mobile device, then specify what parameters we want, and the testing will be run based on that."
"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."
"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."
Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 259 reviews while OpenText ALM Octane is ranked 5th in Application Lifecycle Management (ALM) Suites with 38 reviews. Jira is rated 8.2, while OpenText ALM Octane is rated 8.2. The top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". 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 is most compared with Microsoft Azure DevOps, IBM Rational DOORS, Rally Software, Polarion ALM and TFS, whereas OpenText ALM Octane is most compared with OpenText ALM / Quality Center, Microsoft Azure DevOps, Rally Software, GitLab and Codebeamer. See our Jira 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.
ALM Octane integrates easily out of the box with Jira,
additionally, once you DevSecOps users are onboard to Octane,
they will realize Octane does more, so they can reduce their dependence on Jira.
Several of my customers have come to this realization.
Octane is an Enterprise solution, but Jira is not.