Is possible to have a sprint field for a sub-task

Question

Hello

I want to know if it is possible to have a sprint field for a sub-task

In case of YES, is the sprint value of the differents sub-task linked to a storie can be different between the different sub-tasks  and between storie and sub-task

THANKS

Shalini Pradhan · Accepted Answer

Hello @Florence PICARD ,

Good day! Welcome to Atlassian Community :)

Yes, a sub-task does show a Sprint value in Jira, but it automatically inherits this value directly from its parent workitem. You cannot independently assign or manually edit the Sprint field on a sub-task as it is tied to the parent issue's sprint.

Thank you!

Joseph Chung Yin · Accepted Answer

@Florence PICARD

Unfortunately, you cannot assign a sprint to a sub-task issue.  It automatically inherit the sprint field of their parent issue.  Furthermore, when the parent issue rolls over to a different sprint (i.e. not completed in the current sprint), all of its subtasks automatically rolls over.

Hope this helps.

Best, Joseph Chung Yin

Piyu@Appcento · Accepted Answer

Yes, sub-tasks carry a sprint value of their own. A new sub-task picks up the sprint from its parent story, and you can then move a single sub-task to a different sprint, so they can differ from each other and from the parent. The catch is reporting, a sub-task sitting in another sprint drops out of that story's sprint view and skews the burndown, so most teams keep them aligned. Your board filter usually pulls sub-tasks in anyway, so the work still shows on the board even when the sprints do not match.

Anwesha Pan · Accepted Answer

Hi @Florence PICARD

As already everyone mentioned that by default in Jira, sub-tasks cannot have an independent Sprint field value, nor can they be assigned to a different Sprint from their parent Story. A sub-task always inherits the Sprint of its parent issue.

In my previous team, we used to do the following based on scenarios as workaround:

* Option 1: Create an Epic and break down the work into standard Issues (Tasks / Stories) under that Epic, instead of creating Sub-tasks under a Story. —> Tasks/Stories) can be assigned to completely different Sprints and scheduled independently on your backlog and board.

* Option 2: You can link an issue using ("Relates to" / "Blocks"). If the items are related but need to happen sequentially across sprints (e.g., Sprint 1: Development Task, Sprint 2: Testing Task), make them separate standard Tasks and link them using standard issue links (Blocks / Is blocked by or Relates to).

* Option 3: Track Cross-Sprint Progress via Parent Rollover. If a sub-task is not finished when the Sprint closes, the entire parent Story (along with all incomplete sub-tasks) will roll over to the next Sprint during the Sprint completion workflow.

I hope this helps & answers your question. 🙂

Thanks,

Anwesha

Anwesha Pan · Accepted Answer

Thanks @Matthew Sinclair 🙂 We have been using these hacks in our team and had been so useful

Florence PICARD · Accepted Answer

Could explain me how you use sub-task? because without sprint it is not usefull for me

Thanks

Druvis Cukurs (Lineset) · Accepted Answer

To settle the replies above: a sub-task always belongs to its parent's sprint. You can't give it a sprint of its own, and it moves when the story moves. So sub-tasks suit steps that finish in the same sprint as their story (build, test, review). If the pieces need to land in different sprints, make them stories or tasks under an epic instead of sub-tasks under a story. Or use "Split work item" on the backlog, which turns part of a story into a new story you can plan into another sprint.