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

Assign Team to Sub-Task on Advanced Roadmap Plan

Matt Steadman_pjaqbe

Reading through the documentation on Advanced Roadmaps, it looks like the intended use is to only be able to assign a Team to the Story. Is there any way anyone has found to be able to have a Team assigned to a Sub-Task of a Story? We have a use case where the Story Issue is a main idea and the Sub-Tasks of that Story would be intended for different Teams to accomplish a piece of work on that. Thanks for any response ahead of time.

Accepted answers

Nic Brough -Adaptavist-

I think you're really going to struggle with this one.

Sub-tasks are not independent items outside their parent story, they are very much a part of a story. A story should be worked on by one team, not several.

Sub-tasks are there for breaking up stories into smaller parts so you can assign different team members, or use them for actions in different parts of a product or different technologies or whatever.

But as they're part of the main story, some of their attributes have to be that of their parent. Because if they were not, you could not call them part of their parent. These attributes include sprints, versions, team allocated and so-on.

All comments

Nic Brough -Adaptavist-

I think you're really going to struggle with this one.

Sub-tasks are not independent items outside their parent story, they are very much a part of a story. A story should be worked on by one team, not several.

Sub-tasks are there for breaking up stories into smaller parts so you can assign different team members, or use them for actions in different parts of a product or different technologies or whatever.

Lukasz Linczewski

@Matt Steadman we have a similar case. Do you mind sharing your final solution for that?

Matt Steadman_pjaqbe

Unfortunately I never found a solution for this

Victor_cz3t1o

@Matt Steadman and @Lukasz LinczewskiI read on another thread today and some one proposed a solution you might want to try.

1) Creating two different user stories for the same task

2) Assign the two user stories to the two different teams in question

3) Link the user story that is acting as a sub-task to the main task to the main task with a block.

4) Make sure which ever team or team member is handling the main task can not close the main task without the second user story (sub-task) being completed.

I think this could work as a work around.

Ivan Bezdenezhnih

The problem is as follows: we're trying to plan front-end & back-end efforts on the project with using Auto Schedule. It works only based on the team's capacity and works great if we estimate user stories and assign them to some team. But the team is not cross-functional and front-end devs can't work on b/e stuff and vice versa. So we can plan and estimate only the specific sub-tasks which could be designated to specific teams with their own capacity, but that is impossible. Does that make sense?

Melissa B_6q37iw

I'm running into the same issue...

Riccardo Ancona

I am running into the same issue...

Michelle Hummel

Same issue. I understand the approach for why the Advanced Roadmap was designed this way but it still renders it useless for team capacity planning in my organization at this time. I vote for Jira to address this limitation as a way to provide a more flexible tool for hybrid organizations not able to define "teams' and plan work at the sub-task level in this way.

Nic Brough -Adaptavist-

There is no issue in the software, it's not a limitation.

As discussed in the conversation attached to the answer, sub-tasks are part of their stories, not independent work items.

AntonGolikov

I've also requested this feature. I think that the idea behind the current product is too theoretical. For sure there is a chance to create separate stories for each team, but:

a) story is a logical part of the product - a feature useful for users. As a product owner, I want to keep this logic while creating the backlog. I don't really want to create separate stories for backend and frontend, UX and QA, etc. to deliver the feature. It will just overcomplicate the backlog and planning. I want to have one item in the backlog - the feature I want to be added to the product, rest can be created as sub-tasks (to have the needed level of details of the work to be done to deliver the story/feature)

b) I want to see the whole effort spent on the story delivery. The time spent on the sub-tasks of a story is automatically aggregated (it's exactly what is expected). But if I need to create separate stories for the same feature then I'll need to calculate this effort manually. What is the feature if it's not a story? Seems that epic is something bigger than a single feature (that should be represented as a story).

Pierre Leroux_0abrlk

I cannot agree more with this @AntonGolikov and I am wondering if the current work on Teams is going to address this issue. It looks like at Atlassian, people are working only in single-discipline teams, which is not a very Agile way to work.

raymond Scott

I have been a massive fan of Nick for years and this thread was one of the best I have read. It’s great to see very experienced Agilists differ on scrum opinions . I was lucky enough to have worked with Ken Schwaber while in Boston and he and I often disagreed as I have “hands on” experience and he was very much theoretical backed up with year of past experience! In this case I agree with most of what Nick speaks of with respect to Sub-tasks, they are small pieces of work that individuals often are responsible for , regardless of what team they may be on. There is nothing wrong with have 3rd parties from outside of a team work on a sprint , SME are the prime example .

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

advanced-roadmaps