Bulk upload error with Story and sub-task

[SilviaLo]

We use to use the same template to upload Story and Sub-task, starting from week of Dec-25-2017, it doesn't work with error shown.  Anyone has idea what happen?

First few columns in the upload template 

Issue Type	Issue key	Issue id	Parent id	Summary	Description
Story		1		Sample Summary	story
Sub-task			1	Sample Summary-subtask	subtask

 

[Ignacio Pulgar]

As the error states that 'parent issue cannot be null', I'd review the csv file used for the import, looking for subtasks with no value in Parent Id column.

[Ignacio Pulgar]

...or substasks pointing to a number that doesn't match a Story Issue id in the same csv file...

[SilviaLo]

This file is to create a new story and subtask under 'Software'.  Therefore, we assign 1 in parent ID and set 1 also in subtask by referring to it.  What the latest we find is we can upload even encoutnering the error.  Just can't pass the validation right now.

[SilviaLo]

Issue Type

Issue key

Issue id

Parent id

Summary

Description

Request Type

Request by department

Assignee

Reporter

Priority

End Date

Due Date

Original Estimate

Component/s

Story

1

Summary-story

Story

NEW

MIS

jimlin

jimlin

Medium

16-Feb-18

16-Feb-18

432000

Configure Price Quote

Sub-task

1

Summary-subtask

Subtask

NEW

MIS

jimlin

jimlin

Medium

31-Dec-17

31-Dec-17

5184000

Configure Price Quote

[Ignacio Pulgar]

It's difficult to read that csv... What character are you setting as the column separator? I would suggest using a semicolon ; as the separator.

If the separator has not been properly set, maybe some values could be assigned to a wrong column, therefore causing errors because of apparent omissions.

Another possible cause might be related to the Component/s column, as the JIRA field supports multiple values. In case you would like to set more than one component at once, each of those components should be included into different columns, usually with the same name.

Finally, your screenshot shows a link with the text 'download a detailed log'; may you click on it and post that log here?

[Steven Painchaud]

I'm running through the same error; My Issue ID and Parent ID columns are configured correctly (each subtasks' Parent ID being assigned to their Story Issue ID), and JIRA keepy saying "Fatal error during import: Parent Issue cannot be null".

Here is the extract of the Log of the detailed log discussed earlier:

2018-01-04 16:38:14,832 INFO - Importer started!
2018-01-04 16:38:14,846 INFO - Engine is running in Validation-only mode
2018-01-04 16:38:15,046 INFO - All issues will be imported to project: TestTemplate (TTEM)
2018-01-04 16:38:15,063 INFO - Creating issue: [externalId='1', summary='test']
2018-01-04 16:38:15,206 INFO - No problems found with issue 'test'
2018-01-04 16:38:15,212 INFO - Creating issue: [externalId='2', summary='test 2']
2018-01-04 16:38:15,218 INFO - No problems found with issue 'test 2'
2018-01-04 16:38:15,287 INFO - Creating issue: [externalId='3', summary='test 3']
2018-01-04 16:38:15,296 INFO - No problems found with issue 'test 3'
2018-01-04 16:38:15,301 INFO - Creating issue: [externalId='4', summary='test 4']
2018-01-04 16:38:15,308 INFO - No problems found with issue 'test 4'
2018-01-04 16:38:15,314 INFO - Creating issue: [externalId='autoid-7878989984070602626', summary='ST test 1']
2018-01-04 16:38:15,326 ERROR - Fatal error during import: Parent Issue cannot be null

[Ignacio Pulgar]

Hi Silvia,

It seems there's a bug in the non-admin "Import issues from CSV" when there are too many subtasks associated to the same parent:

https://jira.atlassian.com/browse/JRACLOUD-65048

The workaround is using the CSV import from the "External System Import" i n the Admin area, accessible from this URL:

https://<YOURS>.atlassian.net/secure/admin/ExternalImport1.jspa

Hope it helps.

[SilviaLo]

Hi Thanks, we will try those suggestion

[Casper Frost]

 Thanks @Ignacio Pulgar , the workaround worked.

However, I get the error regardless of how many tasks I am trying to import, if I only import epics, it works, but as soons as I add stories and subtasks, it fails.

Lukily I have access to the admin area, but it's far from a nice solution.

Hoping Atlassian will fix this soon.

[Gui]

Thanks @Ignacio Pulgar. Was freaking out over here.

Finally got a solution.

Is that a kind of bug when importing from the Bulk uploader ?

[SilviaLo]

Sort of, we found that even we got error notice, we can still bulk upload data, therefore, we accept this.