You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Because issues are mostly drawn into sprints or go on to Kanban boards, you do not tend to do multiple teams with a single task. An issue is usually tackled by a single team.
There are times it is useful, but the options you have for doing it are very different and you need to ask the question "why do we have multiple teams on this?"
Two easy examples:
You want to record the time spent on a company event - you probably have two tasks here, one for the events team to log their time arranging the event, and a second one for all teams to log their attendance. In this case, the teams all log the time on the second one, and you can run the time reports grouping by team.
You sometimes have "secondment" - a team doesn't have the right skills, so they ask another team for help with part of the story. Most of us would create a duplicate issue in the other team's board and link the two together, but if you must have it in one place, you'd create a sub-task and assign it to the seconded user.