nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to calculate time for a bug

Venkata Sagar Ganesh Rao Mahendrakar

Hi,

How can we calculate time for a bug
Use case:
ticket is created -> label added - > investigation is done -> label removed = time between creation and removing label is required

Jira has plugin for tracking time for bug?

Please Help

Thanks in Advance

Sagar

Accepted answers

All comments

Bill Sheboy

Hi @Venkata Sagar Ganesh Rao Mahendrakar

Jira does not have built-in time tracking for your specific scenario.

Instead you could investigate marketplace addons and/or write and automation rule to detect this condition and save the time in a custom field. Please contact your Jira site admin to learn if you have automation rules (or other addons available) which could help with this.

Kind regards,
Bill

Mark Segall

Hi @Venkata Sagar Ganesh Rao Mahendrakar - It seems like you're trying to use a label as a status. Is there a reason you can't add a new status in your workflow called "Investigation" or "Triage" that you transition the bug into/out of and use that as your point of reference for time? From there, you could do a couple things:

Aggregate Reporting: You could use the native "Time In Status" dashboard gadget to track the average time in your new status for a given set of bugs
Visibility on a given issue: You could combine with a couple custom fields (e.g. Triage Start/Triage End) and automation to populate the start/End times as issues enter/exist the new status

Dan -minware-

Hey @Venkata Sagar Ganesh Rao Mahendrakar -

As others mentioned this isn't available natively. If you are open to working with a 3rd party we can help at minware.

Below you can see the expanded Bug grouping from our Ticket Flow report. The blue chips are showing how long each took and this metric is automatically captured in minware no time tracking required.