House of Organization
March 07, 2018
House of Organization
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with JIRA Service Desk
JIRA is primarily used as our bug database for issues that are found while testing our software. It houses our 20+ projects and works great for housing our bug tickets in a very organized manor. JIRA is also used for tracking the development of the current sprint that the engineers are working on. JIRA has some great features and links to other software tools such as TestRail and Confluence.
- The organization that we are able to create with JIRA is invaluable between grouping tickets via build numbers or creating central location for information on a development sprint.
- Using JIRA as a tool to create a task orientated ticket that has instructions and information that can be given to a third party contractor in order for them to run a detailed test plan on your software.
- JIRA does have a tendency to make visual changes to the UI more often than is wanted or warranted. It does seem like just as you get used to one UI a new one is available.
- When searching tickets for a specific type of issue it can be difficult to find what you are looking for unless you are very specific.
- If used incorrectly the workflow life cycle of a regular JIRA bug ticket can have create road blocks that requires you to restart the life cycle and retread the steps in order to finalize and close out a bug after it has been fixed.
I do not have experience with similar products