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; } } }

Cannot Import from CSV: "Issue can't be created due to the error/s [ Issue type is a sub-task"

Derek Colanduno_wdrpps

I've seen others with this same issue when attempting to import from CSV, the error I get is:

"Issue can't be created due to the error/s [ Issue type is a sub-task but parent issue key or id not specified. ]"

I've tried to modify the CSV file to add in fields which others have mentioned, I've put things in those fields just to be sure. I'm NOT attempting to create sub-tasks at all, just import a CSV with some new issues. However, no matter what we try, it is always the same error.

In the past, until recently, this worked using the SAME EXACT CSV, but no longer. Did something change?

What more can I look at to make this function like it once did?

Accepted answers

All comments

Trudy P Claspill

Hello @Derek Colanduno

Welcome to the Atlassian community.

Yes, something has changed.

Atlassian has rolled out changes to the fields each issue level uses to note a parent issue.

Refer to these documents:

https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/

https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758

What type of issues are you trying to import? Are they standard level issues?

Does the parent issue already exist in Jira, or are you trying to create that during the import process also?

John Funk

Hi Derek - Welcome to the Atlassian Community!

Are you specifying the Issue Type in the CSV file? (i.e. is there a column for Issue Type in the CSV file?) Or just letting it use the default issue type for the project?

Derek Colanduno_wdrpps

I tried putting in a 'Issue Type' as well. Same result.

Derek Colanduno_wdrpps

These would be new issues with no parent yet. Standard issues, however, we do have a ton of our own custom fields. But, that shouldn't matter too much, it didn't in the past.

The same, exact, CSV format used to work without a problem until about 2-3 weeks ago according to the person who raised the issue.

Here is a sample of the CSV format that was working until just a couple weeks back:

Sample ID,Jira Submission ID (WGS-#),QuAISAR-H Folder Path,Summary,Issue Type

Now no matter what other information I try to add into that CSV, it always gives me this:

"Issue can't be created due to the error/s [ Issue type is a sub-task but parent issue key or id not specified. ]"

It is quite frustrating. Is there a sample CSV format that now works I can see so I can figure out what I need to change to make our imports work again?

Trudy P Claspill

As part of the CSV import process the columns of the CSV file are mapped to Jira fields. To which Jira field is each column being mapped?

Is the import being executed by a non-admin user, or by a Jira admin using the External System Import option accessed from the System settings administration page?

Derek Colanduno_wdrpps

These are being mapped to the fields as indicated in that CSV sample, those are the same field names in the Jira we have.

The CSV file is being imported by a non-admin user. However, I am an admin and the same error happens for me as well.

We are using the import from CSV option from the Issues screen directly.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud