| Excerpt |
|---|
The default ‘Email Participants’ Email Participants field the app comes with is limited to 255 characters. This can be a problem if that is a ‘TEXT’ type that should have been unlimited, but long ago Atlassian implemented this field type with a 255 character limit. If you are processing emails with large numbers of participants. A , that limit can be exceeded, in such cases, you need to create a secondary custom field selection is offered to help the migration to a larger capacity Paragraph type custom field. We cannot change the default field, much as we would like to solve this problem as customer Jira instances are already setup for this type. |
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
Navigate to your profile, and find edit the project mapping you want to change
With an email participants custom field selected, a setting named Email Participants Field (Migration Target) is visible
Select the target custom field from step 1 as Email Participants Field (Migration Target)
Create an automation rule to migrate existing data
Create a new automation rule in Jira. You can do this at either the project or global level of Jira system configuration
Set the rule name. Add the automation trigger type of Scheduled
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
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:
Code Block "Email Participants (pploffice)" IS NOT EMPTY AND "Email Participants[Paragraph]" IS EMPTY
Disable setting Only include issues that have changed since the last time this rule executed
Click Add component to add an action after the trigger and select Edit issue
Choose the migration target custom field and set the variable for your original participants field as the value. For example:
Code Block {{issue.fields.Email Participants (pploffice)}}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
Change the selection in Email Participants Field setting to the same field used in Email Participants Field (Migration Target)
Remove the custom field selection for the Email Participants Field (Migration Target) setting
...