nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

story - done.png story - sub-tasks.png Sub-task 1.png Sub-task 2.png Sub-task 3.png Sub-task 4.png Sub-task 5.png Sprint Complete and Start New.png

Accepted answers

John Funk

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.

All comments

John Funk

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)

scrum board.png

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?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

unknown-hosting-type

jira-unknown-hosting-type