Carrying over tasks/subtasks from one sprint to the next doesn't carry the task

Question

I am new to Jira and trying to understand how to properly use it.  We have a task, deliver XYZ that we have subtasks 1-5 for and we only complete 1-3 in the current sprint so I want to carry the uncompleted 4-5 over to the next sprint.  When I close the sprint and tell it to carry the unresolved items forwrad, the Task didn't carry just the sub-tasks did so now I have orphaned subtasks that are just in a jumble in an Other Issues lump at the bottom.  I would prefer to have the task come with the subtasks so we can keep the work together.  Is there a way to do this?

Shirley_q1an3i · Answer

I agree, Michele. Currently, splitting an issue allows splitting the story points and creates a split link but does nothing about the sub-tasks. My team uses a clunky work-around of cloning the issue and sub-tasks instead. If only a couple of the sub-tasks are needed in the split story then we clone the sub-task in the original story and move it to update the story parent. Like, I said, very clunky.

Michele Mast · Answer

Splitting the issue did NOT carry over all of the sub-tasks related to it which was the original ask I was trying to address.

Jira Guru · Answer

Right-click an issue and select Split issue. You can split an issue in the Backlog or sprint sections, including any future sprints and any active sprint.

Splitting an issue is useful when an issue is so big that it's better to divide it into two or more issues to make work more manageable.

What happens when I split an issue?

* If you split an issue in the Scrum backlog, the new issue will be sent to the Backlog section.

* If you split an issue in one of the sprints (future or active), you can choose to send the new issue to either the backlog, or a future or active sprint.

What happens to the issue details?

* The new issue will be of the same issue type as the original issue. For example, if you split a story into two or more issues, the new issues will also be stories.

* The new issue will have most of the same details stored in the original issue, including priority, component, and label.

* The issue details that won't be copied over include work log, comments, issue history, and issue links, though the original issue will be linked to the new issue.

* The new issue will have the summary that you entered upon splitting the issue.

* If the original issue has estimates, you'll be able to enter estimates for the new issues as well. You can also update the estimate of the original issue as necessary.

* The issue status also returns to the first step of the corresponding workflow, and the resolutions are cleared.