Supported in CSV import

[Holger Schimanski]

Currently it is not possible to directly map values during CSV import to a Project Specific Custom Field.

[Holger Schimanski]

This is because of a limitation of JIRA Importers Plugin. It only allows to map values from a CVS import to custom field of standard JIRA custom field types. https://ecosystem.atlassian.net/browse/JIM-787

A workaround is to import it into a custom field of type Text Field and then change custom field type as described in https://confluence.atlassian.com/display/JIRA/Changing+Custom+Field+Types.

There is another way to do it without "hacking" the database using bulk edit.

1. Add a new custom field of type Select List incl. possible values. (This Select List is just used temporary and will be removed in step 4.) Use this field during CSV import to store the data.
2. Go through the list of possible values and add them to the corresponding Project Specific Select Field.
3. Use JIRA searching to select the issues and then assign the corresponding Project Specific Select Field values using bulk edit.
4. Remove the Select List from step 1.

[Holger Schimanski]

Hope to get full support for CSV import with approach to implement #13: Support for multi-select.

[Holger Schimanski]

Need to check before I can confirm that this is available in 2.x

Cheers, Holger

[Holger Schimanski]

This works now since version 2.x of Project Specific Select Field. But be sure, that you update JIRA Importers Plugin (JIM) to version 6.1 or above via the add-on manager in JIRA.

Cheers, Holger

[Holger Schimanski]

See screenshots on updating JIRA Importers Plugin and import of CSV to Project Specific Select fields.

Cheers, Holger