Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Burndown chart

Anne Jensen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 16, 2018

Any suggestions to why this burndown looks like this?burn_down_chart.png

2 answers

1 accepted

3 votes
Answer accepted
Mikael Sandberg
Community Champion
March 16, 2018

It looks like that because the sprint was started without any issues assigned to the sprint. Issues where added after the start and that is why you see the spike at the beginning, and it is also why you do not see the guideline.

Anne Jensen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 19, 2018

The sprint was started before the issues. Thanks, now the guideline is shown

0 votes
Mauricio June 7, 2018

Have a similar behaviour... Thanks for the answer.... 
One question more .... 

Why I haven´t I got the grey line to compare with my Team velocity? I had it on previous Sprints...

Jira_forum1.png

 

Jira_forum2.png

Mikael Sandberg
Community Champion
June 7, 2018

@Mauricio Ferreyra If you look at the chart for your current sprint, you have a gap from when the sprint was started until you added issues to the sprint, and that is why you do not have the guideline. Same issue as above.

In order to see the guideline you have to add issues to the sprint before it is started.

Mauricio June 7, 2018

Strange @Mikael Sandberg, because some issues (not all) were added before sprint was started.
The problem I had was that some histories were differed from previous Sprint
Is it any turnaround to bring back my sprint guideline?

Mikael Sandberg
Community Champion
June 7, 2018

Did the issues you had on the sprint have estimates on them? The guideline is based on the sum of estimates, so you have to make sure all issues are estimated.

The only way to bring the guideline back is to start a new sprint.

Mauricio June 7, 2018

Seems I'll have to wait and have much care on next sprint...
Thanks a lot @Mikael Sandberg

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events