Reports
Reports turn the work you already track — cycles, work items, states, assignees — into charts and numbers you can act on. Nine report types, one page, no set-up.
Plan: Pro and above
What you can do
- Track a cycle's progress against an ideal line with a Burndown chart.
- See what a cycle actually delivered — and what crept in — with the Sprint Report.
- Get a single 0–100 Sprint Health score with a grade.
- Compare delivery across cycles with Velocity.
- See who is carrying what with Workload.
- Spot whether you are keeping up with intake using Created vs Resolved.
- Watch work accumulate or drain with Cumulative Flow.
- Break the backlog down by state and priority with Status Breakdown.
- Ask AI to write the sprint story for you with AI Summary.
- Export any data report as CSV, and the AI Summary as a formatted PDF.
Getting started
Open Reports
- In the workspace sidebar, click Reports.
- Pick a project from the selector at the top right. Only projects you are a member of appear.
- For cycle-based reports (Burndown, Sprint Report, Sprint Health, AI Summary), pick a cycle from the second selector.
- Click a tab to switch report type. Data loads immediately.
📷 Screenshot: The Reports page with the project and cycle selectors at top right and the row of report tabs beneath.
The reports
Burndown
Plots remaining work day by day across the cycle, against a straight "ideal" line running from the total down to zero. The actual line stops at today — future days are left blank rather than drawn flat.
How to read it: actual above ideal means you are behind pace; below means ahead. A flat actual line under a falling ideal line is the classic warning sign.
The cycle needs both a start and an end date, otherwise the chart cannot be drawn.
Sprint Report
Sorts every work item in the cycle into three buckets:
- Completed — finished on or before the cycle end date.
- Incomplete — not finished, and it existed when the cycle started.
- Scope creep — not finished, and it was created after the cycle started.
You get counts and points for completed and incomplete, plus the item list behind each bucket.
Sprint Health
A single score out of 100 with a grade: Healthy (80+), At Risk (60–79) or Critical (below 60). The score is a weighted blend of four things:
| Factor | Weight | What it measures |
|---|---|---|
| Completion rate | 40% | Items done ÷ items in the cycle |
| On-time rate | 25% | Of items with a target date, how many were finished by it |
| Scope stability | 20% | How little work was added after the cycle started |
| Pace | 15% | Whether completion is keeping up with elapsed time |
A cycle with no work items scores 0 and is graded N/A.
Velocity
One row per cycle that has both dates, oldest first: completed items, total items, completed points, total points. Use it to set a realistic commitment for the next cycle — average the last three or four, not the best one.
Workload
Every active project member with their open (not yet completed) items, open points, and a breakdown by priority. Sorted heaviest first. Members with nothing open still appear, at zero.
Created vs Resolved
Weekly counts of items created against items resolved, for the last 12 weeks. If created consistently outruns resolved, the backlog is growing no matter how busy the team feels.
Cumulative Flow
Daily running totals over the last 30 days: total created, total completed, and the gap between them (work in progress). A widening gap means work is going in faster than it comes out.
Status Breakdown
The current shape of the project: total items, a count per state group (backlog, unstarted, started, completed, cancelled), a count per individual state, and a count per priority.
AI Summary
Pulls the whole report set for the selected cycle — sprint report, health, burndown, velocity, workload, created-vs-resolved and status breakdown — and asks the AI to write a narrative report from that data. You get metric cards above a written analysis.
Because it is grounded in exactly the same numbers as the other tabs, it can only tell you what the data supports.
📷 Screenshot: The AI Summary tab showing metric cards above a written sprint analysis.
Exporting and sharing
- Export CSV — on every data tab. The file is named after the project identifier, the report and (for cycle reports) the cycle. The button is disabled when the current report has no rows.
- Download PDF — on the AI Summary tab, once the summary has been generated. It is a real vector PDF, not a screenshot of the page.
- Share to Slack / Share to Teams — on the AI Summary tab, and only if your workspace has Slack or Microsoft Teams connected. They post the written report into the connected channel.
Tips
- Point-based numbers (completed points, open points) only mean something if your team actually sets estimates. Otherwise read the item counts and ignore the points.
- Scope creep is derived from an item's creation date, not from when it was added to the cycle. Something created before the cycle and pulled in mid-cycle counts as incomplete, not scope creep.
- If a report looks stale straight after a change, wait a moment and hit Refresh — report payloads are cached briefly on the server.
Limits & good to know
- Reports cover one project at a time. There is no workspace-wide roll-up.
- Draft and archived work items are excluded from every report, with one exception: Created vs Resolved and Cumulative Flow include archived items, so historic trend lines do not rewrite themselves when you archive.
- "Completed" always means the item carries a completion timestamp — i.e. it reached a state in the completed group. Cancelled items are not completed.
- The report list is fixed. You cannot build a custom report, change the chart type, or change the 12-week / 30-day windows from the UI.
- Slack and Teams sharing depends on the Integrations feature (Business and above).