Issue Picker – Migration Process

To migrate Issue Picker fields between instances the following steps can be undertaken.

General Notes on Issue Picker data format

Issue picker uses an array of issue keys for storing its data: e.g. ["PROJ-100", "PROJ-101"].

To set the values via the JIRA REST API you can set the array value directly, e.g. "customfield_10075": ["KAN-1963", "KAN-1957", "KAN-1730", "KAN-1958", "ASDF-18"].

If you want to set the values via .csv import, please use repeating columns for the values to be added:

Open

Adding multiple issue keys to an Issue Picker field named “Issue picker (cc based)“ via CSV import

During the migration other formats (e.g. used by other issue picker apps might have to be converted into this format.

If issue keys change during migration (as is mostly the case), the old issue keys have to be replaced (mapped) with the corresponding ones used in the new instance so that the links still work.

Old Instance

1. Export Issues as CSV

Use the standard CSV export in the issue search to export the desired issues to CSV. Make sure to include the Issue Picker field in the export.

Open

Export Issues from old instance as .csv

New Instance

1. Create Issue Picker custom fields in the target instance

Before importing the field contents, Issue Picker fields have to be created and configured using Issue Picker administration dialogues.

2. Create custom field for old issue keys

If you need to map old issue keys to new issue keys during the migration, we advise to create a custom field of type short text to store the old issue keys when importing the issues.

3. Create custom field for old issue picker values

Create another custom field of type Short text (plain text only) to save the old issue picker values into.

3. Import CSV file into new instance

Use the import assistant in the Issue search to import the issues in the new instance.

In the step Setup choose the previously exported .csv file.

In the step Settings choose the project to import into and set other settings as desired.

In the step Map fields make sure to map the following fields:

• Issue Key → Old Issue Key Field, created in step 2

• Old Issue Picker field → Custom Field for Old Issue Picker values, created in step 3

4. Create an automation to fill the new issue picker field

Use Jira automation to map the old keys to new keys and save them into the new issue picker custom fields, created in step 1.

Create a new automation rule.