The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
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 comment
Comments for this post are closed
Community moderators have prevented the ability to post new comments.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
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.
