Ability to nest subtasks
complete
Michael
I am working with sub-tasks, where a list is a project, a task is the main objective, and the sub-tasks are the action items for completing that objective.
The following functionality would be helpful:
- Being able to edit multiple sub-tasks simultaneously
- Being able to nest sub-tasks, just like we can for checklists
Log In
A
Andy
BUG: I can not see nested sub tasks below the first level in a board view. Most likely cause: Short between keyboard and chair.
Phivos-Angelos Kollias
BUG: when creating sub-tasks within a task, it does not show them in the list view immediately but we have to trick the system by going to list view and importing a dummy sub-task to activate the visibility of the rest.
Phivos-Angelos Kollias
It's great we now have subtasks. It was a major reason of NOT switching to clickup. Now, I migrate slowly from OmniFocus, which is great for tasks but does not combine the project management of clickup
N
Nat Gross
- Can a STATUS CHANGE automatically apply to all subtasks?
- When all subtasks have reached a new common status, can it automatically optionally apply that status to the parent task? Especially useful for simple tasks with only TODO & COMPLETE statuses.
Emily King
This is fantastic! I'm using this new feature and love it already. There is just one minor thing I'm running into -- time estimate rollups of nested subtasks don't display correctly on the 'main' subtask if you're in list view and using the option to show subtasks as separate tasks.
If I open the actual subtask item, I can see the time estimate rollup for all of its nested subtasks working perfectly, but the same subtask in list view doesn't display the rolled-up time estimate (only the placeholder hourglass).
I can tell that the system does
recognize
the time that should be rolled up -- if I click the hourglass placeholder on the 'main' subtask, it tells me the total time for the nested subtasks -- so I'm not sure why it won't display in the list view.
Csaba Szabo
Thanks, it is great. Can you solve we can see the whole tree route of subtask on top of the frame? Now we can seethe subtusk name of just the one higher level.
Thanks
S
Serge
This is our customized stylesheet for the new nested subtasks. Notice how we also added little + icons under each set. It's just more convenient for us that having to hover over the main task, and works better for longer lists of subtasks.
Once again, awesome job on this feature!!
M
Marcos Adrián Orso
Serge: Hi, how you get that customized stylesheet? Thanks
S
Serge
Marcos Adrián Orso: Tampermonkey chrome plugin with custom CSS I made. There's some feature requests to allow customizing layout, but nothing "Planned" yet: https://clickup.canny.io/feature-requests/p/own-css-styles-as-option
A
Andy
Serge: This is great! One more step towards stuffing Work Breakdown Structures into Agile because Agile is not appropriate for known structured projects.
would it be possible to share your CSS changes somehow for us visionary/lazy dudes that love your work but will never get it done ourselves?
S
Serge
Andy: Hey Andy, its quite a mess actually, about 900 lines of css. If you want to dig around, can upload it.
Kseniia Skopiuk
We are so happy about it, thank you!!!
Naima Booth
So excited about this feature, I am throwing a huge ClickUp party tonight!! 🥳🥳🥳🥳
Thank you so much guys for listening to our requests!! 😁
J
John Jones
I am in the school of thinking that this only 1/2 solves the real ability to build complex work in ClickUp because This feature:
Tasks and Subtasks with different statuses, remains unaddressed and I'm not confident given Waleed Elaghil comments of there of late if it will ever be addressed, although I'm hopeful for 2021 given the funding and big push to make ClickUp "complete" by year's end :)
With the continued lack of a classic Project entity in ClickUp ala Wrike or Asana, my hope for Tasks in this role, once subtasks became nested, remains unfulfilled due to the very lack of the ability to have Tasks & Subtasks with different statuses. You can't use a task for a Project, have some simple statuses like "to do, in progress, done" but have more complex in the Subtasks, that in case would be the actual work, such as a few more statuses like "in review" or "on hold."
And you certainly can't use a Task/Subtask set up for Epics or Sprints in Dev, because you need many, many workflow steps in the actual dev work per typical Agile methods like "in review" or "ready for deploy". It's ridiculous that the parent level Task - the Sprint or Epic - would have similar statuses. They only need simple Statues.
I remain hopeful that Goals v.2, or some evolution of Lists per this request:
Would fill the need for different statuses on Tasks or Subtasks. Or, if you guys build automations around relations, you could get some of this with related Tasks that don't have the same Workflow, but affect "Parent" tasks in relations. Such as if you complete a set of related "child" tasks, the "parent" is moved to "done."
Relational DB tools like Notion, Fibery, etc. handle the need great as you can make an infinite hierarchy with different workflow on each level, and nothing breaks. I can only guess how many users here need that ability to make ClickUp really work for them, but I know there are a lot, and I'm one of them.
Thanks for listening!
Michael
John Jones, while what you are saying is true, this is indeed a huge step forward. I'm wondering if what you are speaking of could be easily remedied with tags or with custom fields?
J
John Jones
Michael: Michael, good of you to chime in! 100% this is a great step, don't get me wrong. I can now do a good many things I was held back on, and with the simultaneously release of Relationships even more possibilities are now open!
Let me also add that I could actually see the Team expanding on the Relationship feature, perhaps more easily from an architectural point of view, to provide the benefit that Task/Subtask different statuses would provide.
I think we'd need some automation and affecting of the relations to that they emulated Task/Subtasks. For example, a Sprint would be in a list, and relate to a Task list. So you could pull say 10 of those tasks under one Sprint. Then, with some automations have the Sprint affected by what happens in the Tasks. Also see this in boards (via swimlanes, another feature on hold), and on Gantt.
Or, some of the need could be met if Goals v.2 bring things like Status for Goals, visibility on Gantt, Goals in Board View, etc. Because I think a lot of the need for Task/Subtask different statuses - and this is my need mainly - is when they are working in a sort of Project functionality. Goals have great potential to meet this need as Lists and Folders don't really do it as they don't have due dates, status, comments, activity log, can't be @@ mentioned, etc.
Thanks again and hope that makes sense!
Load More
→