Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Assign Team to Sub-Task on Advanced Roadmap Plan

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.

3 answers

1 accepted

2 votes
Answer accepted

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.

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?

 @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.

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

Unfortunately I never found a solution for this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira

Admins, notify your Jira instance of system-wide changes with the new admin announcement banner

Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their  Jira Cloud instance.  ...

682 views 17 19
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you