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."I would rate the stability of this product a nine out of ten."
"The integration with Git works well."
"The most valuable feature is the reporting of the CPU usage on the dashboard."
"It's easy to use."
"You can customize the board according to your needs."
"It helped us contain critical things, like source code and several documents, which is very important to us."
"The solution is customizable."
"The tools for requirement capture we have found very useful."
"I can use Jira Query Language (JQL) to write queries to see the stories that are there for the current sprint. I can also sort them by assignment. I also use Jira is for burndown charts, which give an indication of how efficiently the squad is performing. I also use the Active Sprints function and a feature called Planning Poker."
"Jira queries can be used for different types of deployment automation processes."
"It's very flexible. I can define workflows and custom fields and dependencies between issues and projects. And every project can have a custom configuration with my fields, my names for fields, my validations, and my workflows. It's very customizable."
"The most valuable features are that it is good for tracking the issues and it provides for the usage of Confluence."
"The solution's most valuable features revolve around the dashboard view, which has a burndown chart indicating progress."
"The solution offers up great transparency that makes it possible for everyone inside the departmental organization to see what's happening."
"I like seeing which tickets are open and what our response rate is. They have a lot of good metrics in their system to see what's going on."
"The most valuable feature is Jira Align, which is a plugin that helps you to understand the progress that is made against each epic."
"I would like to see better reporting features. The out-of-box reporting is - I don't want to say limited - but the focus is on the Scrum and Sprint reports. We need more reporting features regarding the history of the work, tracking it more deeply."
"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."
"I think nowadays people are getting into Jira and other tools. What is happening is, this solution is becoming more traditional, whereas Jira and other tools are more attractive for the new users to learn and start using because of the graphical interfaces."
"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 stability of this solution can be improved."
"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 product must be more user-friendly."
"The only thing that JIRA doesn't for us is release management in a way that I can create a list of versions easily."
"Workflows can be improved. We don't use workflows because we can't handle that much complexity. Its interface could be more intuitive for workflows."
"The automation feature needs to be more user-friendly."
"Sometimes the screens can be a bit too busy. There's often a lot of information on the screen. I think paring things down and applying some UX improvements might enhance the look and feel of the interface."
"I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira."
"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."
"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."
"In JIRA, it's a bit complex in terms of what advanced search queries we use. Sharing them is also a problem. Because TFS is on the cloud, we can easily save that query and share it with our team members."
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.