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 do not have a lot of time for investigating new things, but Jira has saved us a great deal of time. It has a nice user interface and we can do a lot of things with it."
"The most valuable features are the customized Dashboard, Sprint Planning, and Automatic Notifications."
"The most valuable feature is working with sprints and having the ability to create sprints."
"Provides good output and is user-friendly."
"Kanban board: The board is easy to use and visually impressive to non-IT users, who found it easy to relate to."
"The most valuable aspect of this solution is its ability to connect everything together."
"Our company follows the Agile methodology for software development, and this product is one of the best tools for companies that do so."
"It has an easy UI that can easily plug-in to every level."
"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."
"Octane creates a gentle approach to Agile-based projects."
"It’s easy to set up."
"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."
"I like the fact that you can use it on top of Jira."
"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."
"An improvement on previous versions because it comes as preconfigured as possible."
"The interface is user-friendly."
"The solution should be more user-friendly and include integration with different tools."
"In Jira Cloud, integration with Excel is missing. Previously, I could import our Excel files into Jira, and I could also download a big Jira report in the Excel format, but now, it needs to be manipulated after that, which is not good. It looks like they've done that on purpose, but I don't understand the reason for it."
"I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira."
"Its search and reporting can be improved. They are already nice, but they can be further improved."
"The features are not intuitive. It would be good if there were templates."
"This solution would be improved with the inclusion of integration with SVN, and auto-sync with the build release number."
"It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free."
"Lacks some common building block approaches to certain things."
"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."
"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."
"Development of extensions or connections to GitHub actions could be better. Better integration with Azure DevOps would also help."
"The biggest problem with ALM Octane is that it's very complex, so it's difficult to use and scale."
"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."
"I like their smart analytics; perhaps they should continue to expand and improve there because it's a fantastic start."
"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"
"They don't support all IDEs yet. We have Visual Studio code, which is not supported, and loved by our developers. This integration is missing. We also had to do our own in-house integration with the Confluence. That is also something that they could add."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 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.