Manage Story and Epic issue types during a cloud-to-cloud migration

While a Jira cloud-to-cloud migration usually adds data to your cloud instance without overwriting existing data, we rename the Epic and Story issue types in a specific scenario.

Scenario

For example, you’re migrating data from a source instance of Jira called acme.atlassian.net to another instance called http://my-acme.atlassian.net.

In acme.atlassian.net, you've renamed the issue types Story to User Story and Epic to New Epic. When you migrate data to http://my-acme.atlassian.net that has issue types called Story and Epic, the issue types will be renamed as User Story and New Epic.

Workaround

To prevent renaming of these issue types:

1. Before migrating data, navigate to Settings > Issues in your source instance.

2. Select Issue types.

3. Select Add Issue Type and create a standard issue type type with your desired name.

4. Use the bulk edit feature to change all relevant issues to use this new issue type.

If you’ve migrated data and your issue types are renamed:

1. In your destination product instance, navigate to Settings > Issues.

2. Select Issue types.

3. Locate the renamed issue type and select Edit.

4. Rename the issue type back to its original name.