The burndown chart lines are not going down and not able to see other lines?

[Satyajit Baral]

The burndown chart lines are not going down and not able to see other lines?

Alos logged hours but the line is not going down?

Also, my burndown chart not showing below: Is there a setting change? 

• Work scope

• Scope projection

• Completed Work

• Guideline

[Nic Brough -Adaptavist-]

Your burndown chart looks like you started a sprint with no estimated items in it, and have then started adding estimated items into it.  You can't burn down if you do that - the sprint needs to record the estimates at the beginning of the sprint, and in this case, it's starting at 0 and has nowhere to go.  I suspect the burndown and guidelines are actually being drawn in the chart, but as every point on them is 0, they're a simple flat line along the x axis at 0

[Satyajit Baral]

My question is how all the three lines are reflecting in the Burnup chart, not in the Burndown chart??  I know I made a mistake by first stating the spring then added the stories to the sprint and then points!! 

[Nic Brough -Adaptavist-]

Burn up doesn't start from the included estimates at the beginning of the sprint.  It starts at 0 and simply adds what is marked done as you go.

[Satyajit Baral]

1. Thank you for all the answers, my next question is there any guiding steps on how to have a proper burndown chart. Now I know, first I have to estimate then pull the stories to sprint. Any other references, docs, videos?

[Nic Brough -Adaptavist-]

https://www.atlassian.com/agile/tutorials/sprints is probably a good start!

[Vinod Ramadoss]

Hi,

This could be because the Y axis measure is in story points, so once the user story is closed its corresponding story points will be accounted for closure and there will trigger a dip in the burn down chart. Hope this helps.

[Satyajit Baral]