Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to upload Sub-task via CSV upload

Conor Smalley
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 21, 2019

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

SummaryIssue IdParent IdIssue TypeLabelsDescriptionCustom field (Epic Name)Custom field (Epic Link)
Demo Epic1 EpicAutomationThis is for a DemoThe Best Demo Ever 
User Story 12 StoryAutomationThis is User Story 1 The Best Demo Ever
User Story 23 StoryAutomationThis is User Story 2 The Best Demo Ever
Sub Task 1 2Sub-taskAutomationThis is Sub Task 1  

2 answers

1 vote
Jon Karnofsky
Contributor
August 26, 2020

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

0 votes
Tarun Sapra
Community Champion
February 21, 2019

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
Community Champion
February 21, 2019

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'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 21, 2019

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
Community Champion
February 21, 2019

image.png

Tarun Sapra
Community Champion
February 21, 2019

Because from the formatting it wasn't immediately clear is the sub-tasks have a "issue id" value or not.

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, state of product 2026, product teams report, developer experience, product manager survey, AI impact, product team stress, product teamwork, dev workflow insights, 1000+ PMs, product leadership research

State of Product 2026

State of Product 2026: your pulse check on product development today. We asked 1000+ real teams how they’re feeling–and they had a lot to say.

Get the report
AUG Leaders

Atlassian Community Events