Measure how long Jira issues take to close, broken down by status. The resolution time report turns workflow drift into a number you can act on.
Time spent report
Where did the quarter actually go? A time spent report shows where hours and effort actually landed inside Jira – the only honest way to know whether priorities and work are pointed at the same things.
A time spent report aggregates Jira time-tracking data and shows how hours were distributed across whatever dimension matters most: Status, issue type, project, label, assignee, or epic. It is a backward-looking view of where the work went.
The dimensions are the point. The same underlying data answers very different questions depending on how you slice it. By status, it tells a workflow story. By issue type, it tells a delivery-mix story. By project or label, it tells a focus story.
A useful report is not a single chart. It is a flexible cut of the same data, shaped to the question at hand.
Benefits of tracking time spent in Jira
Reality check on priorities. Strategy decks rarely match where hours go; this view makes the gap visible.
Workflow diagnostics. Time in each status surfaces queues, blockers, and stages that quietly absorb effort.
Sharper estimates over time. Comparing logged hours on completed work against original estimates feeds better forecasting.
Clearer sense of overhead. Hours on bugs, support, and unplanned work show up against time on planned delivery.
How to use it
A practical workflow:
1. Pick the question first. "How much time did Project Atlas consume?" is a different report from "Where in the workflow are issues spending the most time?" 2. Set the time window: A sprint, a quarter, or a release cycle. 3. Choose the primary dimension, usually status, project, or issue type. 4. Layer in a secondary dimension to find the patterns. Time per project is interesting; time per project per status is actionable. 5. Compare against estimates where you have them, and use the gaps as the start of the conversation rather than the end.
These reports pay off when they feed a decision — a process change, a capacity reallocation, an estimation reset — rather than living as a passive dashboard.
Running the 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 time spent view (sometimes labeled Timespent) is one of them.
Inside Reports & Gadgets, the report shows how logged hours on Jira issues break down across statuses, issue types, and labels. The status view is the differentiated cut: It surfaces how long work sits in each step of the workflow, not just the total on the issue.
Because the data is anchored to Jira issues, the numbers stay consistent with the work leadership is already tracking. Reports can be saved, surfaced as Jira dashboard gadgets, or subscribed to by email, so the right stakeholders see the numbers without anyone exporting spreadsheets.
This is distinct from Timesheets, which is the enterprise-class time tracking and billing product with accounts, CapEx or OpEx classification, and full invoicing. Reports & Gadgets is the right fit for teams who want straightforward, Jira-native time and status reporting without the wider compliance and finance footprint.
Timesheets
Optimize your projects, teams, and resources
The #1 time-tracking app for Jira. Timesheets seamlessly integrates with Jira and your existing workflows to help you track time for accounting, CapEx tracking, client billing, compliance, and more.
Start a Free TrialFrequently Asked Questions
Couldn't find what you need?Go to our documentation
Timesheet Reports & Gadgets and Timesheets are two different Jira apps. The time spent report lives inside Reports & Gadgets and gives you a lightweight cut of Jira time-tracking data – usually broken down by status, issue type, or label. Timesheets is a separate, enterprise-class product with accounts, billable status, CapEx or OpEx classification, full invoicing, and approvals. If you want a quick read on where logged time is going across statuses or issue types, you want this report. If you need billing accuracy, capitalization schedules, or compliance-grade approvals, you want Timesheets.
Granular enough to answer the question, no more. A status-level breakdown for a single project is useful for workflow review but overwhelming for executive reporting. A roll-up by issue type across a quarter is useful for portfolio decisions but useless for spotting the bottleneck in this sprint. Match resolution to the audience.
Then the report tells the story of what was logged, not what happened. The fix is upstream – better tracking habits, lighter-weight logging, and manager review that catches gaps. No reporting layer can rescue bad input data.
It is a useful input, not a complete answer. Historical time spent shows where a team's effort actually landed, which is more reliable than estimates for predicting the next period. But capacity planning also needs forward-looking inputs – upcoming PTO, role changes, project starts and stops – that a backward-looking report does not capture on its own. For deeper capacity work, Tempo offers a dedicated Capacity Planner product.
Related articles
See where shared capacity actually went. Team timesheets roll up Jira worklogs by person, project, and account so managers spot overload fast.
Time tracking gives PMO directors the portfolio evidence to defend spend and catch drift early. See why it's important and how to track it in Jira
Tempo makes it possible to conveniently customize your time tracking experience with Timesheets or time tracking. So which should you choose?
Knowing the status of work is just as important as knowing when it will finish. See an aggregate of how long work takes for future estimation.
Did you know you can use Timesheets data to track project progress by billable hours and more – all within the Structure interface?
Did you know that in Tempo Timesheets for JIRA there’s an easy way to see how much the time spent on issues within an epic?
Learn to identify bottlenecks, reduce workflow inefficiencies, and boost team productivity with Jira’s time-in-status function and Tempo’s Charts.
Everybody gets the same 24 hours per day to achieve whatever they put their mind to. Once it’s lost, time can no longer be used.
