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
in building a portfolio plan many of my stories are assigned to epics, but some are not. is it a best practice to assign all stories to epics for effective scheduling in JIRA Portfolio?
We have found that if you don't make every story part of an epic people have got confused when using the Epic / Story filter in Portfolio. In the case where there are stories that are not part of Epics selecting the Epic filter gives a smaller result then when selecting Stories are as less is included. For now we are making every Story part of an Epic for this reason..... we tend to have a "Long Range" epic for this. We also do not enforce this rule on releases in the medium to long term.
I share the concerns raised about the proliferation of Epics.
Thank you for your thoughts. Your answer echoes my challenges. Not every story needs to be part of an epic (else you subvert what an epic really is) and if I wasn’t using Jira Portfolio, I wouldn’t even think about it. As I am being asked to employ Portfolio for planning purposes, I can see that the timeline getting cluttered with both epics and stories?
Hi Ian! How are you doing?
I don't believe that creating Epics for every Story is a best practice.
It will pollute your Jira and your Portfolio Plans and Programs.
Hope this helps!