Compare target, actual, and capacity
Open the sprint and read the metrics, or the totals row on the board.
Actual time currently isn't limited to the sprint's start and end date. A task can bring in entries from before the sprint or after it closed. So the same task in several sprints can contribute the same entries to several reports.
- Target hours
- Sum of the current hour estimates across every linked task. Missing estimates count as 0.
- Actual hours
- Sum of saved durations from completed time entries on those tasks. Running timers and pure project entries with no task link don't count.
- Capacity utilization
- Target hours divided by the manually stored sprint capacity. The bar can max out at 100 percent even though the number is higher.
- Task progress
- Completed tasks against every sprint task. Each task counts equally, regardless of its estimated hours.
Read the status chart
Switch to the Dashboard tab. The chart rolls tasks up into Open, In progress, and Done. Backlog and other statuses that are neither done nor in progress land in Open. The values show the current state of the linked tasks.
Place the burndown
Set a valid period, with a start date on or before the end date, so the burndown can be shown. The ideal line reduces the task count evenly down to the sprint's end. The actual line uses tasks completed as of today and their last-changed date as an approximation of when they were finished. It measures task counts, not remaining hours.
If a completed task is edited later, its computed completion point on the chart can shift. Newly added or removed tasks also change the curve retroactively. So use it for orientation rather than as an exact historical performance record.
View tasks per week and priorities
The weekly bars assign tasks to the sprint period's weeks based on their due date. Tasks with no due date, or with a date outside that period, appear in the group with no week assignment. The additional priority list shows open tasks with high or critical priority that are due in the current calendar week.
Use the retro after closing
Once a sprint is completed or canceled, the board shows two groups: Done and Not done. Compare the tasks and their target/actual values, and decide which open items get planned further. The retro uses current task statuses. It doesn't automatically record which tasks were exactly done at the moment of closing.
Attribute a shown budget correctly
If the sprint is already linked to a project and a matching budget can be loaded, a budget card appears. This queries the project's budget; it isn't a standalone sprint budget. The separate sprint capacity remains an hour plan. See the Budgeting module for details on maintaining a budget.
Common pitfalls
Closing a sprint doesn't freeze the numbers
Later task and time changes can make even closed sprints look different. Document important closing decisions separately, in a note or a meeting.
A missing period hides the charts
Without both dates set, or with them in reverse order, the burndown and weekly report are missing. The task list works independently of that.
Frequently asked questions
Why are actual hours higher than the entries logged within the sprint period?
The report sums up every completed entry on the linked tasks, and currently doesn't apply a sprint time filter.
Why does an old burndown change?
It's recalculated from the current data and the last-changed date of completed tasks. A daily status history isn't used for this.
Does a large task count more toward progress?
For task progress and burndown, each task counts once. Hours are reported separately, via target, actual, and capacity.