Issue Summary

When a cloud-to-cloud migration happens containing issues on hierarchy levels above Epic (> Level 1), the migration will change the name of those levels on the destination instance.

Steps to Reproduce

Try this example:

On Jira Instance 1: 

1. Create a new standard issue type named "Initiative"
2. Create a new hierarchy Level 2, above Epic, and name the level "Initiative"
3. Put the "Initiative" issue type on this new level
4. Create a project that uses the new issue type (alter Issue Type Scheme)
5. Create a few issues, including Initiatives

On Jira Instance 2:

1. Create a new standard issue type named "Saga"
2. Create a new hierarchy Level 2, above Epic, and name the level "Saga"
3. Put the "Saga" issue type on this new level
4. Create a project that uses the new issue type (alter Issue Type Scheme)
5. Create a few issues, including Sagas

On Jira Instance 1 again:

1. Go to the System menu, then Migrate Cloud Site
2. Create a new C2C migration and select the project created
3. Users/groups migration settings don't matter, just proceed
4. Select destination site as Jira Instance 2
5. Wait for the migration to finish

On Jira Instance 2 again:

1. Go to the hierarchy page
2. Check what the name of Level 2 is; it should be "Saga" but after the migration, it's "Initiative"

Expected Results

C2C migrations, bringing new issue types and/or hierarchy levels should never rename a level name.

Actual Results

C2C migrations are renaming hierarchy level names, causing them to use the same names from the origin instance of the migration

Workaround

Edit the name of the level after migration