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

[Derek Colanduno]

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?

[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]

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

[Trudy 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? 

[Derek Colanduno]

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 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]

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. 

[Trudy Claspill]

These column names are matched to identical Jira field names in the import mapping? Can you provide a screen image of the field mapping screen?

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

[Derek Colanduno]

Below is a screenshot of what we are trying to do when we import. 

[Trudy Claspill]

Thank you for sharing that screen image. That is helpful.

Are you importing to a Team Managed project or a Company Managed project?

I see in the screen under "Issue Type" on the left it says "(e.g. Isolate)". Is "Isolate" the name of the issue type you are importing? Is that the only issue type value you are using? 

Can you show us a screen image of the Issue Types available in your project, showing the issue type category each is in? For a Company Managed project that would be an image of the Issue Type Scheme. For a Team Managed project that would be the image of the Project Settings panel on the left after drilling down to the Issue Types. Please indicate which issue types are included in your CSV.

[Derek Colanduno]

I believe it is a company managed project, however I'd have to find out. 

Yes, the 'Isolate' is one type of Issue Type, there are just two Isolate or Submission. 

[Trudy Claspill]

You can find the type of the project from the Type column of the View all projects page under the Projects menu.

[Derek Colanduno]

It is a 'Company-managed business instance. 

[Trudy Claspill]

Can you show us a screen image of the Issue Types available in your project, showing the issue type category each is in? 

[Derek Colanduno]

[Trudy Claspill]

Thank you for sharing that. That confirms that "Isolate" and "Submission" are not Sub-task issue types.

I am not seeing anything obvious to account for the issue. I will need to do some experimentation of my own in my own system to see if I can recreate the problem.

You could review the documented issues related to CSV imports in Atlassian's public backlog. Here is a search that will help you find them.

You could also open a support case directly with Atlassian to see if they can readily identify a problem that I am not seeing:

https://support.atlassian.com/contact/#/

If you learn what the solution is from one of those sources please share that information here.

[Derek Colanduno]

So, I got it to import a couple times yesterday!

Then, today, for no reason, the ability to choose 'Issue Type' as a Jira field for mapping has gone away. We didn't modify anything with user rights or the fields. 

Any ideas on why the ability to choose 'Issue Type' would have gone away?

Screenshot of it being available just yesterday before I left work, but it isn't there now. 

[Derek Colanduno]

Figured it out!

If you don't have the field you want on the default screen scheme, it will not show up as an option for the CSV mapping. 

[Trudy Claspill]

You said you got the file to import a couple of times the day before, before encountering the absence of the Issue Type field. Did you figure out the root cause of the subtask error message?

[Derek Colanduno]

It was because the field had been removed from the default scheme. 

Found out that someone else was re-configuring the screens and didn't know/realize that if you remove a field from the default, it is then unavailable as an option to map to during importing of a CSV file. 

I didn't know about that either until I dug into the system and documation more!

[Trudy Claspill]

Right, that explains why the field wasn't in the mapping screen.

But your original images showed that the field was in the mapping screen. And on Jan. 2 you replied to John's answer that even when you included the issue type you still got the error.

But then on Jan. 4 you said you got the file to import a few times.

So I'm trying to get clarity on what you did that eliminated the error message that you got where the system thought you were trying to import subtasks.

[Derek Colanduno]

Oh! 

That was solved by another team mate here, they said that it was due to the fact that the CSV didn't have the reference to the Issue Type in the file.

Once we added that in, the import took the CSV without isssue. 

Maybe Jira thought that without the Issue Type it could have been a subtask?