why closed story moved to next sprint or backlog when complete the sprint
Asked by Changlin S:

Hello,

We met the weird scenario that the story and it's sub-tasks already closed (we suppose), but when complete current active sprint and move to new sprint, Jira pop up the hint to move the issue not completed yet, and the story was in the list, this is not as our expectation.

Detail Description below:

Story with status Done and resolution Done, this jira issue has several sub-tasks, and all set to end status and resolution value, details as below pics (story status, sub-task status and sprint change activity).

But when complete current active sprint to start a new one, this closed story still moved to next sprint, don't know why and how to fix it, please give a help.

![story - done.png](/t5/image/serverpage/image-id/338844iDAD058BF955DC35B/image-size/large?v=v2&px=999 "story - done.png")![story - sub-tasks.png](/t5/image/serverpage/image-id/338847i3CC378AD7C27AFBE/image-size/large?v=v2&px=999 "story - sub-tasks.png")![Sub-task 1.png](/t5/image/serverpage/image-id/338845i8AE18DA2D9D5C7C6/image-size/large?v=v2&px=999 "Sub-task 1.png")![Sub-task 2.png](/t5/image/serverpage/image-id/338846iDE14EE24859351C1/image-size/large?v=v2&px=999 "Sub-task 2.png")![Sub-task 3.png](/t5/image/serverpage/image-id/338848i5E7C6DEC1CFB4C4F/image-size/large?v=v2&px=999 "Sub-task 3.png")![Sub-task 4.png](/t5/image/serverpage/image-id/338849iBA7403769996FFA8/image-size/large?v=v2&px=999 "Sub-task 4.png")![Sub-task 5.png](/t5/image/serverpage/image-id/338850iD3265B0002AD4825/image-size/large?v=v2&px=999 "Sub-task 5.png")![Sprint Complete and Start New.png](/t5/image/serverpage/image-id/338851i53AA5F3EF6497B5C/image-size/large?v=v2&px=999 "Sprint Complete and Start New.png")


Answers:
author: John Funk
body: Hi Changlin - Welcome to the Atlassian Community!

The cards must be in the very last column on the scrum board to be considered Completed. Including the Sub-tasks. Regardless of the status, they must be in the far right column.

comments: author: Changlin S
body: Thank you John for answer,

yeah I searched and found your solution, and tried, but still moved from June (searched and checked the board configuration as the solution suggested) to July.

See image below, sub-tasks already in last column with strikethrough.

BTW, the field 'resolution' in the status workflow must not be empty, right? (All sub-tasks already set value on this field)

![scrum board.png](https://community.atlassian.com/t5/image/serverpage/image-id/339001i27868EEC8EDEDCFB/image-size/large?v=v2&px=999 "scrum board.png")


author: John Funk
body: Yes, you should have a resolution for all issues, also.


author: Changlin S
body: All conditions already set as required, not sure why this story still behavior likes this, any other configure missed?


author: Changlin S
body: [@John Funk](/t5/user/viewprofilepage/user-id/7148) Hello again, is the assignee mandatory for this action check? This issue happened again, and I checked the new issue that it had sub task with assignee 'unassigneed', and when I looked back to the old issue, that one had the same situation that had sub task with 'unassigneed'. Please help if this field will be checked when complete sprint and move issue to next sprint.


author: Changlin S
body: There're multiple scrum board in different jira project, if the jquery contains the issues, maybe it will cause the move action to next sprint?


author: John Funk
body: No, the Assignee does not have to be set. Yes, if the issue shows up on multiple scrum boards, that could be the problem.


author: Changlin S
body: [@John Funk](/t5/user/viewprofilepage/user-id/7148) thanks, configured all the board, and observe how will it behavior when next sprint comes.


author: John Funk
body: Best of luck!


Tags: jira-unknown-hosting-type

unknown-hosting-type