User guide

Reports

Four questions a delivery team asks of its iterations: are we on track, do we finish what we commit, do we ship when points are not the unit, and how long does a piece of work actually take. Reports answers all four from history the application already wrote - no separate tracking, nothing to keep in sync.

per iteration derived from the audit trail same semantics as the progress bar

Where

The Reports tab of a project, with an Iteration selector at the top. Reports need time-boxes, so an organization that has never planned one sees No iterations yet and a link to create the first one.

One rule under all four charts

Every report counts statuses by their semantic category, under the same rule the progress bar on the project page uses: Done delivers, Cancelled leaves scope entirely. A status in the Done bucket counts as delivered no matter who moved it there - the sidebar, the board, an agent through the API, a child-completion rollup or a GitHub webhook all write the same audit trail the reports read. And a day row means the state at the end of that day, so the lines on the chart and the numbers in the tables cannot tell different stories.

Burndown

The on-track question, in points: the Ideal line runs straight from what was committed to zero, Scope in iteration steps as work joins or leaves, and Remaining points is today's truth. Scope changes are drawn in - Added and Removed - because an item pulled out mid-iteration is removed scope, and a chart that quietly redrew around it would hide the very thing a burndown exists to show: that the plan changed.

Velocity

The commitment question, in points per iteration: Committed scope beside Delivered, over the last six iterations - deliberately few, because velocity that needs scrolling has stopped being a decision aid. A team whose bars sit consistently under their commitment plans smaller; a team that over-delivers every sprint is under-estimating, not superhuman.

Throughput

The same question without points: items finished per day, counted rather than estimated. A team that ships nothing measurable in points still ships work, and a burndown cannot say so - throughput is the report that survives an unestimated backlog. The Items / Days switch reads it per day finished or per day elapsed.

Cycle time

The patience question: for each delivered item, how long from first entering an In progress status to delivery, with the distribution summarized. The report warns when the data cannot answer honestly - "Nothing has been delivered in this iteration yet, so there is no cycle to measure." and, for items that jumped straight to done, "…never passed through an In Progress status, so no cycle could be measured for them." A team with many of the second warning has a workflow people are bypassing, which is a conversation about the workflow, not about the chart.

Who sees what

Reports are computed from the work you can see, and the Reports tab appears where you have access to the project - the same visibility boundary as everywhere else in the product, so two teammates' charts can legitimately differ when their access does.

Keep going