Task types to optionally apply to subtasks

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.

2 Likes

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.

1 Like

Agreed! I was quite surprised by subtasks also getting a custom task type, and I feel it not applying to subtasks should maybe even be the default.

1 Like