Reports
What each chart measures, what it does not, and the two most common ways to misread one.
Reports live under Reports, and each can be scoped to a project, a sprint or the whole workspace.
The metrics
| Report | Measures | Read it when |
|---|---|---|
| Throughput | Tasks completed per period | You want to know if output is steady |
| Cycle time | Start → done | Work sits in progress too long |
| Lead time | Created → done | People say "I asked for this weeks ago" |
| Velocity | Completed work per sprint | Planning the next sprint |
| Burndown | Remaining work over a sprint | Mid-sprint, to see if it will land |
| Aging | How long open work has been open | Finding the things everyone forgot |
| Distribution | Breakdown by status, assignee, type, priority | Checking for pile-ups |
| Time logged | Recorded time, aggregated | Billing, or capacity planning |
Cycle time and lead time are different
This is the distinction people most often collapse, and it matters:
- Lead time starts when the task was created. It includes the six weeks it sat in the backlog.
- Cycle time starts when someone began work. It measures your process, not your queue.
A team with a good cycle time and a terrible lead time does not have a delivery problem — it has a backlog problem, and speeding up the team will not fix it.
Two ways to misread a chart
Throughput is not velocity. Throughput counts tasks; velocity counts estimated effort. A week of six trivial tasks and a week of one large one can show identical throughput and very different velocity. Neither is wrong; they answer different questions.
Averages hide the tail. A cycle time averaging four days can still contain a task that took eleven weeks, and that task is the one your stakeholders remember. Read the distribution, not just the mean.
What reports do not include
- Archived projects, unless you ask for them.
- Tasks you cannot see. A report scoped to the workspace covers the projects you are a member of, so two people can legitimately see different numbers.
- Deleted tasks. They are gone, including from history.
Exporting
Every report exports to CSV. If you want the numbers on a schedule instead of on demand, the reports API returns the same aggregates — worth using rather than re-deriving the metrics yourself, or your dashboard and Krrim will eventually disagree about what cycle time means.