Agile Project Burn down Chart not reflecting scope change.

[Ferdinand Espedido]

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? 

[Pilar]

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

Pilar