Why the epic in next-generation project cannot be shown in portfolio?

Alicia Y

It seems strange that I create an epic and child issues inside, but once I tried to import my Agile next-gen projects into Portfolio, all epic issues have the same Hierarchy level, and it seems the child issues cannot be linked with my Epic issues, where is the problem? I tried to do Hierarchy setting, still cannot arrange my issues properly, what should I do? It seems the hint for hierarchy level configuration is just for classical Agile project? What about next-gen projects???

Petter Gonçalves

Hello Alicia,

Thank you for your feedback about this issue.

Indeed, the Next-Gen project template is a beta feature where our developers are still implementing new features and integration with other tools, including Portfolio.

We have already reported a feature request for this matter here:

Add support for EPICs from Next-Gen / Simplified Agility projects into Portfolio

Please, feel free to vote on it and become a watcher to increase the priority and be aware of any updates.

For now, my suggestion would be to follow the workaround described in the feature request or use a classic project to integrate Portfolio. Here's the workaround mentioned:

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 recognize them.

STILL, once the mapping is done and the NextGen EPIC is mapped to the EPIC in the Portfolio's hierarchy settings:

• The nextgen EPICs are recognized as EPIC and they can be created from within Portfolio and commit to the project, but there are other problems:
  • The dependencies are not imported from the project source into Portfolio
  • The dependencies creation and updates are not committed from Portfolio to project. This is causing discrepancies between the project and the portfolio plan and then the project needs to be updated manually to fit the committed plan.
  • The issues created with a dependency to an EPIC from Portfolio are not visible in the project backlog or board's views, they can be accessed as project's issues using the issue key directly. This is not the case for the issues created without dependency, they will appear in the project's backlog after the portfolio's plan change has been committed.

Let me know if it works for you, Alicia.