Share Epics and Issues Across Next-Gen Projects

[Olivia Friedlander]

Is it possible to easily move epics and issues across projects? i.e if an Epic with linked Issues is in a Product project and ready for dev, can my PM mass move all those issues + the epic into the Dev project backlog? 

[Kenny Dickie]

I would also like this functionality.  We use Classic projects for each of our development team, however the product team would love to use Next-Gen projects to track multi-project Epics.

[Alexey Matveev]

Hello,

You can use the bulk edit functionality to bulk move issues:

https://confluence.atlassian.com/jiracoreserver073/editing-multiple-issues-at-the-same-time-861257342.html

Go to the Move Multiple issues part.

[Olivia Friedlander]

Thank you for this information. A follow up question: is there a way to share epics and issues across projects? For example, we might have an epic that lives in both product and design and the issues can go back and forth between the two before moving to dev. It would be great if they can be shared to avoid constantly mass moving items. Do you know if that is possible in next gen projects? 

[Alexey Matveev]

It is not possible to share epics in next-gen projects. Only in classic projects.

[Meghan Cochran]

This is frustrating, as we would like to have the stories linked together and the only way is to link them like a daisy chain rather than the more simple and elegant way of having all the related work joined by the epic. Is this going to be fixed? 

[Emanuel Braga]

@Alexey MatveevSharing epics in NG projects, or a new type of issue that can be shared, is in the roadmap?

We have to plan multi-project features and it turns to be very messy to manage.

I've tried Portfolio but it does not have support for NG projects either...

Thanks!