Burndown chart doesn't show scope change for issues that has two values in Sprint field

Situation:

We planned sprint and included not completed issues from previous (closed) sprint. The new sprint has been started and after some time we removed from this sprint one of the issues that was in previous sprint. This was not reflected in Burndown chart, scope does not changed, all looks like removed issue never was in this sprint. Is this expected behavior? 

1 answer

We use JIRA 7.12 server version.

 

My suspicion is that the issue's Story Points are counted in the first sprint to which it was assigned.

 

Once you removed it from the second sprint, the points counted 'backwards' to the previous sprint -- without showing the SP drop in the second sprint.

 

Do you know if the total SPs *increased* in the first sprint, after you removed the second sprint from the issue?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

22,405 views 2 7
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