We performed a comparison between Jira, OpenText ALM Octane, and Rally Software 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.
"This solution assists us with being able to quickly and easily start sprints and keep accurate track of them, including billing using a time-tracking add-on."
"The configurable workflows and boards make it easy for us to execute and oversee our own unique process."
"In terms of product management, Jira increases productivity and visibility into the product. Those are the top benefits this tool provides to the team. Also, it's accessible to the executives and whoever wants to sign on to Jira to see what's going on."
"Integration is good."
"It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days."
"The flexibility to create different flows is most valuable."
"The timeline management is great."
"A very comprehensive product; easy to set up and is very user-friendly."
"The integration points are very good. Octane gives us a window not only into our manual testing, but also our automation testing and our performance testing. We can see all results from all three streams of testing in one place."
"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."
"It’s easy to set up."
"The solution natively supports Agile-Waterfall hybrid software development at an enterprise scale. This is very important to us. Because even though the company wishes to go Agile, we still have projects which follow a Waterfall methodology. In order for us to accommodate both, we needed some sort of hybrid system. Because if we are using a fully Agile system, then the reporting might not be correctly extracted."
"Octane creates a gentle approach to Agile-based projects."
"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."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"It's a good platform to keep track of all the user stories across all projects. So rather than having one off Excel spreadsheets with all of the requirements, it is a good place to have all of that."
"It is very stable. It has been on the market a long time."
"Tech support is very responsive, helpful, and available."
"The visibility it brings to the plan, the ability to capture tasks, and trace them all the way through the life cycle. Providing that visibility helps both me and the team, or teams, to be able to understand where we are in the development process."
"Ease of use - I don't even know when a new release is coming and I don't need to because it's so easy to use what's new."
"The effect of these kind of tools drives the way you organize things. It helps you shape the way you flow."
"The most valuable feature of this solution is the Kanban board."
"CA Agile Central helps the entire organization run like one powerful team."
"Out-of-the-box reporting is limited. It would be helpful if more customisation was possible."
"There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported."
"Nowadays, many organizations are moving toward the Objectives and Key Results (OKR) framework, and this is something that Jira should be able to accommodate."
"For a non-technical person to use, Jira is not intuitive."
"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."
"Lacks some common building block approaches to certain things."
"The support could be improved."
"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."
"Documentation is not clear."
"What could be improved in Micro Focus ALM Octane is its integration with Jira."
"Technical support can be slow."
"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 biggest problem with ALM Octane is that it's very complex, so it's difficult to use and scale."
"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."
"Updating items, sorting, bulk updates—these things could have a bit more flexibility, but it's still possible to do them."
"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"
"I would like for workspace admins to be able to hide projects in the Project Picker and not lose any historical data; make them invisible to certain users, visible to certain users, depending on permission sets. That would be lovely."
"The product needs to have more integration capabilities."
"The stronger CA can get on dependency mapping the better. That's the biggest hiccup. As you're setting up your features, they should make it easier to flag the dependencies, either across features or across projects. Then you're more set up for success."
"We would like more meaningful, customizable dashboards."
"More customization capabilities would be helpful. Providing a little bit more structure around how the system should be set up in terms of the hierarchy structure might be helpful as well."
"I think the interface could be a little bit more visual and less wordy. Right now, it seems like it's just a lot of text on the page. In other ticketing systems where it's more visual, you can see more of a flow. But in this one it's more just a list of tasks. I would like to see that a little bit better, especially considering it has so many great organizational features, like child tasks, different artifacts. It would be great to see it presented more appropriately."
"The navigation within the tool sometimes is a little tricky for me. I'm sure with more use, more practice, I'll become accustomed to it, but some of the things just aren't intuitive."
"We want Rally to generate OKRs, to allow teams to record the OKRs, and then the OKRs can be mapped to the epics and there is organizational alignment."
