Issue Summary

This is reproducible in Cloud to Cloud migrations. 

This problem arises when a customer has modified the default issue types for Epic or Story. Some example scenarios:

• Delete and recreate the Story or Epic issue type

• Rename the default issuetype and create a new one with the original name

• Creating additional “Story (migrated)” or “Epic (migrated)” issuetype

• Renaming of the destination Story or Epic issuetype unexpectedly

Steps to Reproduce

1. Create a Cloud  site A Jira SW project with Story Issue Type
2. Create an issue of type Story
3. Modify the Issue type Story and rename to New User Story
   • While this is allowed within the UI, there is a description:

     Created by Jira Software - do not edit or delete. Issue type for a user story.

4. On the destination Cloud site B, confirm that a Story issue type also exists
5. Create an issue with type Story
6. Migrate the project from site A to Site B

Expected Results

The issue type should be migrated to cloud, but it should not overwrite/rename the existing Story Issue Type as it is actively being used, it should be merged.

How cloud-to-cloud migration links data between sites

Actual Results

Either the Story migrates and become User Story in target or User Story migrates to User Story (migrated).

Workaround

To work around this, create a new non-managed issue type in the Server/Data Center instance, bulk edit all desired issues to be the new issue type and then migrate. That way, the existing managed issue type in cloud will be unchanged, and then the new unmanaged type will also be present.