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.
"We can integrate a lot of tools with the solution."
"The most valuable feature of Jira is the reporting feature, which allows us to track our team's tasks."
"The most valuable feature is the full integration between Work management, Source code management, and Test Automation."
"Overall, it is very intuitive. It is so lightweight and easy to use. It is easy to manage our product backlog and user stories, and it produces great reports."
"Offers great multiple reporting charts."
"The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations."
"You no longer need to email people. You can mention them right in Jira and have conversations there."
"Offers a common language set so we can bring people into projects and get them up and running almost immediately."
"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."
"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..."
"The filtering options are very good once you learn them. The document reports are also valuable. You can create reports in Word and PDF formats. That's very useful."
"Current version of the solution is fairly stable."
"The most valuable features of the solution are its ability to manage test scenarios, test results, and test automation, which are its primary functionalities."
"The most important feature is the integration among all the different features in just one tool: Agile management system, requirements management system, test management, defects management, automatic test execution. Really, if you're looking at other tools, you will never find all that integrated into just one tool with all the traceability, with all the elements in just one place."
"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."
"It's more streamlined because we have it all under one umbrella. And once the business requirements and rules have been created, we can do test cases and apply them to the business rules."
"Stability is an area of concern and it needs improvement, otherwise, it's a good product."
"If Jira would be interested in offering a SharePoint version, it would be beneficial."
"For me, the solution is too complicated as it has too many features. It would be nice if they could streamline things."
"Sometimes, we create the same bug with two or three different Jira tickets in my company, which leads to duplication, making it an area where improvements are required."
"We'd like to see more collaboration tools implemented within the product itself."
"There is a difference between their cloud and their server versions. The next-gen project, which is an advanced feature that allows you to visualize the road map of your delivery over multiple products and over time, is not available yet for the sever version. It appears there in the list, but it's still not right. I've tried to use it many times and I am watching the device show their tracker, but it seems they intentionally want this to increase the utilization of the cloud instead of the server. It is really a nice feature and it's a shame that we don't have it."
"Slow when integrating with other components."
"If they want Jira to be the one-stop shop of the view of all of your deliverables, not just from a defect tracking perspective, but also from a requirement perspective, a code perspective, and a testing perspective, it needs to pull out more data and work better as an integration tool."
"The limitation of Octane is that we can't do a release outside of the sprint. We can only plan the release in the sprint. With Agile and JIRA tools, we can plan the release outside the sprint and do a global release of all the projects from the sprint."
"Improvements could be made by way of additional integrations across the lifecycle."
"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."
"The reporting is lacking from a requirements matrix and a traceability perspective."
"Though Micro Focus ALM Octane doesn't have much of a bug, it lacks integration with some solutions. For example, my company has fairly new software, but it can't be integrated with Micro Focus ALM Octane, so integration with other software, particularly with less popular software, could be improved. Micro Focus ALM Octane also requires a lot of resources during its setup, and I find this another area for improvement. An additional feature I'd like to see in the next release of Micro Focus ALM Octane is the ability to customize the interface, especially when doing a manual test."
"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."
"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."
"Security and security management, meaning the integration of the security, could be enhanced. We know about Fortify, but it would be better to have security features in the original Octane platform without the need for another solution or another application."
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.