Portfolio Hierarchy Mapping - Why are there 5 different Epics defined?
Andy Eunson
Contributor
I created 5 different projects. After building up the backlog in each (epics, stories, etc) I installed jira portfolio and started to create a plan. Note: projects are NextGen Scrum
When I get to the "Portfolio Hierarchy Configuration" i find out that each project has its own definition of Epic (see picture) so I have to scroll through the whole list and select each "epic" in the list.
Q:Why isn't there a master 'epic' issue type defined once and shared across all the projects? that way I wouldn't risk missing one.
