nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to upload Sub-task via CSV upload

Conor Smalley

I have a CSV file that I am trying to upload using the CSV uploader. The first 3 lines work fine but as soon as I add a sub task it fails with the error message

'Fatal error during import: Parent Issue cannot be null'

The detailed log is

2019-02-21 09:20:50,285 INFO - Importer started!
2019-02-21 09:20:50,289 INFO - Engine is running in Validation-only mode
2019-02-21 09:20:50,422 INFO - All issues will be imported to project: MY PROJECT (MP)
2019-02-21 09:20:50,435 INFO - Creating issue: [externalId='1', summary='Demo Epic']
2019-02-21 09:20:50,550 INFO - No problems found with issue 'Demo Epic'
2019-02-21 09:20:50,556 INFO - Creating issue: [externalId='2', summary='User Story 1']
2019-02-21 09:20:50,587 INFO - No problems found with issue 'User Story 1'
2019-02-21 09:20:50,593 INFO - Creating issue: [externalId='3', summary='User Story 2']
2019-02-21 09:20:50,621 INFO - No problems found with issue 'User Story 2'
2019-02-21 09:20:50,627 INFO - Creating issue: [externalId='autoid-7095087678335943636', summary='Sub Task 1']
2019-02-21 09:20:50,634 ERROR - Fatal error during import: Parent Issue cannot be null

The CSV is below

Summary	Issue Id	Parent Id	Issue Type	Labels	Description	Custom field (Epic Name)	Custom field (Epic Link)
Demo Epic	1		Epic	Automation	This is for a Demo	The Best Demo Ever
User Story 1	2		Story	Automation	This is User Story 1		The Best Demo Ever
User Story 2	3		Story	Automation	This is User Story 2		The Best Demo Ever
Sub Task 1		2	Sub-task	Automation	This is Sub Task 1

Accepted answers

All comments

Tarun Sapra

Hello @Conor Smalley

Can you share a screenshot of the first 4 rows, as the data pastes in not clearly formatted.

Ideally, each issue should have a unique issue ID and parent ID should be present only for sub-tasks and this parent ID should be same as the issue ID of the actual parent.

Tarun Sapra

From the docs

Referencing the unique "Issue Id" number of the regular issue in the "Parent Id" column. Do not include any value in the "Issue Id" fields for sub-tasks.

Conor Smalley

I haven't included an 'Issue Id' in the fields for sub-task

Not quite sure why you're saying it's not clearly formatted. you can clearly see it's in a table

Tarun Sapra

Jon Karnofsky

I'm experiencing the same problem. Was there any resolution on this? All the posts I can find seem unanswered.