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?
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events