Issue Summary

When importing issues into Jira Software company-managed projects using the External System Import (CSV) method, the parent-child relationship is not established correctly for the first sub-task in the CSV file for issues that have more than one sub-task (for example, Stories).

Steps to Reproduce

1. Prepare a CSV file for import, containing at least one parent issue with multiple subtasks (Stories), using the recommended parent-child mapping columns.
2. Use the External System Import feature to import the CSV into a Jira Software company-managed project.
3. After the import, review the issues and their subtasks in the project.

Expected Results

All subtasks (Stories) should be correctly linked to their respective parent issues as defined in the CSV.

Actual Results

The first subtask in the CSV file is not linked to the parent issue. It throws the following error on the UI.

Cannot add value [ Work item ] to CustomField [ISSUE KEY] in Epic Link with summary 'Issue Summary'. Probably value was in incorrect format 

The following error in the splunk logs.

   message: Bulk import parent statistics: projects: [12502], total non-subtasks: 3, total subtasks: 0, total issues: 3, total non-subtasks with parent: 2, total subtasks with invalid parents: 0, total non-subtasks with invalid parents: 0, total invalid parents: 0, creation validation failures: 0, issue creation counts: {0=2, 1=1}

Workaround

Without switching to the old experience, use the new import experience for CSV import to bring data into a new company-managed space. After the import, use the bulk move to the existing space.