Average Time in Status: Jira Native Gadget vs. Performance Trend Gadget
The Jira native Average Time in Status gadget, by default, filters resolved issues. We’ll later explain what this means and why it may not always be the most suitable method for tracking time in status across all scenarios.
In the meantime, here’s how to set up our gadgets, in this example, the Performance Trend gadget, so it aligns with the Jira native one, ensuring the results are the same in both gadgets.
Jira Average Time in Status gadget settings:
Select project or Filter
Select status/es, e.g., “In Progress”
Period: Monthly
Average duration in status: Hourly
Days previously: in our example - 180
Matching settings in the Performance Trend gadget:
In the Data Source, filter resolved issues from the matching time period (180 days) and select the the same project or filter as in the native gadget.
Select the Time in Status metric and pick the status “In Progress”. Display the values in hours.
Switch to Average calculation.
Display the data by the Resolved field and specify by Month.
As we have already mentioned, the native gadget calculates average time in status only for issues resolved during the selected period. It does not consider issues that were in the particular status during the selected period but are still unresolved (“In Progress” in our example).
If you want to calculate the average time spent in the relevant status within that timeframe - regardless of whether the issues were closed at the end of the period or still open, we recommend using the Performance Objectives Data Source filter - Status Was - when reporting on the Time in Status metric, and selecting matching statuses in both places.
Here’s are a couple of sample Time in Status reports configured with our gadgets:
Average Time in Status by Priority