It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Burndown chart does not process removed hours from sprint

Due to several reasons I had to replace some tasks with new tasks from the backlog, while the sprint was already started.

The tasks I had to remove were estimated at 40h and the tasks I've put into the sprint are 40h as well. According to my calculations there should be a drop in the 'remaining hours' line in the burndown chart when I remove the tasks and it should go right up again when I add the new tasks to the sprint, making it show the initial amount of remaining hours as before I swapped the tasks.

Unfortunately, the burndown chart only shows the hours that are added, without removing the hours of the tasks that have been removed from the sprint.

How come? Is there any way I can prevent this from happening? In my opinion the burndown chart is not accurate anymore. See below.

Schermafbeelding 2014-10-07 om 14.11.40.png

1 answer

Anyone has an answer?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Halp

Halp - Conversational Ticketing Help Desk for internal requests

From the Halp Team Howdy!  👋   We’re Halp, a conversational ticketing help desk for all of your internal requests in Slack (and soon to be MS Teams!). We’re excited to be a par...

57 views 0 2
Read article

Community Events

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

Events near you