Should I clone a spillover userstory?

[Kasey C]

Hi all,

There are some spillover user stories for each sprint, if I move them to next sprint, then the spillover record will be disappeared when I export a report.

Is there any way that I don't need to clone them but can keep them as my spillover record while moving them to next sprint?

Thanks a lot!

KC

[Nic Brough -Adaptavist-]

No, you should not clone them, you're right in that it will make a complete mess of your reporting and sprint processes.

>if I move them to next sprint, then the spillover record will be disappeared when I export a report

That's not how sprint reporting works.  The record that an issue was in a sprint, but did not get completed, is recorded.  The sprint field records all the active sprints an issue has been in.

For what it's worth, you shouldn't care about reporting on issues that get moved into the next sprint.  It should not happen often, and when it does, the team should be looking at why it did in the sprint retrospective, with a view to fixing the problem that caused it to go over.

[Kasey C]

@Nic Brough -Adaptavist- 

Thanks for your reply.

For those spillover issues, we will move them to another sprint.

However when my teammate try to export burndown chart of the some sprints, the spillover issues will not indicate in the original sprint but in the new sprint.

Is there any way to allow the spillover issues to indicated in original sprint as Spillover, but also as normal issue in new sprint?

Thanks a lot.

[Nic Brough -Adaptavist-]

No, that would completely misleading for your product owners and start double-counting things.  It will not work.

[Kasey C]

When I tried to export a burndown chart, I will have to manually add the bars for spillover issues. Thats why I 'm thinking to clone the issues for next sprint, so that the original can be kept for our record. 

But then there will be more issues in our system may cause confusion to my teammates.