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; } } }

How do I view the guideline on the rapid Burndown Chart?

Dafydd

I'm trying to create a decent burndown chart for the team using the rapid board feature, but the chart is missing a guideline (see screenshot), even though it's mentioned in the legend on the right. Can someone tell me what I'm doing wrong please? Thanks!

screenshot

Accepted answers

Marlon Aguiar

Hi there,

By looking at your chart I believe that you added some issues after starting your sprint (scope change), the problem is that the that the burndown chart guideline is generated when the sprint starts, and it will not get updated when scope change happens, so the guideline is there but is in zero. Starting your sprint with issues in it should solve your problem.

Hope it helps.

Regards,
Marlon

All comments

Marlon Aguiar

Hi there,

Hope it helps.

Regards,
Marlon

Jim Strange

Are we talking about Greenhopper here? If so, I have the same problem. I added Story Points to stories, then added them to the sprint, then started the sprint. The "Guideline" is flat zero all the way along.

Dobroslawa Wierzbicka

It might also be the case that it was the estimates that were added after the Sprint was started - then the guideline will be flat as well.

Dobroslawa Wierzbicka

Is your Board set to use Story Points as the estimate value? If it's using time tracking values, the guideline will be flat (if no time estimates were added).

Jim Strange

"Estimation Statistic" is set to "Story Points", "Time Tracking" is set to "None" on the board config page.

Jim Strange

Does nobody know the answer to this!?

Jim Strange

Right, it was my own stupid dumb fault. I started the sprint before adding the user stories to it. I'm red-faced now...

Nils Winkler

I just ran into the same issue. The Sprint was started at the beginning of the Sprint Planning session, then the stories were added, broken down into tasks, and then the estimation (in hours) of the individual tasks was done. Since the Sprint was already started, all of the stories were listed as Scope Change at the bottom of the page.

To solve this, I went back to the planning board and changed the start time of the Sprint to the end of the planning session, right after all of the estimations were done. Going back to the Burndown chart, I can now see the guideline, which previously was going from 0 on the left to 0 on the right.

Mark Duerden

This worked for me too. I clicked on the down arrow next to the Sprint Title on the Board > Work View page and was able to move the start time for the sprint to after the time the issues were added.

Balvant Biradar2

Thanks Nils. Really it helped me

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud