Supported in CSV import
Issue #7
resolved
Currently it is not possible to directly map values during CSV import to a Project Specific Custom Field.
Comments (10)
-
reporter -
reporter Hope to get full support for CSV import with approach to implement
#13: Support for multi-select. -
reporter - changed status to open
-
reporter - changed milestone to 2.0.0
-
assigned issue to
- marked as enhancement
-
reporter - removed milestone
Need to check before I can confirm that this is available in 2.x
Cheers, Holger
-
reporter 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
-
reporter - changed milestone to 2.0.1
-
reporter - changed status to resolved
-
reporter - attached update to JIM 6.1.png
- attached mapping to jppsf.png
See screenshots on updating JIRA Importers Plugin and import of CSV to Project Specific Select fields.
Cheers, Holger
-
reporter - Log in to comment
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.