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
Next: Root
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.
Dear Community,
Is it recommended to span an epic over more than one release? I have epics that contain stories some of them cannot make it into one release. Should I create a new epic for those and assign the new epic to the new release?
Thanks,
Michael
Hi Michael,
instead of creating a new epic you can also assign more than one release (or fix version in Portfolio) to the epics. Does this help you?
Regards,
Phil
Thanks Phil,
Unfortunately this does not help: if I have an epic with a story that goes into release N and another story that goes into N+1 and I assign the epic to both releases then there is no way for me to rank the epic so it satisfies priorities in the two releases.
My question was a general one: is it a good practice to have epics that span two releases or the guideline is to restrict an epic to a single release?
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.