---
title: "Two Epic Color/Colour fields after deployment"
canonical: "https://support.appfire.com/space/SUPPORT/1006273597/Two%20Epic%20Color%2FColour%20fields%20after%20deployment"
format: markdown
---
## \uD83E\uDD14 Problem

After the snapshot is deployed, there are 2 fields for the Epic Color: one using the UK-English format **Epic Colour** and the other using the US-English format **Epic Color**.

This is due to the different languages being used in the Jira instances(source and target), 

## \uD83C\uDF31 Solution

**Workaround #1**

If you are in the testing phase of the migration, do the following:

- Remove the imported data and the field Epic Colour. Refer to the documentation below if you need to unlock the field
  - [https://confluence.atlassian.com/jirakb/unlock-a-locked-jira-software-custom-field-779158866.html](https://confluence.atlassian.com/jirakb/unlock-a-locked-jira-software-custom-field-779158866.html)
- Redo the deployment and use the option [https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198214297](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198214297)to map the custom field "Epic Color" to "Epic Colour".

> ℹ️ 1. Go to **Deployment** on the target instance and select **New project** or **Merge project** based on the desired action.
> ℹ️ 
> ℹ️ ![image-20260616-031318.png](media://2def611e-98f0-4a19-8601-a88d31261881)
> ℹ️ 
> ℹ️ 2. Go to **Deployment** on the target instance and select **New project** or **Merge project** based on the desired action.
> ℹ️ 
> ℹ️ ![image-20260616-031520.png](media://6fb215b9-a3cc-46c3-a670-07597bc615ba)
> ℹ️ 
> ℹ️ 3. In the **Fields** section, select the *Epic Color* field and map it to the correct field in the target instance by selecting **-->M**.
> ℹ️ 4. In the screenshot below, the ***Epic Colour*** field is mapped to the ***Epic Color*** field — this is the reverse of the required mapping. Follow a similar approach to map the ***Epic Color*** field from the snapshot to the appropriate target field.
> ℹ️ 
> ℹ️ ![image-20260616-031736.png](media://064b29fd-947e-4b36-95cc-3ded3db80c30)

> ⚠️ Check this in a non-production environment before performing it in the production environment.

**Workaround #2**

If the field that should remain is "Epic Color," perform a bulk update on the affected issues as described in the following article:

- [https://confluence.atlassian.com/jirakb/two-epic-color-fields-after-importing-projects-from-another-jira-instance-1142450997.html](https://confluence.atlassian.com/jirakb/two-epic-color-fields-after-importing-projects-from-another-jira-instance-1142450997.html)

## \uD83D\uDCCE Related articles



> Macro (contentbylabel)