Time Since Metric/ Age of …

Performance Objectives: Charts for Jira offers extensive support for dynamic fields and metrics, facilitating comprehensive time-tracking Jira reporting. Among the powerful metrics available is ‘Time since,’ which enables you to track the time elapsed since a specific date field, such as ‘Created,’ ‘Updated,’ ‘Resolved,’ in Jira, and more. For a comprehensive list of date fields compatible with the ‘Time since’ metric, please scroll down to the bottom of the page.

Now, let’s delve into some sample chart configurations utilizing the ‘Time since’ time field.

Create Average Age Report with ‘Time Since’ Metric

Analyzing and tracking issues’ age with the ’Time Since’ metric not only ensures better issue management but also leads to more efficient workflows, improved team accountability, and data-driven decision-making. Here’s a sample “Average Issue Age” report, detailing the average number of days that Bug and Story issues remained open after being created, grouped by priority.

In our example chart, we’ve selected the Average calculation for the ‘Time Since’ metric. The ‘Issue Type’ field is selected for Display by, and we have further grouped by ‘Priority’.

In this report, we utilize the ‘Time since’ metric to calculate the average age of all issues filtered within the data source, irrespective of their resolution status. When setting up the metric, you’ll notice that the “Measure until Resolved” button is selected by default, which calculates time in the following way:

• for resolved issues, it measures the time elapsed from creation to resolution
• for open issues, it calculates the time from creation until the present moment

Should you wish to assess the age of the issues exclusively for closed or open issues, you can customize this within your data source settings. Additionally, in certain contexts, you may find it beneficial to utilize the “until now” selection.  

Combining ‘Time Since’ Metric with Target Feature for ‘Max Issue Age’ KPI Report

The Performance Objectives app goes beyond tracking elapsed time by offering the option to define a ‘max issue age’ target. Slot splitters and target feature, along with various customization options, are what sets our app capabilities apart the native Jira Time Since Issues chart, where those options are missing.

Targets feature allows teams to establish performance objectives related to issue age and ensures that timely resolutions are achieved. By combining the ‘Time since’ metric and a target for max issue age, businesses can optimize their performance, proactively identify and address bottlenecks, and significantly improve workflow efficiency. 

In our sample KPI report, we’ve specified the open issues from the data source. We’ve employed the ‘Time Since’ – Created metric, measured in days, for detailed analysis. The ‘Display By’ parameter is configured to ‘Issue Summary’ to provide further insight into the characteristics of the issues. Additionally, we’ve enabled the ‘Target’ feature, set it to ‘Fixed,’ and established a fixed threshold of 3 days. Exceeding this target is considered undesirable.

Date Fields Supported by ‘Time Since’ Metric for Enhanced Time-Tracking in Jira