Great for what we need
December 28, 2017

Great for what we need

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with JIRA Software

We use JIRA to track defects, and the resolution of those defects, across hardware and software platforms. 95% of the engineering organization uses it in one way or another, although the use cases differ.

We use it to track all defect discovery, investigation, implementation and retest. We also use it as a way to facilitate discussion of the defects, and determine priority and resource assignment across the organization.

Furthermore, its ability to generate reports and dashboards that are accessible, usable and understandable to C-Suite executives is a great tool to keep our engineers focused on solving defects, and letting the tool handle the reporting side of things.
  • Its ability to generate reports and dashboards that are accessible, usable and understandable to C-Suite executives
  • Its ability to integrate with other tools through the use of plugins and add-ons (including source code repositories, a big one for use)
  • Its ease of use - new hires don't generally need to be trained at all, they pick up the right way to use the tool within their first week
  • Some reporting needs the ability to be more customized. For certain reports, we still have to export data to Excel...which is a hassle
  • Some features are very software development-centric. We use JIRA to track hardware and software defects, and some of the hardware defect tracking feels shoehorned in
  • The default behavior is to email any user tracking a defect when anything happens. In addition, users get added to the tracking list when they perform any actions on the defect. These two combined means that many users get overloaded with JIRA emails
  • The reporting has absolutely saved the engineering staff time
  • Teamtrack
We used teamtrack prior to JIRA, and it was a very antiquated solution in comparison . It did not interface well with our other software, ran poorly in modern browsers, and was expensive. JIRA solved all those issues, and gave our company a much better overall solution for defect tracking.
In a software-centric development environment, especially if COTS source code management is used (Rhodecode, as an example) JIRA shines. We, for example, are able to use it to track defects through implementation down to the specific line of code that changed in order to fix the defect. This means that reviewing how defects were fixed after the fact is very easy.