nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sprint burndown chart - flat / increasing line

Ola Czyż

Hi everyone! I am wondering why my sprint burndown chart doesn't work properly. The team is working over the task in sprint and change the statuses for DONE (currently 28 story points is done), but the number of remaining story points is not decreasing. What would be a reason of such a case? I'd appreciate your answers!

Zrzut ekranu 2023-03-3 o 11.24.10.png

Accepted answers

Trudy P Claspill

Hello @Ola Czyż

Welcome to the Atlassian community!

When you say you are changing the issues statuses to DONE, is that resulting in the cards being displayed in the column farthest to the right on the board? If not, then the burndown chart does not consider the issues done. Only issues in the right-most column of the board are considered done for burndown charts. Here is an example:

I have two "finished" statuses; one named Completed and one named Done. These are in separate columns on my board.

I have moved one story to the COMPLETED column, which is not the column farthest to the right.

Screen Shot 2023-03-03 at 9.58.13 AM.png

You can see below that the points show up in the green/Done lozenge when I look at the sprint in the Backlog.

Screen Shot 2023-03-03 at 9.58.29 AM.png

But there is no evidence of burndown.

Screen Shot 2023-03-03 at 10.00.09 AM.png

If I move the issue to the right-most column

Screen Shot 2023-03-03 at 10.01.15 AM.png

...then the burndown chart will show the points as burnt down.

Screen Shot 2023-03-03 at 10.01.28 AM.png

All comments

Patricia Francezi_iDev_

hi @Ola Czyż

welcome to the community!

The burn down chart depends on the estimation statistic that is configured in your board.

If you have configured to Story Points, and if your story has no story points it wont deacrese.

If you have added the Story Points information or new tasks during the sprint the red line will increase (I assume it happened due to the line increasing).

For mor info https://www.atlassian.com/agile/tutorials/burndown-charts

Ola Czyż

Hi @Patricia Francezi_iDev_ Zrzut ekranu 2023-03-3 o 16.09.29.png

Thanks for the answer!

I've got estimation configured on Story Points, ale Story Pints within sprint are estimated (please find in the screenshot). I can understand, that the red line increase due to the changes and adding another tasks, but the thing is - why the red line does not decrease, while more stories are marked as read, so the number of ready Story points increases and the number of story points to do decreases. Do you have and idea why it can behave like this? Thanks is advance for your help!

Trudy P Claspill

Hello @Ola Czyż

Welcome to the Atlassian community!

I have two "finished" statuses; one named Completed and one named Done. These are in separate columns on my board.

I have moved one story to the COMPLETED column, which is not the column farthest to the right.

Screen Shot 2023-03-03 at 9.58.13 AM.png

You can see below that the points show up in the green/Done lozenge when I look at the sprint in the Backlog.

Screen Shot 2023-03-03 at 9.58.29 AM.png

But there is no evidence of burndown.

Screen Shot 2023-03-03 at 10.00.09 AM.png

If I move the issue to the right-most column

Screen Shot 2023-03-03 at 10.01.15 AM.png

...then the burndown chart will show the points as burnt down.

Screen Shot 2023-03-03 at 10.01.28 AM.png

Ola Czyż

@Trudy P Claspill Thank you very much! It was an issue, I've moved the tasks and now it works!

Crimsalytics

We always found it difficult to understand why a burndown chart looks the way it does. I've personally spent hours trying to track down the specific issue changes that caused spikes or flat areas in a burndown chart.

As a result, we built an Analyze Burndown Changes feature into the Crimsalytics Red Line Burndown chart. It works by aggregating the changes to the estimate (story points or time depending on the mode) for each issue on every day there was at least one change. The resulting data is presented in a table that is filterable and sortable.

You can click on a change and it will highlight the corresponding point on the burndown chart so you can quickly see what is happening. Alternatively you can filter the chart to the zoomed in data range or manually enter start and end dates to reduce the change set to a specific period of time.

5 LargeFull - analyze changes.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud