Migrated epics and original epic with different type of issue. How to combine?

Roberto Lima

We performed a migration recently and all the epics have been successfully migrated, as Atlassian documentation states that they can be migrated normally.

It turns out that after the migration we realized that in fact another type of issue was created related to the epics (Epics - Project). In the Jira Cloud there were already the Epics type.

The custom fields related to the epic (Epic Name, Epic Link, etc.) have their context only linked to Epics (Jira Cloud) and are all blocked.

As a result, our projects no longer allow the inclusion of Epics Links in the issues and in Epic it's not possible to add the Epic Name. The context is not captured, as it only considers the original Epics type of the Jira Cloud.

How to combine the types of epic issues migrated and the original epics of Jira Cloud, to allow everyone to have the same context?

Nic Brough -Adaptavist-

Jira can only have one type of Epic.

First, you should establish what issue type Jira sees as Epic at the moment and which one is the imported not-Epic.  Go to Admin -> Issues -> Issue Types and look for both of your Epic types. 

Ideally, hover the cursor over the "Edit" link and look for the "id" in the tooltip of the url that comes up.  We're *probably* looking for the one numbered id=10000 - make sure this really is called "Epic" and your other issue type has a different name (even if it is project-Epic or even just Epics or Epic. - just needs to be an identifiable difference)

Another way to check this would be to try creating an issue of each type.  Note down which one offers you an "Epic Name" as well as a summary - this is the type we need to be called "Epic"

Now we can fix your not-Epic issues, but I'm afraid it is going to be slow.  Start with running a search like "issuetype = not-epic" to find them all.  Then, one at a time, I'm afraid, you use "move" to change the issue type to Epic - this will ask you to fill in the missing Epic name