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?
Hi Janene,
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:
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.