My project's burndown chart constantly shows a flat red line. Is there something I have misconfigured or not had the team update a field in the User Stories? Any assistance would be greatly appreciated.
Are you estimating the issues with story points, hours, or another field? (Note - not sub-task types, only the story level stuff).
Is that the field selected in the estimation statistic for the board?
Are all the issues you expect to be burned down in the far-right column of the board?
Thanks for the reply. No I couldn't move the stories to the far right b/c I work with a gov't entity and user story isn't done until it goes through a through security scan. That being said, we deployed over the weekend and I have moved about half of the user stories to the far right (which is Production) for our team. This is what the Burn Down Chart looks like now. It's still looking messed up.
The burndown chart you would look like that if you had been moving the stories to "done" during the sprint. You've moved them all at the end of the sprint and you've been adding points into the sprint during the execution. The graph can only go on the information you give it.
This looks like you started the sprint with no issues that had estimates on them, then added issues with estimates into it, or added estimates to the items in the sprint.
As you started with a zero estimate, your guideline is there, it's just drawn over the x-axis - a grey line at 0!
Both of those are saying you added a pile of estimated issues to an active sprint on April 6th.
I am not sure why you have done this, it is of no help repeating the same thing that broke your sprint report before. As I said before: A new sprint, started after estimated issues have been put into it
Ok, maybe I misunderstood. So what I need to do is to create a sprint where the Start Date is after the moment the estimation was done for all issues?
Because what I did now is to delete my previous Sprint and removed all the issues that were in it. I put all issues back to the backlog and they already have been estimated. However, my team started working on all those tickets on March 8 so this is why I put the Sprint Start Date to March 8.
I recreated the Sprint and added my issues again.
No. Forget the dates and historical work, they do not matter. The process this stuff is designed to support is:
The important thing here is that you start a sprint with a list of issues, with estimates, that you think you can do within the sprint.
thank you for your detailed response. This is exactly the process I followed. This is why I don't understand why the Guideline (Gray line) is still flat and what I don't see the Time Spent Line (Green line).
Like mentionned by another user in this ticket, I'm also expecting a graphic that has the guideline going down and seeing if my progress (time spent) is above or below the guideline.
We want to be able to see if we are on track on the work that has been estimated. This is why we would like to have a burndown chart that is representative.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events