Migrating email participants to a larger custom field

Choose the target custom field to migrate to
You’ll want to make sure that:

• It’s a Paragraph type custom field. See Atlassian’s documentation for more information about custom fields.

• the field has been configured to be visible on the relevant issue screens in Jira

• It’s not being used for other purposes to avoid conflicts

Set the migration target custom field

1. Navigate to your profile, and find edit the project mapping you want to change

2. With an email participants custom field selected, a setting named Email Participants Field (Migration Target) is visible

3. Select the target custom field from step 1 as Email Participants Field (Migration Target)

Create an automation rule to migrate existing data

1. Create a new automation rule in Jira. You can do this at either the project or global level of Jira system configuration

2. Set the rule name. Add the automation trigger type of Scheduled

3. For Occurrence, set rule to run every 10 minutes. For large projects, you may need to increase the interval to avoid hitting Atlassian automation limits

4. Enable setting Run a JQL search and execute actions for each issue in the query. Enter a JQL query to match issues that haven’t been migrated. For example:

   "Email Participants (pploffice)" IS NOT EMPTY AND "Email Participants[Paragraph]" IS EMPTY

5. Disable setting Only include issues that have changed since the last time this rule executed

6. Click Add component to add an action after the trigger and select Edit issue

7. Choose the migration target custom field and set the variable for your original participants field as the value. For example:

   {{issue.fields.Email Participants (pploffice)}}

8. Save changes and enable the automation rule.

Wait for automation rule to finish data migration

• You’ll know when it is finished as the automation rule audit log will indicate that no issues matched the trigger JQL query

Alter custom field selection in profile

1. Change the selection in Email Participants Field setting to the same field used in Email Participants Field (Migration Target)

2. Remove the custom field selection for the Email Participants Field (Migration Target) setting