-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
1
-
Minor
-
Issue Summary
This case is an issue that csv importing to a company management project.
Creating an issue linked to an existing Epic via CSV on "External system import" results in an error and fails to link the epic.
Mapping an existing epic issue key to "Parent" results in an error.
2024-02-05 10:05:08,332 INFO - ------------------------------ 2024-02-05 10:05:08,332 INFO - Importing: Issues 2024-02-05 10:05:08,332 INFO - ------------------------------ 2024-02-05 10:05:08,332 INFO - Only new items will be imported 2024-02-05 10:05:08,482 INFO - Importing issue: [externalId='1', summary='new-task1'] 2024-02-05 10:05:08,491 WARN - Unable to retrieve issue key for parent : XXX-3 2024-02-05 10:05:08,915 INFO - 1 issues successfully created 2024-02-05 10:05:08,917 INFO - ------------------------------
Linking subtasks to existing tasks is not a problem, it only occurs when linking to an existing epic.
Also, when both epic and task were newly created in the same csv, the mapping by "parent" did not cause any problems.
Steps to Reproduce
- Import the following CSV file
Issue ID,IssueType,Summary,Parent 1,task,new-task1,XXX-3
- Mapping as follows
- Submit [Begin Import]
Expected Results
An issue linked to the Epic is created.
Actual Results
The issue is created, but the link to the Epic is not created.
Workaround
Mapping as "Epic Link" as shown below will work as expected.