We performed a comparison between Atlassian ALM, Jira, and OpenText ALM Octane based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Atlassian, Nutanix and others in Application Lifecycle Management (ALM) Suites."The main power of this tool is the integration between the different products of the Atlassian suite. We have good integration with work management with Java. This is the major strength from this provider."
"This solution fits very well into our agile product management environment."
"The most valuable feature is the Scrum board."
"The most valuable feature is working with sprints and having the ability to create sprints."
"For QA, the most interesting for me are boards, backlog, and filters."
"Kanban board: The board is easy to use and visually impressive to non-IT users, who found it easy to relate to."
"It includes by default all the necessary tools for a project manager to work and make their work more efficient."
"I've never had a bug or a bug message that I needed to open a ticket for."
"Jira offers tools for managing projects using Agile methodology. I think it is good to encourage the development team to use Jira, so that the organization benefits from the proper execution of projects on time. Basically, it helps our organization to execute in a better way."
"It handles all of the issues that we need it to do."
"Its integration with Bitbucket, Confluence, and other things is most valuable."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"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 platform's most valuable feature is pipeline integration or continuous integration services."
"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."
"Octane creates a gentle approach to Agile-based projects."
"Backlog management is the most valuable feature. This was a capability that was missing or difficult to achieve in ALM Quality Center."
"The most valuable feature of Micro Focus ALM Octane is the reports. We are able to do customization."
"The key feature is the usability. It is fast to learn and easy to use. It's very intuitive to work with. Most of the important functions are available via a few clicks, compared to other tools where I have to open a sub-menu and then a sub-menu and another sub-menu, and then press a button."
"The reports are not really customizable, which is something that they should improve on."
"There is room for improvement in the high-level project management."
"The automation for scheduling software and doing software tests should be simplified because it's complex and too rigid."
"Scripts should be more readily available for implementing projects."
"There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported."
"The Jira dashboards could be more useful. The dashboards have good widgets but the comparison of data over time or extraction of trends from the data is not easy."
"Ease of administration and customization. It is really clunky in this area."
"The sprint-related graphics need to be improved."
"It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins."
"The stability could be improved."
"It should have Behavior Driven Development (BDD). There should be an option to add macros to help with that. A lot of people are using it now, and it would be nice if there was a way in there to be able to generate the BDD of commands whenever you're creating a story."
"Development of extensions or connections to GitHub actions could be better. Better integration with Azure DevOps would also help."
"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."
"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."
"There are some challenges when we want to integrate the tool with other products, and it takes time for a team to figure out how to do it."
"We have some requests to beef up the manual testing abilities and the ability to report on testing progress. All the basics are there, but there's an issue of maintainability. For example... once you plan a test and it creates a run, more particularly a suite run, you can't edit the suite run afterward... That that is not realistic with how people work. Mistakes are made and people are humans and we change our minds about things. So the tool needs to allow for a bit more flexibility in that testing area, as well as some better widgets to report on progress."
"The biggest problem with ALM Octane is that it's very complex, so it's difficult to use and scale."
"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."
"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."
