Jira sprint burndown not working? Six checks, and how to read scope change
The sprint is half done, the team is busy, and the burndown chart is still flat. Or it jumps up for no clear reason. Nine times out of ten, Jira is doing exactly what it was told to do. Here are the six checks that fix most burndown charts, in the order we would try them. They apply to company-managed boards; team-managed projects are covered at the end.
1. Done means the right-most column
A work item counts as done when its status is mapped to the right-most column of the board, whatever that status is called. If your “Done” status sits in a middle column, for example before “Ready for release”, the line won’t drop until the item reaches that last column. Check Board settings › Columns.
2. What the chart counts
The burndown counts with the board’s estimation statistic: story points, work item count, time or another number field. Admins set it in Board settings › Estimation, and the Sprint Burndown dashboard gadget follows it. On the report itself, the drop-down only changes your own view. To count work items on the gadget, set the board to Issue count and Time tracking to None.
3. Estimates before the start
Work with no estimate counts as zero in a story-point burndown. And an estimate added or changed after the sprint has started shows up as a scope change, not as progress.
4. Sub-tasks do not carry points
Story points on sub-tasks are not counted: only the parent’s points move the line, when the story is done. Put the points on the story. Time estimates on sub-tasks, on the other hand, do roll up to the parent.
5. Scope change is a step up
Work added to the sprint after it started, or an estimate raised, makes the line go up; work removed, or a done item reopened, moves it too. The table below the chart lists each change with its date. A burndown that climbs is not broken: it is telling you the sprint grew.
6. Weekends and the ideal line
By default, the board skips Saturdays and Sundays, and the guideline stays flat on them. Add your holidays, or change your working week, in Board settings › Working days so the guideline is accurate.
Team-managed projects
These board settings don’t exist there. Estimation is set in Space settings › Features › Estimation, with story points or time, and weekends are left out by default; working days can’t be changed.
When you want it on a dashboard
Clearlane Sprint Burndown puts the chart on any Jira dashboard: work left each day against the ideal line, scope added or removed in plain sight, work items or story points, sub-tasks and weekends if you want them, and one sentence that says whether the sprint is on track. Every number opens the work items behind it. We heard “why is my burndown flat?” too many times. So we made the chart explain itself.