Issue Summary

External System Import not mapping to label fields in Next Gen projects

Steps to Reproduce

1. Add a new field of the type label in a next-gen project (lets say a field called secondLabel)
2. Create a csv with the following fields - "Issue Key","Summary","secondLabel"
3. Use External system import to import the issues from the CSV to the Nextgen project

Expected Results

Value from the csv column secondLabel is mapped correctly to the field secondLabel

Actual Results

No errors are thrown during the csv import and values from the csv column secondLabel are mapped correctly to the field secondLabel.

Workaround

The import maps the values correctly to the Jira label field. If this is feasible map the labels to the Jira label field instead of a custom field of the type label.