Try our new research platform with insights from 80,000+ expert users

Jira vs OpenText ALM Octane comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 8, 2024
 

Categories and Ranking

Jira
Ranking in Application Lifecycle Management (ALM) Suites
1st
Average Rating
8.0
Number of Reviews
267
Ranking in other categories
Application Requirements Management (2nd), Project Management Software (4th)
OpenText ALM Octane
Ranking in Application Lifecycle Management (ALM) Suites
8th
Average Rating
8.2
Reviews Sentiment
7.4
Number of Reviews
40
Ranking in other categories
Enterprise Agile Planning Tools (8th)
 

Mindshare comparison

As of November 2024, in the Application Lifecycle Management (ALM) Suites category, the mindshare of Jira is 23.5%, down from 23.9% compared to the previous year. The mindshare of OpenText ALM Octane is 6.2%, up from 5.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

Saroj Ekka - PeerSpot reviewer
Offers good repository integration, sprint board and easy to set up
There are some features and reports we need that are not there. For example, if I have to find out the capacity of the current sprint by user and compare it with the previous sprint, that visibility isn't there. We can know the capacity and what happened with the whole sprint, but not for an individual person to see where it's falling and how it's tracking. Report and analytics capabilities are important for a product manager. That visibility is important, so we use Jira. Some of the features are there, and I use my own Excels or other data things to compensate for that.
GeorgNauerz - PeerSpot reviewer
A stable tool for sprint planning, test management, quality management, and automated testing
I think the area of release management in the tool is an area of concern where improvements are required. In general, the connection between releases and scrum teams needs improvement, as it could be optimized owing to its linkages, making it very uncomfortable as soon as you have strong teams or scrum teams that work with different items over several releases. In future product releases, the solution needs to focus a bit more on the metric part. The product's dashboard is a metric for productivity and process control.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"In Jira, the integrations I have used so far are the repository integration, like when it gets added, or the integration with Confluence, which is good."
"The links between tickets are very valuable and the boards I found to be configurable and usable. The boards allow some level of extended configuration and they can be customized according to our project needs. Additionally, it is easy to use."
"This is a user friendly solution."
"Jira is very useful for project management for internal projects."
"There are a lot of different plugins for Jira. Unfortunately, we did not test so many and the big pain point for us is the rigorous handling and the roadmap of Jira. We have a portfolio and structure plugin and we have our story map plugin in Jira"
"We use Jira for project management and tracking."
"It improved communication, as it was a popular tool, and most people enjoyed using it."
"Internally we use Jira for our own implementations and capturing requirements and our customers are using the whole tool for the whole software development life cycle. They're using it for the full life cycle of the product."
"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."
"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 user experience is a lot better than any tool that I have used before. Overall, it is great. It has a smooth interface, which is very user-friendly. It makes it easier to work together and have more transparency and customization, which is very good."
"People really how easy it is to customize. In some previous tools, that has been very limited, or you had to know how to write code to do some of the customizations, or it was very confusing. Going back to the user interface, they've made the customization of the tool, the workspace settings, very easy for people to figure out and use."
"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."
"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."
"Its end-to-end traceability is one of the big advantages. Most of our agile projects work in a closed team structure. We are seeing what is the flow, where we are, and what is the project milestone. So, it provides end-to-end traceability and good visibility of project milestones."
"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."
 

Cons

"There's been the odd amount of JIRA downtime (not self hosted) and sometimes tickets that can't be accessed."
"There are some minor quirks, such as zero-point stories not appearing in the portfolio scope."
"I manage the progress of the stories in an Excel chart with dates on work progress or thing to do. I don't like the progress or the stage changing from the stories in Jira."
"I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice."
"If CI/CD is integrated with it, it would be better. I've used Azure DevOps before, and it's nice to have everything, such as CI/CD Repos and other things, integrated. Jira has fewer integrations. Azure DevOps has an easier interface, and it has got everything in one spot. I don't have to jump around in different applications."
"There needs to be an easier way to capture a few metrics. I wish there was an easy way for Jira to explain to me what has been added after the sprint has been done. Currently, it is a bit difficult for me to tell. In addition, when rolling over stories from one sprint to another, it is kind of difficult for me to find out how many story points were actually rolled over without going into Jira and doing an analysis. I wish Jira would somehow aggregate that information for me so I can easily report about it."
"Something I would like to see improved is the traceability feature. When you have a user story, if you can see all the test cases, it would be an improvement if you could see any design documents or any change management."
"The plugin management needs a lot of work."
"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."
"What could be improved in Micro Focus ALM Octane is its integration with Jira."
"Documentation is not clear."
"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 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."
"I like their smart analytics; perhaps they should continue to expand and improve there because it's a fantastic start."
"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."
"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."
 

