when adding issues to a sprint, which has already been started, the guideline at the burndown chart will not be corrected.
So when the sprint has 0 issues at the start and i will add 5 issues with several story points, the guideline is not corrected and will stay at the buttom of the graph (at 0 story points).
Is this a know bug or a desired behavior?
Answer from Atlassian:
"This is actually an expected behaviour for the Burndown Chart Guidelines to be flat in the bottom of the char., The reason of this behaviour is because the estimated of the sprint should be already decided before the start of the sprint, if there is a scope changes such as the estimation changes or another story included in the sprint while the sprint already started, the guideline will same stays. I believe that the guideline changes is to prevent confusion to the team who looked at the board, as the scope changes after the sprint started is not recommended.
I might not able to explain it clearly, but there is a bug ticket that have been raised for this in which include the comment/answer of this behaviour:
I hope this could clarify it and thank you for your patience."
But still there still cases where I need to the change the guideline - adding capacity:
1. one cancel his/her vacation, or
2. add more devs into the sprint.
In these cases, how can I move the guideline up for certain amount of time to reflect the capacity increase?
Some of us aren't perfect, don't have time to prepare the Sprint properly and it happens the MORNING after the sprint started. So I get a guideline in the burndown chart that reflects this. Sure , its my bad and I am not playing by the "rules". It is the real world or at least my reality. So what I would really like is a button that RECALCULATES the guideline whenever I want to.
In my world things change, I don't like it all the time but it would be great to be able to adapt on the fly with changing resources and tasks that happen for whatever reason.
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG