Move parent ticket (Epic) and child tickets together to a new project

Morgan Manns_n54lyk

I am migrating one of our departments from a Team-Managed Jira Software project to a Company-Managed Service Management project. I've recreated everything to be as similar as possible in a way that makes sense and now I am working to migrate all open tickets over (about 200 open tickets and 3000 closed tickets). I have no problem migrating/moving tickets that don't have parent/child relationships, however I am struggling with Epics that have child ticket relationships. Does anyone have any tips on how I can move parent/child tickets together? Currently, I get a warning message saying:

"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."

Secondly, does anyone know any filters/queries I can use to move them together? 

JM Perrot

Hello @Morgan Manns thanks for your question, 

One filter to get Epic and their children in you team managed project can be :

project = ABC AND (parent != EMPTY OR issuetype = Epic)

With this request, you'll get all the issues (including subtasks) with a parent and your epics.

If not, have you tried using automation to link issues? I don't know if it works, but you can make an automation rule in your team management project to link issues with their Epic. Once you've done this, you can "reverse" the rule to recreate the Epic-Issues relationship based on the link you've created. Don't forget to create a specific link beforehand.