Bug Age Calculator

[sravani vennapusa]

I want to calculate the Bug age from creation to closed . But I want to exclude the time when the status is kept On hold. Can someone Suggest on this.

[Birkan Yildiz _OBSS_]

Hey @sravani vennapusa 

First, welcome to the Community!

Native Jira calculates the total time from creation to resolution, but it doesn't natively allow you to pause the timer for specific waiting statuses like "On Hold".
To calculate this accurately without complex workarounds, you can use the Duration Between Statuses report in Timepiece - Time in Status for Jira.

Here is exactly how you can set it up:

• Select the Duration Between Statuses report type and click the Metrics button to define a custom metric.
• Set Start At to "Issue Creation" and Stop At to your "Closed" status. 
• Set the Paused On option to your "On Hold" status.

With this setup, Timepiece calculates the exact bug age, but the metric will automatically pause counting whenever the issue enters the "On Hold" status. 

Pro tip: You can also apply Custom Calendars to your report to automatically exclude weekends, nights, and public holidays from the total bug age calculation.

You can find Timepiece - Time in Status for Jira on the Atlassian Marketplace.

Full disclosure, I'm on the team that makes Timepiece. Hope this helps!

[Rahul_RVS]

Hi @sravani vennapusa 

Welcome to the community !!

If you would like to try out a mktplace app for this requirement, pls explore

Time in Status Reports 

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. It works for current issues and closed ones as well.

With Status grouping feature, can help you define your own cycle time / issue age time and view the averages of the same. You can add your specific statuses to the status group to calculate the bug age. Also the app has 20+ reports to meet a variety of use cases.

You can set your own working calendar to exclude weekends and holidays from the time in status calculation.

More details here.

Disclaimer : I am part of the app team for this add-on 

[Anastasiia Maliei SaaSJet]

Hi @sravani vennapusa! You can calculate this with the Time Metrics Tracker app.

To do this, create a custom metric for bug age and exclude the statuses you don’t want to count — in your case, On hold. This will let you calculate the time from creation to closure without including the time the issue spent on hold.

 

With Time Metrics Tracker, you can also configure different metrics, set Warning and Critical time limits, use Work Schedule Support to exclude weekends and holidays for more accurate time tracking, display results in different time formats, view the average time, and sort the data in ascending or descending order.

[Ivan Manolov _Appfire_]

Hi @sravani vennapusa,

Welcome to the community.

Jira doesn't provide a native way to calculate time-in-status with specific statuses excluded from the calculation. The standard "Created" and "Resolved" dates give you the total elapsed time, but there's no built-in field that lets you subtract time spent in particular workflow states.

Atlassian Analytics (available on Premium and Enterprise plans) could potentially help by building a custom query that computes time differences across status transitions, but this requires SQL knowledge and access to the underlying issue history data.

A note on the approach: As @Bill Sheboy mentioned, excluding "On Hold" time from bug age calculations can obscure important process insights. Time spent waiting is still part of the customer's experience and your team's throughput. If bugs are sitting in "On Hold" frequently, that's often a signal worth investigating rather than filtering out. Consider whether your goal is to measure actual cycle time (which should include all states) or active working time (which is a different metric).

That said, if your use case specifically requires excluding certain statuses, you'll likely need to look beyond native Jira features.

Best,

Ivan

[Ivan Manolov _Appfire_]

@sravani vennapusa one more option if you're open to apps from the Atlassian Marketplace: the app my team and I are working on, JXL for Jira, handles this easily.

JXL includes a Time in Status history column that you can configure to show exactly the statuses you want included in the calculation. You'd simply exclude "On Hold" from the column's status list and it gives you the net bug age automatically. It also supports working calendars (so weekends/holidays are excluded), and occurrence modes like Sum, Average, or Median if you want to see aggregated values across multiple issues.

Disclosure: I work for the team that builds JXL.

Cheers,

Ivan

[Bill Sheboy]

Hi @sravani vennapusa -- Welcome to the Atlassian Community!

What problem are you trying to solve with this measurement?  That is, "why do this"?  Knowing that may help the community offer better suggestions.

Until we know that "why"...

The measure of total duration from Created to Closed / Completed is called the "Lead Time", and it helps teams considering process improvement changes / methods.  For example, when the team makes process changes they can compare the before and after time measures to evaluate impacts.

However, removing time for a work item in a "On Hold" status conceals part of the processing where work is waiting (i.e., delays).  That makes evaluating process improvements both more difficult and not representative of the actual impacts.  This could mislead the team and stakeholders.  For a step where work is waiting, it may be better to evaluate why waiting occurs (e.g., with root cause analysis), and consider how to reduce / eliminate that step.

As noted earlier, knowing why you want to do this will improve community suggestions.  In the meantime, please consider discussing your scenario with your team's agile / process coaches to learn their thoughts.  Thanks!

Kind regards,
Bill

[Danut M _StonikByte_]

Hi @sravani vennapusa,

Welcome to the Atlassian Community. 

Jira does not provide an out-of-the-box report specifically designed to calculate “time in status” while excluding selected statuses.

With Atlassian Analytics (an enterprise/premium feature), you may be able to build a custom chart that excludes specific statuses, but this usually requires custom queries/SQL.

Alternatively, apps from Atlassian Marketplace often support this directly out of the box.

If you want to use an app, this can be easily achieved by using the Time in Status gadget offered by our Great Gadgets app. Here is an example, with the average bug age split by priority:

On its Data tab, this chart will display a table with the bugs, their age and time in every workflow status.  

In its configuration settings, the gadget allows you to exclude certain statuses such as "On hold":

Hope this helps.

Danut.

[Enric Font]

Dear @sravani vennapusa 

I you can get the time each work item remains in each status you can use the SLA report of the Gadget Utilities for Jira Cloud

You can select the filter of work items to display and add the statuses you can track