Issue Summary

When performing a Jira C2C migration, one of the issues would not migrate due to the reporter being invalid.

There is no indication on the migration plan of errors, but the customer identifies an issue(s) that are missing.

Searching for the migration logs, we can see an error similar to this:

Chunk Migration Error: DefaultEntityMigrationError(dateTime=20XX-XX-XXTXX:XX:00.000000X, entityId=mri:mig:jira:issue:XXXXX, reason='IllegalArgumentException: User [qm:1q2w3e4r-1q2w-1q2w-aea3-qa1q2w3e4r5t:1q2we3er4r5t6y7u] does not exist', actionToResolve='null', numDownstreamFailures=40)

If we search the Source site, we can locate the issue where a Customer from JSM is the reporter. Either because the customer was deleted or JSM is disabled and removed from the site, the issue does not have a valid user.

Steps to Reproduce

1. Create an issue in JSM with a customer account.
2. Delete the Customer account or remove JSM from the site.
3. Create a plan to migrate to Cloud.
4. Select the Cloud environment.
5. Start the migration.

Expected Results

All data is successfully migrated.
And if there are any errors, they should appear in the migration report.

Actual Results

The migration is completed without showing any errors, but the data is not migrated to the Destination.

Workaround

Approach 1: Identify the issues that were not migrated and import them to the Cloud via CSV import
Approach 2: Change the Reporter/Assignee manually on the affected Issues on the source site to existing users (valid only for Reporter/Assignee)

If the problem is with the Creator, open a new ticket with the Cloud Migrations Support team for assistance.