Replaced a Story with Another but sprint burndown chart shows as a scope change?

I had to delete a story and replace it with another one because we forgot to clone a template we created. We deleted CRM-4527 and replaced it with CRM-4595. The issue is that if you look at the sprint burndown chart in JIRA, it shows the increase in story points because of the new story, but it doesn't show the decrease as a result of the deletion of the old story. As a result, it looks like there was ascope change for the sprint, when there really wasn't. Can you please look into this and fix this issue?

1 answer

1 vote

I think the way Jira sees this is a scope change.  One the sprint starts any additions is a change.  If this is done before the sprint starts there is no issue.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Sarah Schuster
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

11,965 views 15 13
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