nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Guideline is not corrected when adding issues to sprint after sprintstart

Thomas Soring

Hi,

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?

Thanks

Accepted answers

Thomas Soring

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:

https://jira.atlassian.com/browse/GHS-6525

I hope this could clarify it and thank you for your patience."

All comments

Mike Sorensen

It is working properly.

You should not have started the Sprint with zero story points if you expect any value from the burndown chart.

Thomas Soring

Answer from Atlassian:

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:

https://jira.atlassian.com/browse/GHS-6525

I hope this could clarify it and thank you for your patience."

David Balcaen

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.

Dinghao_Zeng

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?

Jack Brickey

You cannot change the guideline after sprint starts. Any changes in estimation will be recorded as churn as it should be. The guideline is a static capture of the plan at the time of commit.

Yavor Hristov

Real life happens, people get ill, customer changes their opinion, a hurricane, etc... you should be able to recalculate.

Aron Silan

100% agree. Theory and reality are completely different. Maybe atlassian should consider taking feedback from people using this tool in an ever changing environment where tickets do get added/updated during a sprint!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software