We would love to hear how people would use this and what they expect to happen with all the data associated (comments, lists, etc.)
Sometimes I create a task within a list. As days pass, this task begins to look more like a project that would better be served as a list itself. Sure, this may have something to do with incorrect project planning, but nevertheless it's a problem.
It would be great if a task can be turned into a list or a folder.
As my team is learning ClickUp there have been more than a few growing pains.
One of which has been the creation of Folders with Lists which should have been Lists with Tasks, however there's no easy way to convert these items.
Similar to what you're asking, I'd like a general way for a user to be able to shift an entire group of items up or down in the hierarchy. In this way I could take a Folder with Lists and Tasks and turn them into a List with Tasks and Subtasks.
If Subtasks already exist, then a popup could inquire (as it does when altering statuses) whether you would like the current Subtasks to remain Subtasks or be converted to a Checklist.
I've just completed a large and complex import from Wrike to Click-Up. The Hierarchical structure from Wrike has been lost and all items have been brought in as Lists at the same level, not nested as they were in Wrike. The ability to shift Lists down Tasks and their Tasks to Subtasks would solve the current nightmare of totally restructuring a project from scratch!
Flexibility is the need here. It should be extremely easy to move any Space, Folder, List, Task or Subtask up the hierarchy or down the hierarchy. When planning out a project, the user should not have to accurately predict upfront where every object will fall in the hierarchy. It shackles creative thinking and takes too much time to have to do that. The user should have the flexibility to freely move objects up or down the hierarchy as part of the planning process. So the need is for maximum flexibility.
YES PLEASE! When organizing a structure, sometimes you think you know the layout and realize you need to move out a bit. I have multiple lists that I'd like to convert into one list and make the current list tasks, but since this isn't an option it's going to cost me time that I really don't want to dedicate to it. It's nice to build in the flexibility of project structure as you are entering things in. Also, I'd want my existing tasks to become subtasks and everything else stay the same, similar to when you change a task to a subtask. Basically a "tab" that shift everything in.
I've converted a task to a list, but changed my mind and tried to convert back to the task. However in surprise this feature doesn't exist.
It should be interchangeable or at least need the waring "this conversion cannot be undone".
@Satoshi Onoda: Personally, I think this feature can be added after nesting subtasks will be added first (and these are on the roadmap). As it is now, a list with tasks with subtasks could not be converted that easily. Other than that, I can see a value for some people in this.
I know that I would be very interested! It isn't easy (or possible, really) to know the exact scope of a project/task before you've gotten into the nitty-gritty of it, and sometimes you need more/fewer subdivisions than you thought. It would be nice to go in and convert up/down at most levels where needed so you didn't have to do it manually (and sometimes more than once).
"Checklist items > subtasks > tasks > lists > folders > spaces"
is what I would prefer when converting up, with each piece converting to be one larger. So, a folder would convert to a space, its lists would become folders, their tasks would become lists in those folders, their subtasks would become tasks in those lists, and checklist items would become subtasks of those tasks. You wouldn't be able to convert a space up, but that's unavoidable (and unnecessary, at least for my use).
"Spaces > folders > lists > tasks > subtasks > checklist items"
is what I would prefer in the opposite case, when converting down. A space would become a folder, the former folders would become lists, the former lists would become tasks, the former tasks would become subtasks, the former subtasks would become checklist items. Existing checklist items can't really subdivide further, so they would probably need to be left as is.
I would be thrilled if that were possible! I know I personally tend to under/overestimate the scope of projects a lot, so this would be a great time saver for me.
I use some lists for tracking tasks connected to a development of certain feature or document, and these lists are grouped together in a set of folders (a folder for software development, a folder for law texts commenting etc.) - folders allow me to have a predefined set of custom statuses (inherited by all lists).
Sometimes, what seemed like a large feature with too many steps and therefore was made list, would become better as a single task with subtasks to be more manageable.
List info should be moved into task's description, attachments, owner>assignee. Statuses should be resolved by the same logic as in moving a task from a list to a list (ergo ask user to map the statuses), based on the destination list for the converted task.
Potential problem would be converting a list with tasks which already have subtasks - maybe asks user, if he/she wants these to be merged into other subtasks of the converted task, or maybe merge these into description of the subtask with check boxes or optionally convert them into a checklist?
At first blush, a single task may seem sufficient but then it explodes in scope and complexity, and needs to become its own project. Conversely, something that seemed big initially may have a slower velocity, and be "just" a single task with subtasks. Good for the user to have flexibility in toggling these.
Most common use I foresee will likely be making a task into a list. My experience has been that people are more likely to under-scope and underestimate and have to endure scope creep, than overestimate and have to scale things back.
This feature would be great especially if we can set/tag certain tasks as parent/child which would be very useful to easily define epics or OKRs.
PS: I do not like to use "Goals" for epics...
What I mean is that many times when planning many KR become Objectives and so need to breakdown tasks even further...