I accidentaly convert task to a list and can't revert it.

According to the current guide - this is not revertable action. I believe not having an option to revert the changes back is really a trap in some cases. Would appreciate if it can be reverted in future for such cases.

this would also help another problem which is to export attachment data, which for now has to be done individually task by task, but if we can convert a list to a task than we can export all attachments from the list after it is converted.

Just did a massive import from Wrike to Clickup...the way our clickup setup was recommended, we should be managing tasks - all of my projects from Wrike came over as Lists and no way to transition them (other than manual) so that everything is aligned from the start. If you've been asking about this for 2 years and tons of people say they want it, when will it get implemented?

This works for me using the Select all tasks, move to subtask button at top.

List description becomes task description. Any Tasks become subtasks. Seems to be a simple conversion.

When a project first starts it is sometimes difficult to fully understand the amount of work required. So if a project appears to be large we generally make it a list. However, sometimes the predicated amount of work is incorrect or the final product pivots. It would be nice to be able to convert this list to a task and any tasks that were on the list would become subtasks.

I would like to see a checklist that could be promoted to subtasks; subtask that could be promoted to a project (new task type); and a project that could be promoted to a list and the same demoted in reverse order. Something like this is available in Things 3 ios app.

All we'd need is for the data that's on the list to go to the task; and for anything on the tasks to domino down the now subtasks.

We want to remap our task templates the way one can do with lists. This forces us to create our task template at a list level, then move the task out of the list to the list we really want it to live in and delete the shell we were forced to create.

This feature would be another workaround. Create it as a list to remap the dates properly and then convert it down to a task level.

For Projects, we use Tasks and Subtasks. When a project gets large enough, we convert it to a List with Tasks (and Subtasks). However, when the project is completed, we would like to have access to the data, but don't want to have to leave it as a List. Converting it "back" to a Task with Subtasks, would solve a lot of this for us.