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
M
Michał Piotrkowicz
Very useful
Grzegorz Nowakowski
Very useful
Maciej Paruzel
That would be helpful solution
Jacek Strugała
I'm agree
Mateusz Jan Brzozowski
That would be useful
Ines Schiller
YES this is exactly what I need, too
Sam Baron
Ivan Villa I know the original post is old, but I'm going to respond to this because I just came across it, and my feedback hasn't been mentioned. I use relationships sparingly because the view grouping and rollup features are lacking. This is where Notion really beats ClickUp in my opinion.
Also, my main use case for this feature would be 'parent task = project', 'sub-task = task'.
Ivan Villa
Merged in a post:
Subtasks to default to the parent task type
Tom Barrett
Task type defaults at the list level are great, but they are causing sub tasks to default to the task type of the list when really they should match the parent task.
Please change the logic to default to the parent task type when a subtask is created
Ivan Villa
This has come up a few times internally. some questions that would be good to get community input on:
- Is the main need just for the top level, or are there valid cases for nested levels?
- What's the driver for using something like subtasks over alternatives like relationships? (We can come up with some ideas, but it's always good to hear from the people actually working with these.) 🙂
Zara Pamboukhtchian
Ivan Villa as a user, or space owner, I want to make it easy for my team to follow the SOPs we have set. For instance, a Feature Task Type is filled with Story Task Types as their subtasks. Stories will have tasks or actions.
Bugs will have test cases as their subtasks.
I'm aiming to enhance workability, clarity, and stats by reducing friction into using the features of the Task Type.
Brittney Hahn
Ivan Villa We are using task types to help collect information instead of a drop down list for the type of task. This would allow us then to collect certain data only on the task types needed.
H
Heidi Moore
Ivan Villa I also want the capability like the OP does so I can use a CRM-type function. I want our Contacts list to default to a person type, but I'd like to be able to have any subtasks that get added to that person be standard tasks. It's really nice to have everything be there and collapsible/expandable in one view.
Daniel Toft
Ivan Villa We use task types to define whether a task is a feature, a user story, or a task. A feature contains user stories as subtasks and user stories contain tasks as subtasks. It would be great to be able to restrict subtasks to a specific type by their parent, or at least be able to make it a default option.