You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Since Portfolio currently doesn't support Next-Gen projects and their issue types, do you plan to work on this and add this functionality? My company is trying to choose the right tool for project and portfolio management, and this will be extremely helpful to know since we do plan to use Next-Gen projects, and the new Roadmap feature.
Thank you for getting in touch with Atlassian Community!
Related to this limitation, we still don't have a date of when it will be implemented.
We've been tracking a feature request for this to make it available:
On the feature, there is a workaround that may help you:
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.
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 recognised 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 commit 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 commit 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 issuekey directly. This is not the case for the issues created without dependancy, they will appear in the project's backlog after the portfolio's plan change has been commit.
Please, click on vote and watch to receive updates about the feature.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.