Next Gen Project - Epics with stories in multiple projects

[Brandon_McDonough]

For a 'Next-Gen' board, is it possible to have an epic which has stories in it that span across a number of other projects?  If so, how do I set that up.

The reason I want to do this is that I'd like to use Jira's new roadmap feature to plan the work which will be done by different development teams using different Jira projects for their work.  After doing some research, it seemed like I could create a single project with the roadmap that would contain only epics and have the stories within those epics assigned to different projects based on the team responsible for that story.  However after setting up a couple of test projects, it seems as though Next Gen epics can only contain stories within the same project.

[giulia.perelli]

Hi @Brandon_McDonough,

as far as I know, you can add an issue as child of an epic only if the issue belongs to the same project of the epic.
No matter if the projects to monitor are classic or next-gen (NG).

Your objective can be reached with "Advanced Roadmap" (only available for Premium Plan).
It allows you to customize the hierarchy between issue types, so you can create a 'Initiative' issue type over the 'Epic' and manage the new Initiative issues in a dedicated project for monitoring purpose.
See: https://confluence.atlassian.com/advancedroadmapscloud/configuring-hierarchy-levels-998650959.html 

Hope this help.

Interested to hear your opinion or your alternative options.

Regards,
Giulia

PS:

in any case, it's not usefull to set a NG project as the 'main project' to manage the epics, because the NG board is able to display only the project's issues.
As any other NG project-related configuration, the board configuration of a NG project has the project scope: no schemes, no opportunity to share configuration outside the NG project.

The basic roadmap: same behaviour. Documentation on managing epic on roadmap: https://support.atlassian.com/jira-software-cloud/docs/manage-epics-on-the-roadmap/