Historical project key can result in incomplete project migration in Jira Cloud to Cloud (c2c)

Issue Summary

During C2C migration, if you have changed the key of a product in the destination that matches a pkey used in the source data.

This can cause confusing migration results due to incomplete project migration. Any issues not having references to the current/historical pkey in the destination will be migrated, but any that reference issue keys for the conflicting project key would fail to migrate with no indication in post migration reports as to why.

Steps to Reproduce

1. create a new project in the destination with same pkey from project in source data
2. add sample issues referencing other issue keys in the same project, and a sample ticket that does not reference the project
3. change the pkey of the project in the destination.
4. attempt to migrate rekeyeed project from source

Expected Results

• Issue is reflected in prechecks similar to current behavior for JCMA S2C migrations

• The RequiresAttention post-migration CSV accurately reflect that this is due to the historical PKeys usage

Actual Results

• Example of NeedsAttention.csv output available after completing C2C migration -

  • ERROR,{PKey},project,{name},We couldn't import {name},Failed while importing project,Contact support at https://support.atlassian.com/contact/
    

• Example of error in summary.csv output

  • Unable to add project historical key [ABC] for project [DEF]
    

Workarounds

Recommended:

1. delete the project from the destination site that previously used the same project key as the one attempting to be migrated
2. purge it from the trash to free up the key

Alternative:

Move the issues from the source project on the source site to a new empty project using a key that does not exist in the destination.

This new project can then be migrated to the destination site. Once migrated, the issues can be moved back from Project XYZ to the original project. This would result in the migration of the project, but with a different key.

MAJOR CAVEAT

Due to the amount of issue data manipulation involved, this route can make it difficult to reference audit trails for any affected issues of the project(s). Furthermore, the project will have a new key on the destination site, which will require manual updates post-migration to any references for the original key in filters, dashboard, reports, etc that Atlassian cannot assist with.