I probably need to switch a setting to get the "proper" burndown chart view that show the decreasing guideline and actual performance. What I get now is the RED line (remaining hours) and the GREEN line (Time Spent(
One option is close/delete the current sprint, re-create a new sprint and make sure to associate the stimated task before starting the sprint. But, another way to solve this (Burndown chart does not show ideal guideline) is to make sure all estimates have story points, and then change the day or time of the sprint start until you recognize the initial story points and displays the ideal guideline.
Hi @Clive Enoch, and welcome to the community.
Unfortunately, you have run into a known behavior of Jira: When a sprint starts and no work with estimates has been assigned yet, the ideal guideline doesn't appear.
See this Atlassian post for more info: https://confluence.atlassian.com/jirakb/missing-guideline-in-the-burndown-chart-779158658.html
Please consider not starting your sprint(s) until the work is added during planning.
A better product solution to this issue would have been to make the guideline dynamic, responding to both the original scope, changes, and the remaining actual scope over time. That is what I do when I export Jira data to tools like MS Excel to create more useful burn charts.
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
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