We have implemented Scaled Agile, and some portfolios are requesting the Large Solution (SAFe) which requires an extra level in the hierarchy. We currently have
Initiative -> Epic -> Story that would become Initiative -> Capability -> Epic -> Story
but we don't want the capability level to be mandatory and allow Epics to link to Initiatives or Capabilities.
How do we do that?
Thanks in advance
Coco
Hi @Coco S Chaussée I think that a custom relation combined with Structure for Jira Add-On could be useful to present a customized portfolio views including upper hierarchies.
For example: I've defined my epics as features or releases that impact my KRs and KRs impacts my Objetives. With a correct configuration I've generated this view:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use issue links to create your own hierarchy at any level. If you are fine with a marketplace app to visualize the tree hierarchy based on the issue links, you can try out
Key features:
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.