Issue added to sprint with incorrect remaining hours

After a sprint was started a new issue was added. There had already been some work done on the issue but when it was added to the sprint it had 12 hours remaining but 77 hours are added to the sprint making the burndown completely wrong.

1 answer

0 votes
Ahmad Danial Atlassian Team Oct 06, 2013

Hey there, Guðjón.

It is a default behavior of GreenHopper's Burndown Chart to show the incorrect value when you added new issue(s) to the active sprint. The rule of thumb of Scrum is that when a sprint has started, no new issues should be added or removed to ensure that the data is accurate and the chart is plotted correctly.

In the future, ensure that you plan the sprint and ensure that all the necessary issues are added into the sprint before you start it. Hope this helps.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

213 views 0 5
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you