I want to "Complete Sprint" with sub-task not being in status "Done".

[Paramee Ratanabirabongse]

I want Jira to help me automatically move my stories to the next sprint while keeping the statuses. I used to be able to do that with sprints (when I was playing with Jira) but I'm not sure whether there were subtasks in those stories.

[Nic Brough -Adaptavist-]

Jira will move open stories to the next sprint when you close the current sprint, without any status change.

The story will take its parts with it (sub-tasks are part of a story, not separate items, and hence are "in a sprint" when their parent is)

Note that there is a case where Jira will block sprint completion - when you've managed to set up your workflow to allow your stories to be put in a state where they are done but not done at the same time.  It is possible to set up Jira to allow someone to put a story in a "done" status when it has not-done sub-tasks.  This is clearly nonsense - a story can't be done if bits of it are not done, and Jira can't handle that because it doesn't know whether the story is actually done or not.  If you have open sub-tasks, then, by definition, the story must still be open or in progress.

[Johannes Haase]

"This is clearly nonesense ...".

I don't think so. You can have completed the Story by itself but you can still have Subtasks which turned out afterwards not to be needed. For this, we have introduced the status obsolete. However, by this behaviour we cannot finish the Sprint when we have Stories that are actually completed but have Subtasks other than status Done - which is very inconvenient. We had to unlink the last column of the Scrum board from the obsolete status because the usability was very bad so that Subtasks became, unaware by the Jira-User, obsolete who have drag&dropped the subtasks there with the intention to bring it to the Done state. Furthermore, keep in mind that the ordinary Scrum team has no permission to close/delete a Subtask, so we need this status obsolete.