# Default Subtask Types **URL:** \ **Category:** Product Ideas\ **Tags:** in-development, subtasks, custom-task-types, agentic-work-management\ **Created:** [8 May 2026 04:39 UTC](https://forum.asana.com/t/default-subtask-types/1140208 "2026-05-08T04:39:07Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\ **Post date:** [22 July 2026 00:44 UTC](https://forum.asana.com/t/default-subtask-types/1140208/3 "2026-07-22T00:44:39Z")
Noting this thread is similar but slightly different to this, which some may also want to vote on: > [@Task types to optionally apply to subtasks](https://forum.asana.com/t/task-types-to-optionally-apply-to-subtasks/1103759): > > 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 … --- _[View the full topic](https://forum.asana.com/t/default-subtask-types/1140208)._