Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

How to link Next-Gen Epic to Portfolio?

Janene Pappas
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 25, 2019

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? 

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 30, 2019 • edited

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events