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

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

Florence PICARD

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

Accepted answers

All comments

Matthew Sinclair

Good news/Bad news.

Good News: Sprint is present on Sub Tasks

Bad News: it won't let you edit said field - because its a Sub Task.
(Although there may be a way to break that - but in default terms - not happening)

Suggestion: Use a "non-sub task" hierarchy Issue Type. (0 or higher NOT lower) - I suggest this carefully - custom issue types is a slippery slope.

Shalini Pradhan

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

@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

David Day: Appcento

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

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

Matthew Sinclair

These are good "more detailed" options than I suggested.

Using already built in issue types is always good!

Anwesha Pan

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

Florence PICARD

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

Thanks

Matthew Sinclair

The issue isn't the SubTask not being in a sprint - the issue is the Sub-Task cannot be "moved" from sprint to sprint.

It inherits the Sprint of its parent.

Which is why I suggested using a non sub-task (Rank 0 or higher) or you should look into the work around suggested by Anwesha.