Issue Summary

In some scenarios, a Jira C2C migration may show inconsistent results on the target site (missing Issues for example) if an invalid (duplicated) custom field has Issues associated with it.

This may happen in a scenario where the Jira source cloud site has two custom fields called Epic Color (native) and Epic Colour (duplicated).

The observed behavior is that any Issues associated with the Epic Colour custom field will not be migrated over to the target site.

There may be a lack of visibility of this data disparity due to:

• CLOUD-11474 Jira C2C plans are marked as completed, but there may be missing entities

Steps to Reproduce

1. Have Jira Issues associated with the duplicate custom field (in this case, Epic Colour)
2. Run a Jira C2C migration using the Jira C2C Tool

Expected Results

If the duplicated custom field is causing Issues not to be migrated, the expected behavior is that the Tool warns the Admin user that the migration failed.

Actual Results

The Jira C2C Tool doesn't show any indications of errors and shows 100% success.
The Admin may take days to identify that there are missing entities post-migration.

Workaround

If you notice missing entities in a Jira C2C migration on the target site, please open a ticket with Atlassian Support.

For this specific scenario, the resolution is to disassociate the Issues from the duplicated custom field Epic Colour.

The Admin can also associate them with the native Epic Color custom field if necessary but it's not required for the purposes of the fix. Disassociating the Issues from the duplicated custom field will resolve it.

A bulk change in the affected Jira Issues can be done to accomplish this: 

1. go to Jira -> Filters -> Advanced issue search
2. paste this JQL (an example, make sure to tailor it to your own instance)

   project = <affected project key> AND issuetype IN (Epic, Task)

1. confirm you're seeing the number of affected Issues as a result (the number of Issues that were not migrated)
2. on the three-dot button to your right-upper band click Bulk change all <number> issues(s)
3. a new tab will one on the browser -> click the first box to select all issues
4. on the bottom of the screen click Next
5. select Edit Issues
6. click Next
7. search for Change Epic Colour on the UI (CTRL+F or CMD+F)
   1. check the box (this is the only box you'll check in the UI)
   2. remove the custom field value and leave the text box empty
8. click Next
9. click Confirm after you verify the only change that will happen to the <number> of affected Issues is the removal of the custom field value from the custom field Epic Colour