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 Atlassian, Microsoft, Nutanix and others in Application Lifecycle Management (ALM) Suites.
"The sprint tracking is really helpful and very convenient."
"The dashboards are useful."
"A most valuable feature involves the ability to customize the entries and to update them quickly."
"When we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool."
"The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on."
"The timeline management is great."
"The solution offers a lot of plugins."
"I've never had a bug or a bug message that I needed to open a ticket for."
"The most valuable feature of Micro Focus ALM Octane is the reports. We are able to do customization."
"The most useful feature of Micro Focus ALM Octane is the dashboards, they are easy to use."
"A valuable feature is the pipeline, so that we can now connect to Jenkins and then have all the results from testing, from external, in the tool, so that we can see the whole approach from there. Also, We can work with labels so we have better filtering solutions than in ALM. And it's much smarter and leaner to use than ALM."
"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."
"It is a very stable solution. Stability-wise, I rate the solution a ten out of ten."
"The platform's most valuable feature is pipeline integration or continuous integration services."
"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."
"I like the fact that you can use it on top of Jira."
"What I like most about Rally Software, in terms of using it for the agile process, is that it's clear, useful, and user-friendly. I also like that it has every field you can use for the Scrum process."
"Helps me plan an estimate of how soon or how far out we'll be able to deliver something."
"The most valuable feature is actually creating a field within there for architectural review. So when teams are struggling or have questions on the architecture or strategy that they take, they can actually flag that particular story, release, or project. Those can then be reviewed by the architecture team and the teams actually get additional information on how to course-correct, build on the architecture that we're trying to build throughout the organization, and get over road blocks much quicker."
"My teams uses it for their daily agile management. They describe their user stories and track the progress of their projects."
"We can work better and at a higher quality, than we were able to before."
"When it comes to the valuable features of Rally Software, it excels at burn-down charts, burn-up charts, and road mapping once it's set up. I particularly appreciated the new feature for releases and road mapping, which worked exceptionally well."
"CA Agile Central helps the entire organization run like one powerful team."
"It helps with getting the alignment between strategy and execution for the product teams, all the way down to the delivery teams."
"Integration with some of the automation tools could be improved."
"I want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting."
"Sometimes the solution doesn't communicate well with other platforms. It's quite difficult to integrate things and make the data flow from A to B, to Jira, and then back to other areas."
"I'm mostly focusing on the requirements traceability with my thesis, the integration could improve for other tools. The companies are not only using Jira. For example, for the test cases or for the documents templates, we are using Polarion and we have been having some integration issues."
"Test case management could be more user-friendly. When we add or update test cases, there should be a better way to organize them within the dashboard."
"In terms of improvement, I think Jira (Jira Agile, specifically) can be made more user-friendly. Most of the time, when people are somewhat used to the process, they find it easy to work with. But the thing is, if I want to create a sprint, I'd like the ability for it to come out like a kind of board or something like that. For example, they could offer something like a wizard for users who want to quickly create a sprint on the spot with a few clicks. I think that could be useful."
"The dashboard reports can be improved. Its dashboard reports are good, but you cannot have complex reports. They are currently very basic. For instance, we can only choose two columns for a dashboard, so it is not friendly enough."
"I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA."
"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."
"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."
"The Requirements Module could be better, to build up a better requirements process. There's a huge improvement from ALM.NET to Octane, but it's still not really facilitating all the needs of the product owners, to set up their requirements in Octane."
"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."
"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."
"Updating items, sorting, bulk updates—these things could have a bit more flexibility, but it's still possible to do them."
"It would help us if ALM Octane got FedRAMP-certified, so our government departments could use the cloud solution. That way our external consultants could access it. We've created a URL to get to it, but if it were FedRAMP-certified and service and had support in the continental United States, that would be better."
"Octane, from an administration perspective, is very limited. The application is improving with each release but what is missing is the ability to manage users and workspaces. I would also like "usable" reporting for more than a few workspaces. Also still missing is the ability to copy a workspace or get data in or out, except for limited REST calls."
"It's a bit cumbersome to manage the Project Picker. As we sunset teams or projects close out - but we still have test cases tied to those teams or projects that are being used in other spaces - we have this monstrous list in the Project Picker that becomes really difficult to manage and find, and we can't clean that up ourselves. It would be nice if it was easier to do that and not lose your history."
"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."
"In terms of improvement, perhaps some more metrics. If they could add some additional, that would be cool."
"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."
"I think there is a missing link with the development activity. Some developers are pushing in new versions of the code, but you cannot make the link from the user story to a specific application version."
"As it is right now, it does not support automation of the quality assurance process. It just supports manual testing."
"More importantly, we are seeing internal challenges from Atlassian because of their highly integrated suite that enables further automation and centralization of activities that are also highly necessary – messaging notifications cued off builds, collaboration on Solution Architecture Documentation, etc."
"The product needs to have more integration capabilities."
