Average time to resolution
Navigation |
|---|
Report Usage
It shows the total time it took each user to change the status of an issue from one to another. The Y-axis displays hours, and the X-axis lists users who made transitions within the selected period.
Specific functionality:
At the top of the report card is a date bar swap for quickly changing the time frame.
The report can display an average trend line if enabled, showing the average time spent on resolution tasks among selected users.
Hovering over a user bar reveals a tooltip with the number of issues, average resolution time, and hours above average.
Color highlights indicate values above or below the average.
Next to the date bar swap is a dropdown for temporarily changing the period without affecting the saved configuration.
Clicking a Jira user bar opens a subtable listing the user’s assigned issues and the total number within the selected settings. For full guidance on how to work with subtables, see the Working with Subtables .
Formula
Σ Time spent in each status from the selected start status / Amount of issues.
Setting up a report
The report has 5 tabs of configurations: Data source, Parameters, Display, Subtable, Description.
Data source & Description
This report supports filtering issues by Basic Source, Saved Filter, or JQL query. For full guidance on how to configure your data source and , see the Data Source & Report Description
Specific Report Parameters
Countdown statuses selects the starting status for count. The options are all available statuses in current Jira site.
Period lets user select the time unit to customize the displayed data.
Display
Manage the visual appearance and presentation of the report, including the visibility of specific elements and the formatting of data.
Show average toggle lets the user show the average line or not.
The average value counts as the sum of average time to resolution of all Jira users divided by a number of Jira users. It allows comparing the average time indicators within selected Jira users.
Report Use Cases
✅ Analyze how quickly individual developers are progressing issues from “In Progress” to “Done.”
✅ Monitor whether support agents are resolving requests within expected timeframes.
✅ Measure how long it takes for issues to move from “Ready for QA” to “Done”.