The Split Custom Field context script allows users to separate custom field contexts between two projects, duplicating the custom field values across the projects. This means they can be configured separately.
For example, two projects are using the same custom field configuration scheme, one project needs to delete/add/deactivate a field value from a multi-select list but the other project does not. Use the Split Custom Field Values script to split the shared custom field context between two projects. This creates a new context, duplicating option values, and migrating all issue field values, allowing custom field values to be edited independently.
Although it is possible to create a new field context and move the project across, this causes values for all fields associated with the original context to be lost. Using Split Custom Field Context allows field contexts to be split between projects without the need to re-enter field information.
From ScriptRunner, navigate to Built-in Scripts→Split Custom Field Context.
In Name of Custom Field Config Scheme, select the name of the config scheme which will contain the new custom field context created.
Under Project Name, select the project(s) to move to the new context. This field shows projects using the field configuration selected in step 2.
Issue types associated with the selected configuration scheme and selected project show in the Issue Types field. Select the issue type(s) to associate with the new scheme. Leave blank to select all options.
Under New Context Name, give a name to the new context.
Click Preview to see a summary of changes including the number of issues to be updated.
Click Run to create a new custom field context for each project selected.