Default Sub-Task Type
Ben Valentin
In Clickup 3.0 we can set "Default Task Type" in a list (Which is awesome). But it doesn't let you set default "subtask" types.
e.g. - I want to make a "Person" task type for the default in my List, but I want each Sub-Task of those "People" to be an actual regular Task. (This will help me utilize CRM style functions, while letting those subtasks show up in my everything view as actionable tasks, without showing the CRM lead name, since those aren't actionable tasks...)
Log In
Caroline Ginty
Merged in a post:
Different default task type for main task and subtask
Sebastian Szczerbicki
I need to create a list where the main task will have a custom task type and subtasks on this list shouldn't be this task type.
eg. Setting up a list for workers. Default task type is Worker/Workers. When I'm creating a subtask it's set to be worker as default, which doesn't make sense and generates additional clicking
M
Mr Simon
You can set different default task types so that the main task has one type (e.g., “Feature”) and subtasks have another (e.g., “Bug” or “Checklist”) automatically.
Róża Gontarz
Very useful!
Andrew Untersee
Another use case - Parent task is a "file" or contact record and subtasks would be the actual action items or tasks for that record. If the list has a default task type, there should be an option to select a default subtask type without having to rely on automation
Clemence Wiart
My subtasks don't inherit the parent's type unless there's a filter set on that list or dashboard card. But ultimately, same issue here. I don't want the task type to be inherited at all. I don't understand how this is intended behavior.
P
Patrick Benske
Ran into the same issue. Please prioritize his!
Alex Nascimento
It's good.
Raina Ahuja
Merged in a post:
Allow default custom subtask types for custom task types
Liam
Currently, when creating a subtask in ClickUp, the subtask automatically inherits the parent task’s type. This can be limiting for teams that require a strict structure, especially when using custom task types. For example, if a parent task is of type “Project,” its subtasks may need to be of type “Milestone” or “Deliverable,” rather than simply inheriting the “Project” type.
What about:-
Adding the ability to define a default subtask type for each custom task type.
This way, whenever a subtask is created under a specific parent type, it will automatically be assigned the appropriate subtask type as configured by the user or admin.
Brian Gotts
This seems like a very simple to engineer, but wildly high impact quality of life improvement. ClickUp any updates?
Andrew Tomassetti
Just realized this today that the default task type changes every subtask as well which made me revert almost all of our lists back to "Task" instead of list specific task types. Having a default option specifically for subtasks so they dont change to the default task type is definitely needed.
We have lists for Intakes, User Stories, Epics, Bugs, etc, and the subtasks are never the same task type as the parent so we're unable to really use Default Task Types currently.
Load More
→