Migrating project from Next Gen to Classic

anna.brooks

I've started the migration process but it seems I am going to lose all my my sub-tasks. I get a message that reads:

Please note that 409 sub-tasks were removed from the selection and do not appear in the table below. You are not allowed to bulk-move sub-task issues together with their parent issue. In this case you will only be asked to move the sub-task if you move the parent issues to a new project.

Does anyone know if/how the sub-tasks will be migrated? I don't want to proceed without being sure I won't lose them.

Gideon Nolte _Eficode_

Hi Anna, 

I totally understand your fear/confusion. After my first read of the message I had quite a lot of question marks in my head as well, but let's try to understand what it's trying to tell us and test if we got it right.

So clearly it says that all subtasks were removed for the selection. We can really skip the second sentence and jump right to the last one:  You will only be asked to move the sub-task if you move the parent issue to a new project. 

What that basically means is, that a subtask (child issue) cannot be moved without its parent, therefore it is removed from the initial move selection. Yet again a child issue cannot remain in a project without its parent and you will be asked to move it when you move the parent - which remains in the selection. 

To test if that's the case I moved a Task with a Subtask from a Next-Gen project to a Classic project.

I can assure you that the subtask itself as well as the relationship to its parent stays intact. Make sure that the new Classic project "Issue Type Scheme" includes a Subtask issue type.

 

This is a screenshot of the final confirmation before the migration:

Moving Task and Subtask from Next-Gen Kanban to Classic Kanban.

 

Hope this cleared up your doubts.

 

Gideon