"No sub-task issue types exist for your selected project .." error when migrating classic to NG

[Ellyza Marthadicta]

Hi,

When I try to migrate from classic project to Next-Gen project, I got this error.

I followed this instruction and only selected Standard Issue Type.

Can somebody help me how to migrate it?

Thank you in advance.

[Eoin · Accepted solution]

Subtasks are now available in next-gen projects, and moving subtasks issues from classic to next-gen projects is also now possible.

Introducing subtasks for breaking down work in next-gen projects

[Petter Gonçalves]

Hello Ellyza,

As you can see in the documentation you mentioned, subtasks will be lost in this migration process, since new Gen projects do not allow the creation of sub-tasks issue types yet.

That being said, if you still want to migrate your issues to a next-gen project, I would suggest you change the issue type of your sub-tasks before performing the migration.

Then, you can use other kinds of links to keep those sub-tasks linked to their parent issue.

[Osni Passos]

Why we don’t have subtask?

[Nic Brough -Adaptavist-]

Because Next-gen projects don't support them yet.

[Luke Carrier]

Worth noting that they're on the roadmap.

This is a big blocker for us moving our projects too -- hope it ships soon!

[Osni Passos]

Waiting for this too. 

[Parag Bhatnagar]

Still the case it seems. :(

[Denise Vaugeois]

@Petter Gonçalves Do we have an update on this? An approximate time frame for those of us with Nex-Gen boards that need to move tasks with sub-tasks? 

Thank you in advance

[Emanuel Y]

I'm just glad I'm not the only one having this issue. We look foward to an update.

[Jonathan Mao]

I'm getting the same error despite converting all Open sub-tasks to tasks.

[Nic Brough -Adaptavist-]

You will need to convert all the sub-tasks, irrespective of status, or remove the ones you don't want to move.  Also, a lot of people have a sub-task type of "task" - are you sure your "task" issue type is a parent-level type?