Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Agile Project Burn down Chart not reflecting scope change.

Ferdinand Espedido
Ferdinand Espedido August 31, 2015

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? 

Answer
Watch
Like Be the first to like this
291 views

1 answer

0 votes
Pilar
Pilar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
September 2, 2015

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

Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira Software
TAGS
AUG Leaders

Atlassian Community Events

    See all events