I've read a workaround to link in Portfolio and Next-Gen Epic issues, but this is simply not working well. The quote is "Go to Portfolio's hierarchy configuration and map the Epic issue types coming from next-gen projects to the Epic level so Portfolio will properly recognise them."
When I attempt to edit the hierarchy and add the Epic level from the Next-Gen project, it then becomes "above" the Standard Epic and messes up my plans.
Can someone please explain how to link in the Next-Gen Epics properly?
Currently Portfolio does not play well with next-gen project types as portfolio does not support the next-gen projects at this time due to variation in field types that separate the next-gen projects from classic projects.
While the project type does not interface well with Next-gen, you can still link the projects in a hack-around manner, but it is not recommended to do so and the following KB article goes into more detail on what functionality is missing when you do use a next-gen project on a Portfolio Plan:
And the Feature request tracking portfolio support of the next-gen project type can be followed here:
Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...
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