When the product launch is full of bugs.

[Leslie C]

50+ developers.  Many scrum teams.  Company launches new features, enhancements every quarter.  

Bugs are sliced & diced a myriad of ways for reports, dashboards, decks.  Nonetheless, the teams continue to deliver bug-ridden code.  The devs blame QA, QA blames the delivery managers for too little time, Product blames the project managers for features that do not answer the requirements, and so on.  

Do I need to reinvent the wheel here?  Or, is there a plan, checklist, plug-in, etc. available so that I can gather the correct data to expose the issues that need attention.  

[Iryna Komarnitska_SaaSJet_ · Accepted solution]

Hi @Leslie C 

If you decide to switch to Jira Cloud, here are some recommendations.

To quickly create bug reports, I can advise the Issue Creator app.

It will help speed up the testing process and create high-quality visual feedback.

[Bloompeak Support · Accepted solution]

Hi @Leslie C

You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app. For further details, you can have a look at Status Time Reports How to Videos.

• This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Free.

Hope it helps.

[Valeriia_Havrylenko_SaaSJet]

Hi @Leslie C  👋

While there may not be a one-size-fits-all solution, there are some add-ons you can try to improve your bottlenecks.

As an alternative , I guess you can try Time in Status for Jira Cloud if you are switching to cloud version. The primary purpose is to help teams gather valuable data about the lifecycle of your issues in Jira. Add-on allows you to measure and visualize the time spent in each status, such as "Open," "In Progress," "In Review," and "Closed," and provide 7 types of reports to help you identify areas for improvement.



Also Time Between Statuses will be an option for you too. This add-on, which measures connections in the workflow, through a transition time in specific issues. You can count Cycle and Lead Time by setting start/stop and pause statuses in the configuration manager. To detail the calculation conditions you should select the first/last transition to/from status.

Add-ons have a 30-day free trial version and free up to 10 users. 
Please, let me know if you have any questions

Hope it helps 😌
Valeriia

[Leslie C]

Thanks!