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

[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

[Venkata Sagar Ganesh Rao Mahendrakar]

 Hi @Bill Sheboy 

Thanks for the Reply

We don't have automation plugin in Jira.

Thanks for the reply!!

Regards
Sagar

[RVS_Support]

Hi @Venkata Sagar Ganesh Rao Mahendrakar 

If you are open for a mktplace add-on, you can try our addon:

Agile Tools : Epic Tree, Links Tree, Time in Status & Worklogs

The add-on provides the time in status for the complete lifecycle of the issues plus a variety of other use cases.

Do try it out.

Disclaimer : I work for RVS, the vendor for this app

[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.

We offer a free trial - let me know if you want to check it out!

Dan

[Venkata Sagar Ganesh Rao Mahendrakar]

Hi @Dan -minware- 

Thanks for the Reply!!

We will get back to you

Regards

Sagar

[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

[Venkata Sagar Ganesh Rao Mahendrakar]

Hi @Mark Segall 

Thanks for the Reply!!