Issue Summary

Historical keys data is not always being migrated using JCMA

Steps to Reproduce

1. Create FOO project
2. Create an issue in a project and the issue id was FOO-1
3. Created another project BAR and move the issue FOO-1 to project BAR.
4. The issue id is now BAR-1.
5. Again move the issue back to FOO, issue id is now FOO-2.
6. Migrated the project to a target cloud site.

Expected Results

Historical issue key references from server are migrated to cloud and/or JCMA provide more insight into what historical issue keys are not migrated successfully in the post-migration report

Actual Results

Historical references are not always migrated per this documentation. Customers may have automation/workflows in place that reference a previous issue ID expecting to be redirected to the new number, as it would have done in the server environment, but are instead presented with a screen stating the issue does not exist, and are now required to perform additional post-migration work to update ticket references or search for the current issue number.

Workaround

Currently there is no known workaround for this behavior.