Epics disappear on Roadmap after migration

[vvvvvito]

We're attempting to migrate our next-gen project to the classic project since it now has roadmaps enabled. 

We performed a test migrations of a single epic, and three of it's child issues - everything went along nicely, all four issues were migrated successfully, parent links were maintained, including development tasks per issue.

However, we cannot see the epic in the classic Roadmap.

When we create new Epics, they will appear in the Roadmap  - any migrated Epics don't seem to show up on the Roadmap. We want to maintain the development tasks against the epics and issues, so we prefer not to create new epics then assign the child issues to the new epic.

Any advice?

[vvvvvito · Accepted solution]

We've managed to figure out a work-around to this issue. Not natively supported, its a bit fiddly but it seems to work.

1. Create a custom field called 'Epic Name'.
2. For all epics, update field to the name of the relative Epic, and all the associated child issues for that epic. e.g. if you have an Epic called 'ABC' and three child issues, set the new custom field 'Epic Name' to equal to 'ABC' for all four of these issues (3 child + 1 parent).

3. Migrate across your Epics,  one-by-one, with the associated child issues.
❗Make sure when migrating the Epic, to set the Epic Name of the Epic you're migrating, This has to be done epic at a time, otherwise if you migrate multiple Epics at once, you will set the Epic name to equal 'ABC' for all Epics. 

4. Once migrated, open up the Issues interface in your target project

5. Search for the epic name you just migrated, the epic plus all associated children will appear.

6. Set the Epic to another issue type, (such as feature), then set it back again. This will break the links between your child and Epic issue. However, this will also make your epic show up on the Roadmap. 🥳

7. Go into all the child issues you have in your issues interface and reset the 'Epic Link' to the Epic you just 're-triggered'. 

8. Don't forget to update the 'Epic Name' in your new Epic issue (as the field would have been lost during the re-trigger)

[WaiYee Loo]

Hi @vvvvvito ,

Thanks for the detailed workaround!

I can see my Epics from Next-Gen project showing on Classic Roadmaps after moving them according to these steps:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-next-gen-and-classic-projects/#Find-and-move-your-existing-issues-to-your-new-project

I am not sure why you needed the extra steps for your Epics, could you elaborate how the issues were migrated please?