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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I came across this question a lot recently and I'm curious how you are solving this problem:
For the high level planning before stories etc. are created, it is important for a lot of organizations to assign epics (or also other issues in higher hierarchies) to multiple teams and let the teams estimate them.
So you end up with an epic that should have assigned multiple teams that all estimated their effort.
EPIC-1 - Create an app PoC: 22d (sum of the team estimates)
On hacky solution would be to create subtasks or stories as placeholders and assign them to the teams and estimate these. And with some scriptrunner dialog, the issues could be created in a more convenient way. But later you have to remove this tasks again, right?