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

This widget could not be displayed.

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 Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

292 views 5 0
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