Problem with replanning stories to the next sprint

[Aude_Reynaerts]

Hi all,

I've just closed our sprint (my first time) and I've chosen for the option to replace incomplete issues to our new sprint.
The only problem is: subtasks of uncompleted stories who were done already are also replaced to this new sprint. So now it seems, that on our first day of the sprint, we've done already a big amount of subtasks. What do I have to do now?
And how can I make sure these will not be counted in our statistics as "done in sprint 8"? (as they were done in sprint 7)

Thanks for your help already!

[Petter Gonçalves]

Hello @Aude_Reynaerts

Welcome to the Atlassian Community!

You are correct to say that completed sub-tasks are moved along to the next Sprint if its parent is not complete. This behavior works as intended and happens because the sub-tasks are in the scope of the same amount of work on the board.

Additionally, you can check in which Sprint a sub-task was completed by checking the sub-task history individually, however, this information will not be displayed in the board reports at all.

We understand that in some scenarios our customers expect it to work in a different way, so I created a new feature request for Jira Cloud application to make sure your feedback will be received by our Product managers:

Hide Completed subtasks from the previous sprint in the current sprint 

Feel free to vote and watch in the suggestion to increase its priority and also receive notifications about any updates.

For now, if you want your sub-tasks to be removed from the board when completed in an independent way, I suggest using the Epic -> Story relation instead of Story-Subtask:

Learn how to use Epics in Jira Software 

Let us know if you have any questions.