Merge data from two custom fields into one in Jira Cloud

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

The steps in this article have the potential to irrevocably change issue data within Jira. As such, we recommend that you create a backup of your data before attempting any changes. 

Sometimes, including after server-to-cloud migrations, two redundant fields exist in Jira. You may want to merge the data in these fields to a single field to remove redundant fields.

For example, imagine there are two fields:

  • Field_A

  • Field_A (migrated)

Field_A (migrated) was in use before a Server to Cloud migration, and Field_A is being used in Cloud.

The end goal is to merge the data of Field_A (migrated) with Field_A and delete Field_A (migrated).

Solution

Merge field data with CSV import

  1. Export all Jira work items from your instance to a CSV

    1. Keep the search filters blank to see all work in the search results and then export the filtered result in a CSV

  2. In the downloaded CSV file, delete all the columns except the issue_key, summary, Field_A, and Field_A (migrated)

  3. Cut and paste the data from the Field_A (migrated) column to the Field_A column

    1. There must be no data in the Field_A (migrated) column

    2. This step will overwrite all existing data in Field_A

    3. If you need data from both fields to exist simultaneously, you may need to use spreadsheet merge functions

  4. Import the CSV file

Once done, the data in the Field_A (migrated) field should become empty for all work items, and Field_A will contain the data from Field_A (migrated).

You can then delete Field_A (migrated).

Merge field data with Jira Automation

  1. Create an automation rule

  2. Select the trigger type of Scheduled

  3. Add a conditional to check if Field_A (migrated) IS NOT EMPTY

    1. This is optional, but avoids executing the rule on work items that have no value for that field

  4. Add a conditional to check if Field_A IS EMPTY

    1. Again, this is optional, but it can help to avoid overwriting existing data in Field_A

  5. Use the Edit issue action

  6. Select Field_A as the field that needs to be set

  7. Select ...(More) > Copy from > Current issue and Field_A (migrated) from the dropdown

  8. Save the rule > enter a name > Turn on the rule

Once done, the automation rule will run at the scheduled time and will copy the data of Field_A (migrated) into Field_A for all work items in the rule's scope.

Once done, you may delete Field_A (migrated).

Updated on April 3, 2025

Still need help?

The Atlassian Community is here for you.