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; } } }

Split a story and move all undone subtask with it

Mortada Haddad

Hello out there

When splitting a story and moving it directly to next sprint

The story will be moved, but not the subtasks, this forces you to recreate all subtasks.

Is possible to move all undone sub-tasks with the story?

Either move all subtasks with it, or keep the "done" subtask in the first sprint and move all "undone" subtasks to the next

Any help appreciated

Accepted answers

All comments

Tinker Fadoua

Hi Mortada,

Can you please include some screenshots from your board configuration?

Something has been configured the wrong way as you should be able to move a story with all its subtasks to the next sprint without problems.

Mortada Haddad

Hello Fadoua
Thanks for your reply

When you say board configuration, which settings do you means?

Regarding my questions, its only when splitting a issue, the subtasks do no move with it.

If i close a sprint, or use move, the subtasks will go with the parrent issue.
But if i right click and choose split issue, and move it to the next week, it will only split the issue but not the subtasks

Tinker Fadoua

What about cloning the unfinished story so that you don't have to re-create the subtaks?

Nic Brough -Adaptavist-

Splitting a story is not really the right thing to do. If you have not finished the story in this sprint, then you have not met what you told your users you were going to do and you should move the whole thing to the next sprint, with all its existing subtasks. Splitting an issue because you didn't complete the sub-tasks in this sprint is not how Scrum works, so Jira has nothing to help you do it. If nothing else, it completely messes up all the numbers you're trying to use Scrum to get to.

Splitting an issue is something you should be doing in grooming, not during a sprint, and during grooming, it's very common not to have sub-tasks - adding them is often part of it. (At the latest, splitting should happen when you're doing sprint planning and realise an issue is too big or complex to commit to. At which time you might not have any subtasks).