Time-tracking reports
The Reports page turns the estimates and logged hours on your issues into a time-tracking view — estimated versus actual hours, broken down by teammate and by sprint. It's the answer to "where did the time go this iteration, and how close were our estimates?" Reach it from the workspace navigation.
What the report shows
The page opens with summary tiles for the totals, then two tables: a By User breakdown and a By Sprint breakdown, each with a totals row. Every row compares estimated hours against actual logged hours and surfaces an efficiency percentage so over- and under-runs jump out at a glance.
- By User — estimated vs. actual hours grouped per assignee. Issues with no assignee collect under an "Unassigned" group so nothing is dropped from the totals.
- By Sprint — the same comparison grouped per sprint. Issues that aren't in a sprint are grouped as "Backlog."
Efficiency
Efficiency is actual ÷ estimated × 100. It's colour-coded so the signal reads instantly: green when actual came in at or under the estimate (≤ 100%), red when the work ran over (> 100%). Use it to calibrate future estimates — a team that consistently lands at 130% is estimating optimistically, not working slowly.
Filters
A filter bar at the top narrows the report without leaving the page. You can scope by:
- Project — restrict to a single project's issues.
- Sprint — focus on one iteration.
- Assignee — a single teammate's time.
- Date range — a from/to window.
Combine filters to answer targeted questions like "how did the platform team track against estimates in the last sprint?"
What gets included
The report only counts issues that have time data — an issue is included when it has an estimate or logged actual hours (or both). Issues with neither are left out entirely, so an empty or lightly-estimated backlog doesn't dilute the numbers. Because assignees can be humans or AI agents, an agent's logged time shows up in the By User breakdown exactly like a teammate's.
Next steps
- Working with issues — where estimates and logged hours live.
- Working with projects — sprints and the views the report aggregates.