Is it possible to have an optional level in Portfolio for JIRA.
We are looking at if Portfolio could support our implementation of SAFe 4.5.
Currently we have either a Portfolio Epic OR Program Epics. New levels in Portfolio for JIRA.
That means that Program Epics do not have parents.
And the children of Portfolio Epics are Features (JIRA Epics).
That also means that a Feature (JIRA Epic) can have a Portfolio Epic or a Program Epic as a parent
You cannot have an optional level in the hierarchy. If you try to view your plan at the Portfolio Epic level, you will either need to see the next level down as Program Epics or Features (JIRA Epics). If you try to view a plan that has the Portfolio Epic -> Program Epic -> Features in the global hierarchy at the Portfolio Epic level, but you happen to have no children Program Epics under it, all issues in that view will show in the "All issues without parent Portfolio Epic" section. Meaning, it'll look bad.
The way to properly address this is to create a dedicated JIRA project for your Program Epics, then have those sit side by side with Features (normal working team JIRA Epics), and have the Portfolio Epic be the parent of both. The dedicated project for Program Epics essentially becomes your product requirements, while working team Epics and Stories becomes the work to fulfill those requirements.
Denver AUG Leader
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs