Resolution time report
A resolution time report measures the elapsed time between when a Jira issue is created and when it is resolved. It tells you how long stories, bugs, support tickets, or any other issue type sit in your workflow before they close.
The headline metric is usually an average or median, but the real value lives in the breakdown — by status, issue type, priority, assignee, project, sprint, or label. That is where the patterns hide.
A good report is less about declaring "we are fast" or "we are slow" and more about answering the next question: Where is time being lost, and what kind of work is losing it?
What does a resolution time report measure?
It measures the gap between issue creation and issue closure in Jira, then breaks that gap down by whatever dimensions you care about. The core inputs are a start event (typically issue creation), a stop event (a specific closing status transition), and the cohort of issues in scope.
Benefits of a resolution time report
Shared definition of speed. Arguments about velocity collapse into a concrete number anchored in actual closing times.
Early warning on workflow problems. Aging tickets and rising medians surface in the report before they surface as escalations.
Better SLA management. Support and operations teams can spot trends against committed response and resolution windows.
Honest retrospectives. Sprints are easier to debrief when "we were slow" turns into "P2 bugs took 40 percent longer than P3 bugs."
How to use a resolution time report
Work through the analysis in this order:
1. Define what "resolved" means in your workflow — the specific status transition that stops the clock. 2. Choose the cohort of issues to study, usually a project, a sprint range, or an issue type. 3. Run the report and look at the distribution, not just the average. A handful of stale tickets can drag the mean badly. 4. Slice by priority, assignee, status, or label to find the segments driving the long tail. 5. Pair findings with workflow analysis — which status is holding the work? Where is it going stale?
The report is the diagnosis. The fix usually lives in queue management, triage practices, or scope.
Running the resolution time report with Timesheet Reports & Gadgets
Timesheet Reports & Gadgets (also referred to as Prime) is a separate Jira app from Timesheets. It is a lightweight reporting layer that extends native Jira time tracking with prebuilt, configurable reports — and the resolution time report is one of them.
Inside Reports & Gadgets, the report breaks elapsed time down by status, so you see how long issues sit in each step of your workflow rather than only the create-to-close number. That status-level view is what turns the report from a vanity metric into a workflow diagnostic.
Because the data comes straight from Jira issues, the numbers reconcile with the work leadership is already tracking. There is no separate analytics stack to maintain, and reports can be surfaced as Jira dashboard gadgets or subscribed to by email so the right stakeholders stay current.
This is distinct from Timesheets, which is the enterprise-class time tracking, billing, and CapEx or OpEx product. Reports & Gadgets is the right fit for teams who want simple, Jira-native reporting on the time and status data they already have.
