v0.15.0

Reports

Five reports and an insights panel. The whole set is built on one idea: a report that cannot be
trusted at a glance is worse than no report, so each of these says what it is measuring and
refuses to imply more.

Flow — created against resolved over a window, so you can see whether the queue is growing.

Cycle and lead time, with aging work in progress. Not just what finished, but what is still
open and how long it has been open, which is the half that usually goes unlooked-at.

Sprint burn-up with a real scope line. Scope changes are drawn, not hidden: issues added to
and removed from a sprint are recorded as events, so a sprint that grew looks like a sprint that
grew. The sprint review record keeps that history after the sprint closes.

Velocity as a forecast band, never a scoreboard. It is drawn as a range, and it is deliberately
not presentable as a per-person number.

An insights panel on search results. Any search you can express becomes a small set of
aggregates over exactly the issues it matched. This is the dashboard replacement.

Export. CSV of the plotted series, PNG with fixed axes so two exports are comparable, and
shareable URLs — a report you can hand to somebody is a report they can check.

What was deliberately refused

Burndown, the cumulative flow diagram and a configurable gadget dashboard are not here, and
that is a decision rather than a backlog item. The reasoning is written down in
docs/design/reports-proposal.md §3.

---

Full Changelog: v0.14.0...v0.15.0