When you set a custom task type as default for adding new tasks, all tasks - including sub-taks, are createrd as a custom task type.
In our workflow we have custom task type to see the status of e.g. a request, but the subtasks need to be normal tasks.
Is there a way to do this? If not , would this be useful for others?
Hello @Herve_Buisset - When you are adding the tasks to the project, are they being added manually with a rule or are you using a task template?
My problem is that when I add a subtask to a task (that is a custom task type), the subtask is also the same custum task type. IMO this is not logical. You use a custom task type e.g. to update the status of the “main task” and you should have the option to use “task” or “custum tasks” as subtasks.
You could work around this with a rule that converts all new tasks to your preferred task type instead of using the default.
Rules for new tasks (currently) don’t work for subtasks. If in the future they do you can select them to run on tasks only.
2 Likes
Yes! Thanks for the workaround.
1 Like
Great workaround, indeed!
1 Like
system
Closed
19 July 2025 09:15
7
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
For anyone interested, you can vote for this here:
I’m a big fan of custom task types but having used them extensively over the past months, for myself and customers that I work with, I have not found a single use case yet where they would be useful as subtasks. Perhaps others have..?
The current workaround is to disable them from being the default task type in the project settings, and creating a rule that will set the task type when a new task is added to the project. However, this workaround means we lose the unique UI feature of task types …