-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
6.2.8, 7.0.11
-
6.02
-
2
-
Severity 3 - Minor
-
Multi-Select Field does not get populated during CSV import. This problem is specific to the "Import Issues from CSV" function that is meant for end-users (Dashboard > Issues Dropdown > "Import Issues from CSV"). If using the method via Administration menu, that works fine.
Note: this is not the same as the issue types bug that is mentioned here: JIM-1435. The problem occurs regardless of setting Issue Type in the field context.
Reproduction Steps
- Create a multi-select type field
- Import a simple csv file
- example: [^import-test.csv]
- Import it via: Dashboard > Issues Dropdown > "Import Issues from CSV"
- Walk through the steps and map a field to the multi-select field
- Observe that issues are created without the multi-select field being populated
Expected Result
User would expect that all issues are created with field values properly populated
Actual Result
Import finishes with the following:
0 projects and 1 issues imported successfully!
Import completed with 2 warnings:
Cannot add custom field value: null The value [ {null=2} ] can't be added to the Custom Field [ multi-select ]. The value [ {null=2} ] can't be found or is in the incorrect format
Issues are all created, but multi-select field values are not populated
Workaround
Issue import with multi-select fields work fine when using the admin option of the importer (Administration > System > External Imports > CSV Import).
- is duplicated by
-
JIM-1679 Loading...