Problem

The cloud-to-cloud migration service with Jira Cloud currently does not support migrating the "Issue Color" field. This causes the field to be lost after the migration is complete.

Suggestion

Support the migration of the "Issue Color" field during a cloud-to-cloud migration

Workaround

This workaround involves the temporary use of an intermediary project with identical status fields to the source project, to prevent the loss of relationships. This process may be time-consuming, but it provides a temporary solution until the issue color field is integrated into the migration feature. Please follow the steps detailed below:

1. After the initial migration of the project to the new cloud site, move all issues to a temporary project. Ensure this project has identical settings to those in your original project, as well as any custom fields, to prevent loss of relationships.

2. Within this temporary project, all epics will retain the 'Epic Color' field. At this stage, assign each epic a unique color. Ideally, this will match the color coding used in the original source project.

3. Once each epic has been assigned a color, transition all issues back from the temporary project to the original target project. This step will ensure that the 'Epic Color' field is retained, but only if the field has been modified during the process.