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 that changes the ‘Add task’ button and Add task text within each section or group, which is great and provides unique customization to a project.
For those reasons, please make task types optionally applied to subtasks. I would imagine a simple switch (similar to Rules settings to not run on subtasks) would do the trick.
This makes a lot of sense. I do use custom task types for subtasks to get around the default “Changes Requested=Complete” issue with standard approvals, but can’t think of a situation where they’d live in a parent task of the same type.
Task types are great to indicate a “type of thing”, and have a project organised around it as a list of those things. Like clients, guest accounts laptop request, etc…
Setting the default is great, but most of the time when you add a subtask to one of these it’s “this is what needs for this type of thing”, not: “this type of thing has the same type of thing as a sub”.
It’l likely end up like: “I’m adding a laptop request to my laptop request.” which doesn’t make any sense.
I’m also using this, and besides missing the UI element (which I really like) it really feels like something I shouldn’t have to create a rule to do.
If anything, I think also having subtasks be the default task type should require extra work.
There’s more feedback where this came from with regards to integrating task types well. It’s awesome functionality, but - to me - it doesn’t feel quite finished.
I’ll vote for this with the operative word here being optionally in the request title.
I can see how this would be useful for folks and I’m all onboard for making people’s lives better.
However, I do use custom task types for subtasks. Sometimes the same custom_type as the parent and sometimes as a different custom_type.
Since projects cannot be viewed in a Kanban view nor exist as sub-projects of parent projects, I often find myself using a custom task type to accomplish this. It’s similar to this (albeit without the ability to create column subgroup by status within a column subgroup by status).
To be honest I stumbled upon it by chance and thought it was a new feature added recently - never seen custom task types in subtasks before although I am a big fan of using.
In our current case I’ve set the custom task type as default - but all subtasks are created by rules following our workflow - and they are always standard-tasks.
Yesterday one of our testing team members added a new task within a later stage (section) of the project and then created a new subtask that became a custom task type - which makes no sense for our workflow.
So - I think it would be quite useful to have the option to set a different default for subtasks.
The described Workaround (rule to change task type for new tasks) will work fine for this project by now but I am also a friend of the gui to directly add a “named” new (custom) task fitting to the project
- never seen custom task types in subtasks before although I am a big fan of using.