Closing sprint with open issues being added (instead of moved) to next sprint

[Venkata Ramana Kaza]

While closing a Sprint, letting Jira move open issues to one of the future sprints, is showing such issues as scoped for multiple sprints. See attached image.

Is there a reason why Jira adds sprints than just updating it? I am under the impression that this messes up the Sprint Report and any custom filters. Hence I move them explicitly to next sprint (through bulk edit), ensure there are no open issues and then close the sprint.

Looking for inputs on what is the best way of handling open issues while closing a sprint.

Thanks & Regards,

Ramana.

[Ste Wright · Accepted solution]

Hi @Venkata Ramana Kaza 

I'd say the behaviour in Jira is correct.

You want to know when an issue has been in a sprint before and had to move between sprints. You want the Sprint Report, Burndown, etc to show where scope was incomplete so you can have a discussion about why this happened - for example, was the issue too low of a priority? Was it not ready to be built? Was it blocked? Or were the sprints over-capacity.

If you remove it from an open sprint and add it into the next sprint, you're losing these data points and it won't be clear when an issue moves sprints over and over. 

Whilst the target is for a sprint to be "complete" within its timebox, that is in an ideal world which rarely exists. If issues are moving into multiple sprints, you need to know and be asking why this might be.

Ste

[Venkata Ramana Kaza]

Ok. Thanks @Ste Wright for the quick response