Flow Guide All guides ↗
Every section

Reports

How the work is going: each sprint, delivery over time, how smoothly work flows and how it's spread across the team. Each section says what it's for, who sees and changes it, and how to do the main jobs there.

📉

Sprint

How the current or a past sprint is going against its plan.

Product Owner · Scrum Master · Developers · Stakeholders · Admin
Project › Reports › Sprint

Reports are for every role on the project — the Product Owner, Scrum Masters, Developers and Stakeholders — and for organisation Owners/Admins. Nothing here changes your work; it only shows how it's going. The Sprint tab, its burndown and its sprint report are on every plan.

See how a sprint is going

  1. Pick the sprint from the list at the top (running and completed sprints), or step through them with the arrows.
  2. Four tiles sum it up: Time (days left, or "day 3 of 14"), Done (points or items finished), Scope change (what was added or removed after the start) and, while it runs, Against the ideal line (points behind or ahead).
  3. The Burndown shows story points left each day against the ideal line, with a Today line on a running sprint. It fills in once a day while the sprint runs.

See how each item ended

  1. The Sprint report groups the sprint's work items as Done, Still open (or Not finished once the sprint is completed) and Removed during the sprint, with points per group.
  2. Unfinished items in a completed sprint say where they went — "Moved to backlog" or "Moved to Sprint 5".
  3. Any notes written when the sprint was completed show as Notes from completing the sprint.
🔢Exact numbers — click Show as table on a chart to see the same numbers as rows — handy for copying, and for screen readers.
🚚

Delivery

How much your team finishes over time.

Product Owner · Scrum Master · Developers · Stakeholders · Admin
Project › Reports › Delivery

Delivery shows how much your team finishes over time, and how long work takes. Every chart on this tab is part of the Starter plan and up; on Free, each shows an upgrade note instead.

ChartWhat it showsPlan
VelocityStory points finished in each completed sprint, with the averageStarter & up
Sprint completionWork items in each sprint when it ended (added ones included, removed ones not), and how many were finishedStarter & up (comes with Velocity)
Cycle timeFrom the first move into In progress until DoneStarter & up
Lead timeFrom the day a work item was created until DoneStarter & up

Use it for planning

  1. Look at Velocity before sprint planning: the average is a realistic guide to how much to commit to (the same average appears on the sprint's planning line).
  2. Check Sprint completion for a pattern — if sprints often end with lots unfinished, plan less or split work smaller.
  3. For Cycle time and Lead time, choose Finished in the last 30, 90 or 180 days (90 to start with). The chart shows how many items took how long, and Took longest lists the slowest ones to talk about.
🌊

Flow

How smoothly work moves from start to done.

Product Owner · Scrum Master · Developers · Stakeholders · Admin
Project › Reports › Flow

Flow shows where work piles up and how smoothly it moves. It has three parts: flow metrics and cumulative flow (Starter plan and up), and the Where the open work is breakdown, which is on every plan.

Flow metrics

  1. Four tiles: Work in progress (against your WIP limits), Throughput (items finished per week), Cycle time (how long half of the items take, and 85% of them) and Ageing (items in progress longer than usual).
  2. Throughput charts items finished per week over the last 8 weeks.
  3. Work item age lists open work in progress, oldest first, coloured against your project's own cycle times.

Cumulative flow

  1. The chart stacks how many items were in To do, In progress and Done each day.
  2. A band that keeps widening means work is piling up there. A flat Done band means nothing is finishing.

Where the open work is

  1. Open work is counted by Status, Type and Priority. Tick Include done to count finished work too.
  2. Click any row to open the backlog filtered to exactly those items.
♾️Kanban projects — the Reports page opens on this tab (tabs Flow · Delivery · Team) and the line at the top sums up the flow — work in progress, what finished recently and how long items usually take.
💳On Free — the flow metrics and cumulative flow show an upgrade note; the breakdown still works.
👥

Team

How the work is spread across the people on the project.

Product Owner · Scrum Master · Developers · Stakeholders · Admin
Project › Reports › Team

The Team tab, Who holds the open work, shows how the work is spread across the people on the project. It's on every plan.

Check the balance

  1. Each person has a row with a bar of their to-do and in-progress work, their Open count, and Done, last 30 days.
  2. An Unassigned row counts open work nobody has picked up yet.
  3. Click a name (or Unassigned) to open the backlog filtered to that person's items.
🤝Use it kindly — it's a quick way to spot someone overloaded, or work waiting for an owner — a prompt for a conversation in stand-up, not a scoreboard.