Can I move sub-tasks to different sprints??

[Bunty]

Hi Everyone,

There are cases where a particular Feature could extend over more than a Sprint.
In such cases, we would want the sub tasks that are divided underneath the feature to be assigned to different Sprints.

Is it possible?

Thanks,

Manikanta.

[Nic Brough -Adaptavist- · Accepted solution]

>There are cases where a particular Feature could extend over more than a Sprint.

In "proper" scrum, that means you are not breaking up your stories enough and you need to look at improving your grooming.  Stories should fit within a sprint.

In real life, people do have stories that are too large, and when that happens, a story should move to the next sprint in its entirety, taking its subtasks (open and closed) with it.

Moving a sub-task into the next sprint is automatic - it moves with its parent when you close the old sprint.

Putting sub-tasks into different sprints is wrong and broken, and hence not possible in Jira.  If you want to do it, then you have stories that are not broken down enough - look at fixing that instead.

[Chase Flinn]

That's subjective and rigid way of looking at things. Stories should ideally be completed in a sprint but since agile promotes continuous flow a story can start whenever in a sprint due to various reasons. 

Splitting stories into horizontal portions of work to make them fit perfectly is a worse practice then having a story that represents an outcome but maybe is a little bit bigger and might roll over if we arent starting it the first day of the sprint. Stories are supposed to be outcome based, not based on a technical stack or unusable increment. 

When it comes to capacity planning it would be useful in some situations to be able to move a subtask portion of the technical requirements to the next sprint if we know we wont finish it this sprint. 

[Nic Brough -Adaptavist-]

No, I'm afraid you do not understand scrum or agile processes here.  Carrying over work into the next sprint is a sign that your team has failed in some way, and need to change their process.  Whether its a failure to decompose your stories into manageable pieces, your estimation is not right, your team is trying to take on too much work, there are unplanned interruptions, etc, etc, etc.

Stories are indeed supposed to be outcome based, but the whole point of a sprint is to deliver an increment.  You can't do that if you carry things over - the whole point is that a carry-over is a failure.

[Deleted user · Accepted solution]

Hi @Bunty,

You cannot. The Sub-tasks are part of their parent, and it's the parent that moves from sprint to sprint.

Thanks,

Swathi