How to bulk move EPICS and include all issues types including sub-tasks between projects?

[tamar]

I want to move multipals epics from one project to another. The epics should move with all the childs tasks as well. I will apricciate any help.

[Trudy Claspill]

Hello @tamar 

Welcome to the Atlassian community.

Is the source project a Team Managed project or a Company Managed project?

Same question for the destination project.

With native functionality, when you move an issue that has subtask, the subtasks also move. You don't need an extra step for that.

If you are moving the issues between Company Managed projects, the issues will retain their links to their parent Epics. If the source or destination project is Team Managed then links between Epics and their child issues will be lost. You may also encounter data loss from custom fields used in the issues.

With the above considerations you can use the native View all issues screen to create a filter to retrieve the issues you want to move and then use the native Bulk change feature and the Move issues option in it to move the issues between projects.

[tamar]

Hey @Trudy Claspill
I'm new to JIRA, so I have some follow-up questions:

1. Who can I konw if the source project is a Team Managed project or a Company Managed project?

2. Where can I find the View all issues screen?

3. Where can I find the  Bulk change feature?

Thanks in advance,
Tamar

[Trudy Claspill]

1. You can find information about the project type from the Type column on the View all projects page under the Projects menu. 

2. The View all issues screen is under the Filters menu. It is used to search for issues.

3. The Bulk change feature is an option available from the View all issues page, under the button labeled ... in the upper right corner.

[Tim Kopperud]

Hi @tamar, welcome to the Atlassain Community. 

To move one or more Epics with related tasks you can use the Bulk change feature. 

Please see the "Pro tips" at the end before moving. 

Start by finding the Epics to move by using JQL, like the example in the image below.

Click on the ellipsis menu in the upper right corner and select Bulk change

Select all issues and click Next

Select Move issues. This should activate a warning about losing the relationchip between the epics and the child issues. 

Click on the Move child issues in the warning. A pop-up dialog will be shown. In that dialog press the Move child issues button.

Jira will now find the related issues and include them in the move process. Make sure you map everything to the same target project (ref yellow markings). 

You must adjust the mapping to your specific needs. When done press the Next button. 

If you have sub-tasks withan any issue you will now see a screen to map sub-task types, as shown below. (If you don't have sub-tasks this screen will not be displayd.) Select the mapping according to your needs and press the Next button. 

Is the target workflow statuses doesn't match with source statuses you will now see a screen like the one below. As you see here "Closed" doesn't exist in the target workflow. Map the target statuses based on your needs, and press the Next button.

You will now get a screen about fields, and what will be lost during the move. Like e.g. this example

You migth now see several "repeting" steps (screens) like the two lasts above each time you press Next. The migration wizard will iterate until all mappings are set. When done you will see a confirmation screen like in this example

Check that everything is correct and press Confirm. If you see any errors you can go back by using the left  menu in the Bulk operation wizard, or you might start all over. 

Pro tips: 

Start out by moving only one Epic. Then follow the steps in the wizard. When done, double check everything that was moved; the Epic and the related issues. After confirming that everything worked as you wanted, you might start moving the remaing Epics. 

TimK.

[tamar]

Hey @Tim Kopperud , 
Thank you for your detailed response. I followed all the steps you provided, but for some reason, all the tasks related to an epic have moved to the backlog and lost their epic association. Is there a way to resolve this?

[Tim Kopperud]

Hi @tamar, first a question to understand the impact. Did you follow my pro tips, that means only starting out by moving one single issue? If not, how many Epics did you move?

TimK.

[Carine Monteiro]

Hi @Tim Kopperud , 

I need to move issues from one project to another using bulk changes, sometimes the option move child issues is displayed and other times it's not.

I have many Epics that don't show the option to move child issues and I don't know why.

[Mike Goitein]

Hi @Carine Monteiro - I had the exact same problem.

I wasn't getting the prompt to move child issues.

In my case, the reason was because my Jira Epics were parented by Capabilities.

Once I did a bulk edit and removed the Capability parent, I was then able to get the "Move child issues" link to bring the child issues along with the Epic move to another Jira project.

Hope that helps...