Pricing and Cost Advice

"The standard package of Jira is for 100 users. They should offer more packages for other increments, such as 500 or 2,000. In my previous company, there was a free package that provided a minimal number of users."
"The price seems reasonable to me. It's very similar to Splunk."
"The license is yearly. It is a large, long-running program."
"We are on an annual license and could be less expensive."
"The price at the moment for Jira is okay. I'm absolutely not amused with the plans to try to drive us to the cloud or to other licensing models. For the very simple reason that we are a company in the defense sector where cloud is problematic in a number of the domains. We are now approximately 60 users and the new policy will actually confront us with an upscale to approximately 500 users. I find it unacceptable, and may potentially lead us to look for another solution."
"The tool's pricing is reasonable."
"I don't feel that price is an issue."
"I think the starter pack of three users, up to five users, is free. So you can try it out."
"Pricing is the weakest point. It is expensive, but the tool has plenty of features. The main problem we have is that the pricing is very high compared to some other solutions."
"The price of Micro Focus ALM Octane is too high compared to other solutions."
"The tool's price is extremely high."
"The cost of this product is very high."
"The solution has reduced our testing costs."
"The comparison is always with Jira, so the pricing of Octane is a bit on the higher side. But if you look at what you have to add to Jira, on the plug-in side, to have the same abilities you have with Octane, you're more or less even, or even ahead with Octane."
"In my opinion, it's good value for the price that you pay."
"It's pretty pricey, one of the most expensive ones on the market... The value depends on if you use all the features that it has. It comes with a lot of features. The difference between the license structure of ALM and Octane versus JIRA, is that you get everything with ALM and Octane... For JIRA, you buy the pieces one piece at a time."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Answers from the Community

HV
Apr 19, 2023
Apr 19, 2023
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.
See 2 answers
EB
Nov 16, 2021
Hello @Vishwa-Reddy, @GeorgNauerz, @Agne Gecevice ​and @reviewer1154316, Can you please help @Harshal Vora ​with their question?
reviewer1933914 - PeerSpot reviewer
Apr 19, 2023
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. 
 

Top Industries

By visitors reading reviews
Educational Organization
50%
Manufacturing Company
8%
Financial Services Firm
7%
Computer Software Company
6%
Financial Services Firm
28%
Manufacturing Company
11%
Computer Software Company
11%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Is Jira better or would you go with Micro Focus ALM Octane?
Hi Netanya, Basically , it all depends on the use cases for your environment and the business needs. Hope the below data may be relevant to you for identifying your needs and deciding on the approp...
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
What is your experience regarding pricing and costs for Jira?
The product is quite expensive. It costs approximately 1.2 million rand per year. It's a fixed price, depending on the modules that you get. You have specific tools, that's what you pay for. I rate...
What do you like most about Micro Focus ALM Octane?
The platform's most valuable feature is pipeline integration or continuous integration services.
What is your experience regarding pricing and costs for Micro Focus ALM Octane?
The tool's price is extremely high. When I was using Micro Focus, there were ten licenses, costing around 1,38,000, which was outrageous.
What needs improvement with Micro Focus ALM Octane?
The tool's price is high, making it an area where improvement is high.
 

Comparisons

 

Also Known As

Jira Software
Micro Focus ALM Octane, Micro Focus Octane
 

Overview

 

Sample Customers

Square, Nasa, eBay, Cisco, SalesForce, Adobe, BNP Paribas, BMW and LinkedIn, Pfizer, Citi.
Orange, Airbus, Haufe Group, Kellogg's, Claro, Bon Secours, World Wide Technology
Find out what your peers are saying about Jira vs. OpenText ALM Octane and other solutions. Updated: October 2024.
816,406 professionals have used our research since 2012.