Some issues will lose the relationship with their parent epic.

[Chad Crotchett]

When moving issues from nextgen project to nextgen project I get the following:

Some issues will lose the relationship with their parent epic.

You're moving some issues away from their parent epic. To avoid losing the relationship between these issues and their parent, move the epic issue as well.

Note: The epic relationship won't be lost when moving between classic projects.

What's the best way to manage epics spanning across nextgen projects?

[Trudy Claspill · Accepted solution]

In this post, the responder recommended using the Roadmap feature.

https://community.atlassian.com/t5/Jira-questions/Next-Gen-Project-Epics-with-stories-in-multiple-projects/qaq-p/1305566

[Chad Crotchett]

Thanks for the info. That question (and the documentation) does mention that Next-Gen Projects are defined as "Projects" where as we use them as "Product Teams", so that's probably part of the issue.

I was informed by a peer that moving the Epic task and all stories in one Bulk Change would keep them together without remapping everything. This works, as long as the Epic only belongs in one next-gen project.