This has been an issue for way too long. It's a fundamental problem with Atlassian's core offerings and values to the customer to make Agile and team management easy. How do you release a standard product like NextGen Projects boasting "ease of use", then require your customers to pay for "premium" to get advanced roadmaps, only to have the 2 solutions not work together? 

Same as earlier comments, we planned out migrating our entire enterprise view of all of our work in Jira using this new advanced planning feature, and now we have the choice of nuking our team managed projects and migrating all the issues to a classic project, or abandoning the idea of the advanced roadmapping capability.

This was a waste of money for us - paying for features we can't use. And now we have to incur additional costs to find a solution that will actually work.

Massive fail, Atlassian.

Literally the only reason why I upgraded to a Premium plan was so that i could get the advanced roadmap feature. I will be canceling that account after much disappointment. The language is confusing, who thought it makes sense to name "next-gen" something that DOESN'T support new features? Sighs.

Extremely frustrated at this situation

We are looking forward to this, too. We need roadmaps on tasks and other issues.

It’s a little disappointing that your premium product (i.e. Jira Premium) doesn’t support what Atlassian suggests is the “better” project type (i.e. Next-gen).

In fact the lack of support for next-gen projects is a disincentive for me to move to Premium.

I’m very interested in the Advanced Roadmaps, especially the unlimited ladder levels and cross-team support, but we moved our major projects to Next-gen some time ago, so I’m kind of stuck between features.

We were looking at the premium package but we use Next Gen. Without advanced roadmaps the cost is not worth it. We will be looking forward to this update. 

Agree, Next-Gen <-> Advanced Roadmaps incompatibility breaks the user experience. We really want to use these new features together.

Both of these are new features, so it is frustrating that they won't work together: we'd expect modern features to be compatible with each other. Because they aren't, we are presented with a heavy workaround, which is running a series of migrations away from next gen back to classic projects.

We don't want to have to run a series of migrations away from a new feature (next-gen, which we really like) back to older functionality, in order to make another new feature (advanced roadmaps) compatible. We don't want to choose and lose out on one set of awesome features...! And we definitely don't want to spend time relinking issues in the migrated projects (a side effect of migrations).

This incompatibility is frustrating as to us as there are no obvious conflicts between the two... indeed, to us, the "roadmaps" functionality of next-gens appears to compliment the functionality provided in advanced roadmaps, not conflict. Furthermore, Roadmaps (a core feature pulling us towards next-gen projects) are now in Beta in classic projects... so there appears to be a lot of parity there, and a lot of demand for this here: isn't this low hanging fruit!?

If there are any beta programs we can join for this, please let us know - we're keen!

Totally agree! Advanced roadmaps on next get project will definitely boost our projects and plans. 

Advanced roadmap support for both classic and next gen Jira projects is a key piece of functionality that is inhibiting the rollout of advanced roadmaps across our engineering teams as it is difficult to justify the price differential without this.

I agree this is a broken process and NextGen projects should have a robus road mapping feature that allows epics and stories to be viewed in a gant chart.  Also I would suggest that we have an issue type called "Initiatives" that are a collection of epics for new features.