Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,460,661
Community Members
 
Community Events
176
Community Groups

Must an epic end within a single release?

Michael Kogan
Michael Kogan Jan 24, 2019

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

 

Answer
Watch
Like Be the first to like this
311 views

1 answer

0 votes
Phil
Phil Jan 24, 2019

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

View More Comments
Michael Kogan
Michael Kogan Jan 24, 2019

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

Like
Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced Roadmaps
TAGS

Atlassian Community Events

See all events