why closed story moved to next sprint or backlog when complete the sprint

[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.

[John Funk · Accepted solution]

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. 

[Changlin S]

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)

[John Funk]

Yes, you should have a resolution for all issues, also. 

[Changlin S]

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

[Changlin S]

@John Funk  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.

[Changlin S]

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?

[John Funk]

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

[Changlin S]

@John Funk  thanks, configured all the board, and observe how will it behavior when next sprint comes.

[John Funk]

Best of luck!

[Changlin S]

@John Funk  we configured all board in same jira project, scrum or kanban board, set columns configured end status to last column, but this problem comes out again.

And want to confirm another scene: 

There're some scrum boards and kanban boards with the filter on same jira issues in this jira project, will this scene matter when move to next sprint? 

The filter of Kanban board like this:  project in (ESAS, B-MAP) AND issuetype in standardIssueTypes() AND sprint not in closedSprints() ORDER BY Rank ASC

[John Funk]

If you are using multiple scrum boards, that might be the problem. Especially if the issues are not in the last column on all boards. 

[Changlin S]

All the scrum boards' last column already aligned.

The suspect might be that there're also kanban board in same jira project, if this impact the move action.

[John Funk]

Yes, I would suspect that is the problem. 

[Changlin S]

Well we still stuck in this problem. It's complicated, we have many projects and managed with same sprint cycle, and different project may have different sub-task types and also may have different ending status.

But for the story shown sub-tasks incomplete, we checked and confirmed they're in ending status, and resolution is set with values.

we also have many boards in different projects, I tried to confirm them in the last column in projects that shown incomplete, but this still not works for me.

I tried to find what the action exactly did when do the 'complete sprint' clicked, but with no lucky.

any further suggetsions? thanks

[Changlin S]

Give one example here:

The 'Tech-Story' for manage the sprint bugs, status=Closed, and all sub-bugs with status 'invalid' or 'closed' and resolution like below, the 'tech-story' still moved to next sprint.

[John Funk]

Can you share a screenshot of board configurations for the Columns? Especially the last handful of columns and the mappings to the statuses.