Report Library
The built-in reports, and what each one answers.
Every report is grounded in your own connected data — none of them ship with sample or placeholder numbers.
| Report | Answers |
|---|---|
| Code Review Health | Is review happening promptly, or are PRs sitting unreviewed? |
| Cycle Time Composition | Where does a PR's time actually go — coding, waiting for a reviewer, review itself, or deploy — org-wide and by service? |
| Engineer Velocity | Per-person PR throughput, review load and cycle time. |
| Repo Health | Deploy frequency, change failure/revert rate, bus factor, CI reliability, and open security alerts across every repo — filterable by team, with a click-through detail panel per repo. |
| Sprint Velocity | Jira sprint-over-sprint throughput and scope change. |
| Kanban Flow | Where Jira issues get stuck moving through your board. |
| Jira Issues | Issue-level detail — status, assignee, age — filterable like any other report. |
The Jira-backed reports (Sprint Velocity, Kanban Flow, Jira Issues) need a Jira connection — the rest work from GitHub data alone.
Looking for who's on call? That's On-Call, in the main sidebar — see On-Call Registry — not part of the Reports section since it's a live roster, not a comparative/ranked panel.
Cycle Time Composition's deploy stage needs GitHub Deployments or a configured deploy workflow (Settings → Integrations) — a PR without a known subsequent deploy isn't counted in any of the report's stages, not just the deploy one, since every stage's median is computed over the same set of PRs.
Looking for your own PRs, reviews, and cycle time? That's My View, in the main sidebar — see My View — not part of the Reports section since it never compares across people.
Filtering
Every report supports the same filter bar: date range, team, and (where it makes sense) repo or Jira project. Filters persist in the URL, so a filtered report view can be bookmarked or shared as a link.