Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Sub-Task Team forced to equal the parent?

Hello all,

    I am trying to build an advanced roadmap for a set of teams. I am coming up against an issue where we may have a story, and a set of sub-tasks within that story that have assignees across multiple teams. Is there a workaround for this?

1 answer

0 votes
Curt Holley
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 09, 2022

Hi @Ben Weisman 
It is true, when using the "Team" field, like Sprint, Sub-tasks have to have the same as their parent.

The workaround is, go up a level in the hierarchy. As in, use Epic for the stories and Story (or task or whatever) for what were the sub-tasks. As "standard" level issues can be separated from the parent and have a different team, be in a different Sprint.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events