Agile Project Burn down Chart not reflecting scope change.

One of my developers had a 'place holder' task within a story worth 80 hrs. He then added a bunch of 'real' tasks adding up to 80 hours. He then deleted the orginal task of 80 hours. The scope reduction did not reflect on Burn Down.  Is this normal behavior on a deleted task? How can I reduce my Sprint scope by 80 Hrs to make the burndown accurate? 

1 answer

Can you try removing the placeholder task from the active sprint instead of directly deleting it.

May be it is a bug with jira-agile.

If you remove it from the sprint then the scope change will reflect


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,327 views 14 20
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot