"The combination of a highly flexible state machine together with a platform independent API enables possibilities to automate many steps that in many systems are manual."
"It can be adapted to any process flow and easily be integrated with other in-house tools using the ClearQuest API."
"The sprint tracking is really helpful and very convenient."
"The burndown chart is also helpful when it comes to reporting and allows us to know where we are going, especially during development."
"This solution focuses on lean methodology which we have found useful and it can also be used on any device."
"We do not have a lot of time for investigating new things, but Jira has saved us a great deal of time. It has a nice user interface and we can do a lot of things with it."
"The solution has been very stable overall."
"Everything is tracked in one place."
"Its visual display and ease of use are most valuable."
"The burndown charts help track projects."
"Lack of a modern web interface compared to other systems might discourage customers."
"Jira could provide more insight into sprints such as how did we perform in the last sprint compared to other sprints. It would be helpful to have metrics and a dashboard feature for others to see."
"It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free."
"There's been the odd amount of JIRA downtime (not self hosted) and sometimes tickets that can't be accessed."
"Ease of administration and customization. It is really clunky in this area."
"Could offer an improved user experience."
"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."
"An area for improvement in Jira is that it's not designed for test management. To use it for test management, you need an add-on or several add-ons, e.g. Xray or Zephyr."
"I manage the progress of the stories in an Excel chart with dates on work progress or thing to do. I don't like the progress or the stage changing from the stories in Jira."
Earn 20 points
IBM Rational ClearQuest is ranked 1st in Defect Tracking while Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 263 reviews. IBM Rational ClearQuest is rated 7.2, while Jira is rated 8.2. The top reviewer of IBM Rational ClearQuest writes "Tracks change requests, problems, and physical asset management. I would like to see data type for floating point numbers. ". 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 ClearQuest is most compared with IBM Rational ClearCase, HCL Compass and IBM Rational Synergy, whereas Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM.
We monitor all Defect Tracking 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.
