We performed a comparison between IBM Rational ALM and Jira based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The tools for requirement capture we have found very useful."
"At the same time, if you're working from the architect or the designing team you, it's quite easy to manage the resources online."
"The solution is customizable."
"The planning feature is rich with Scrum concepts: Sprint, Sprint retrospective, the rules in the Scrum framework."
"It's easy to use."
"We have something called the GC (global configuration), which is a unique feature compared to any other competitor we have in the ALM space."
"You can customize the board according to your needs."
"I would rate the stability of this product a nine out of ten."
"This product provides you a good view of the status of your projects."
"The solution is stable and reliable."
"The layout, workflow, automation, and metrics are helpful in Jira."
"We have found the structure, functionality, and how Jira handles the tickets most valuable."
"The roadmap feature and the ability to integrate with Power BI are probably the most valuable features in it. It is a great solution. I absolutely love it. It is a tool that was designed for project management, and it has been awesome to work with it so far. I also love Confluence."
"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."
"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 most valuable feature of this solution is the source linking on the commit level to git."
"The interconnectivity between packages is a major support problem and can be improved."
"The stability of this solution can be improved."
"One of the complaints from users is that they have to click buttons too many times for just a simple task. Changing this would lead to a better user experience."
"Some improvements to the user interface (UI) would be helpful, such as exposing more services to make it easier to customize to the needs of each customer."
"The features should be more intuitive. If I'm looking for something, its location should be easy to locate."
"The solution can improve in the development area and the customized applications."
"The directory designer manager is uncivil. The design manager is clearly really unstable."
"The GUI is a little bit outdated."
"I'd like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile."
"What I don't like is that perhaps there are not so many different apps that can add value over the management side of the product."
"A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time."
"Slow when integrating with other components."
"It would be good if we can grant access based on the roles. This is something that Jira can look into. Currently, anyone with Jira access can access everything. Being able to define access based on the roles will give us more flexibility in managing Jira. I would like to have more reports in Jira. Currently, eight or nine reports are there. You can use Screen Test to get more reports or data from Jira, but you will have to get more add-ons, plug-ins, and stuff like that. It would be good if they can increase the number of reports."
"Could be more intuitive."
"Tracking is important but the built-in features don't meet our needs."
"It can have a more high-level view of portfolios. It has quite detailed views, but I would like a high-level view of portfolios. We want to integrate Jira with Microsoft Active Directory, and I don't know how easy or hard it is going to be. I don't know if Jira supports this. We are starting that integration in the last quarter of this year. I hope to find all the required tools for this integration."
IBM Rational ALM is ranked 11th in Application Lifecycle Management (ALM) Suites with 17 reviews while Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 reviews. IBM Rational ALM is rated 7.2, while Jira is rated 8.2. The top reviewer of IBM Rational ALM writes "A complex deployment that is not stable, but is cloud-based". On the other hand, 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". IBM Rational ALM is most compared with Codebeamer, Microsoft Azure DevOps, Polarion ALM, PTC Integrity and Atlassian ALM, whereas Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM. See our IBM Rational ALM vs. Jira 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.