Cannot import subtasks, bug with "Issue Type" during import in Next-Gen project

[Szymon Sobczak]

I'm trying to import tasks from CSV file. We're consolidating projects, so the CSV is exported from Jira.

Jira imports the issues correctly, but refuses to add parent/subtask links. This is because it creates all issues as type "Story". Then it complains that "Story" cannot be a sub-task.

I have tried mapping the values of Issue Type field during import, but the mapping is ignored and all the issues are getting imported as Story anyway.

I have also tried using the exact Issue Type names in the CSV file ("Story", "Subtask") and importing it with default mapping, but I see the same error.

I have created a clean test account to try the import, the same problem persists. This is on a next-gen project.

[Petter Gonçalves · Accepted solution]

Hello @Szymon Sobczak

Thank you for reaching out.

Unfortunately, it is not possible to import sub-task issues to Next-gen projects at this moment because of the following bug:

CSV imports do not map Issue types for Next-gen 

Feel free to vote and watch the bug to increase its priority and also receive notifications about its fix implementation.

While our devs work to get this bug fixed, you can work around it by following the steps below:

1. Import the CSV file into a Classic Software project instead, by following the instructions and column mapping in the documentation below:
   Importing data from CSV 
2. Move the issues from the Classic Software project to the Next-gen project:
   Migrate between Next-gen and Classic projects

Let us know if you have any questions.

[Szymon Sobczak]

Hi @Petter Gonçalves, thank you for looking into this!

I'm trying to use export-and-import as a workaround for another problem we have with Jira - I'm getting Error 500 when trying to move tasks to another project.

We're trying to consolidate and merge 2 next-gen + 1 classic Jira projects into one. Could you advise how to do it? I can't "Move" issues because of Error 500, I can't export-and-import because of this one...

[Petter Gonçalves]

Hello @Szymon Sobczak

Could you please provide us with a screenshot of the error returned when you try to move your issues from one project to another? Is this problem happening when you try to move issues from Classic to Classic projects or just when moving them between Classic and Next-gen projects?

Also, can you check if more details of the error are returned in the development tools of the browser?

Definitely, the only way to work around the CSV import bug would be by moving the issues from one project to another, so we must troubleshoot the error 500 you are facing.

[Petter Gonçalves]

Hello @Szymon Sobczak

I found the detailed question you created regarding the 500 error you were facing when moving issues:

https://community.atlassian.com/t5/Jira-Software-questions/Error-500-when-moving-issue-in-next-gen-project/qaq-p/1417954

I provided some instructions that might help you work around the problem. Can you confirm if that worked for you?

[Szymon Sobczak]

Thanks for your help @Petter Gonçalves !

I think those are two different issues, I replied in the "error 500" thread on that one.

Regarding the issue with importing, you're right, the bug you mentioned is the reason for my problem here.

I've upvoted it and I think that's all we can do here for now, so I spent the rest of the day manually converting imported issue types and linking subtasks...

Anyway, there is a bug report filed for this, so I think this question is closed. Too bad the workaround was manual, but that's done now.

Thanks again Peter!

[Nora Rieger]

Hello,

I have a similar issue with sub-tasks in an next-gen project, maybe you can help here, too?

In an existing issue I am offered the option "add a child Issue" and then the option "choose an existing issue". (My Jira is in German so I am not sure that I translated correctly, the German wording ist "Untergeordneten Vorgang hinzufügen" und "Bestehenden Vorgang auswählen"). But the search for existing issues does not give any results, unless I create a new sub-task directly in an existing issue. Which is not an option for me, as I have a list of appr. 40 issues, that need to be attached to other issues in a parent-child logic. I am also not able to change a task or story into a sub-task. (I was hoping this would make the issues appear in the search results). The issues I want to select are not having sub-tasks themselves, and sub-tasks are enabled in the project setup.

Thanks a lot for you support. Best, Nora