-
Type:
Bug
-
Resolution: Answered
-
Priority:
High
-
Component/s: Import/Export - External System Import
-
21
-
Minor
-
208
Issue Summary
Importing issues via CSV with an existing parent issue fails when using the Parent field
Steps to Reproduce
- Prepare a CSV file to create an Epic and link it with an existing parent. Please check the below example (Parent of the Epic should be ABC-321)
Issue Type,Summary,Reporter,Parent Epic,Test epic,testuser@xxxx.com,ABC-321
- Import the CSV file: System --> External system import
- Map the columns as in the below screenshot:

Expected Results
The issue is created and linked to the existing parent.
Actual Results
The user will get the below error since the issueid is not specified:

You have to define which CSV column maps to Issue Id if you want to import parents.
After adding the issueid columns as suggested in the following documentation Import data from a CSV file, the issue will be created, but it will not be linked to the parent issue:

By changing the mapping from the Parent field to the "Parent Link" field (the deprecated field) and without adding the Issueid column, the issue will be created and linked to the parent.


Workaround
By changing the mapping from the Parent field to the "Parent Link" field (the deprecated field) and without adding the Issueid column, the issue will be created and linked to the parent.

