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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Sub-Task Team has to be the same as parent? Workaround?`

Hi all,

     How are people capacity planning using teams if multiple teams work on a sub-task within a story? This seems like basic functionality and I'm shocked this is how it works currently.

Can anyone provide a workaround?

2 answers

1 vote
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 29, 2022

They don't have multiple teams working on sub-tasks.  A sub-task is a part of a base issue, not a separate item, it's a fragment of the parent.  It doesn't make sense to give that to another team than the team tasked with doing the main story.

0 votes
Eddie Meardon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 13, 2022

Hi @Ben Weisman 

@Nic Brough -Adaptavist- has the right idea, though it's an idea I can expand on it a little.

It's built this way on purpose. In a plan, a story should be a piece of work assigned to an individual team. Subtasks are smaller tasks within that, but still handled by one team. If work needs to be broken down into smaller pieces or it needs to span multiple sprints, it should be bumped up a hierarchy level so that multiple teams can work on it. This decision was made based on Agile planning philosophy. 

Cheers

Eddie

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events