Converting a task in one list to a subtask of a task in another list should NOT remove the original list from that subtask | Voters

Converting a task in one list to a subtask of a task in another list should NOT remove the original list from that subtask

Jake Spirek

Use case: I am frequently converting tasks in a sprint to a subtask, and it removes the task from the sprint and only has it live in the list of the parent task. 
This is super frustrating!
This isn't specific to sprints, but this use case is where I first noticed it, and it's very frustrating. 1. You have an existing task in your sprint that you want to make a subtask of a parent task that lives in another list. (Since now subtasks can live in multiple lists, you don't expect that it will REMOVE your task from your current sprint!) 2. Convert to subtask 3. It is now a subtask of the other task, but now it's removed from your sprint.
I submitted this as a bug, but they said it’s how it’s designed. Not a good user experience. 
Since the whole point of sub tasks in multiple lists is to allow them to live in MULTIPLE lists, why do you REMOVE it from its original list where you expect it to remain?!

September 23, 2021

Tony Feng

Having the same issue. This is really annoying. Since this request has been requested since 2022, hope it will get some love from developer

Collin Bentley

Also reported this as a bug, and was told that it's a feature. Tasks & Subtasks in multiple lists doesn't make sense if they don't stay there, even when a task is converted to a subtask in a different list... e.g., we take a task from the sprint backlog list & convert it to a subtask of an epic task in the Product backlog list — we expect the task to be in both lists, but instead, it's just in the Product backlog list & we have to manually add it back to the sprint backlog list as well :/

Duncan Green

Very annoying, please fix.

Trento von Lindenberg

I see this is an old one and may not be viable anymore, but this is a big issue for me! Currently, ClickUp seem to support a traditional Epic -> User Story format, but using multiple lists and subtasks does function as a workaround. However, it can't be automated because converting a task to a subtask removes the original list -- it would make this workflow a lot simpler if we could at least set that as a toggle!

Matt Holland-Jones

I'm having exactly the same problem!

I have tasks in one list, that need to be logged as a subtask in another list. I add the task to the 2nd list no problem, but as soon as I make it a subtask in the 2nd list it vanishes entirely from the original list. This is incredibly frustrating, as I then have to add it back to the list it originated from. ClickUp allows me to get the final result I want, but is double the workload for something that should be very simple.

Josh M

I have this same issue.  
Use case: I have one list named "Documents to Review".  Each main document is a Task.  I have another list name "Tasks Assigned", which comes from various workgroups/meetings and may include more or less stuff than the list of documents. Obviously, a Task would say something like "Review Submittal #1", which is one of the Documents.  To link them together and make it easier to navigate, I tried to share a copy of the Document's task as a subtask of the Assignment.  But as said by the OP, when I add the Document's task to the Assignment's list and then bump it in as a subtask of the Assignment Task, Clickup then moves
 the task exclusively to the second list.  
I'm sure there's a million other ways to look at the situation, but I specifically want the main Document tasks to be in their own nice list because I have a second group of people looking and referencing them that have nothing to do with the workflow.  Plus, they'll all be nicely organized and include a revision comment history when the project is done (as opposed to moving and reorganizing all of the Document (sub)tasks at some point in the future).  I'm planning to use that list as a permanent document/history repository for the project.
And I know that the Document's task can be @@ mentioned inside
 the Assignment's task, but then I can't see the Document (sub)task's custom fields (comments, additional statuses, notes field, etc.) in the Assignment list.  Both original tasks are in the same Space, so I don't see issues with conflicting statuses and custom fields, etc.
Asking honestly, is it really that hard to have a Task in one list show up as a Subtask in another?  Maybe I could see it being hard the other way around depending on how the Task object is set up, but I've always assumed that subtasks were same as tasks, just with some hierarchy added?
Thanks for considering!