With the new custom fields by task type feature drawing near (and hopefully statuses by task type will be picked up shortly after), it would be great to have task type inheritance.

By this I mean: some task types could be considered sub-types of other task types, and thus inherit all (or some) of their parent’s features — while still adding their own unique properties.

Examples:

* Event (parent) → Meeting (child) inherits Event fields like "Location" and "Attendees" + adds "Meeting Type" and "Agenda".

* Employee (parent) → Intern (child) inherits Employee fields like "Employee ID" and "Job title" + adds "Supervisor" and "Program".

* Task (parent) -> Bug (child) inherits statuses like "To Do", "In Progress", "Completed" + adds "Reported" and "In Review"

With inheritance in place:

* Fields and statuses are automatically inherited from the parent type.

* They can still be filtered by the parent type (e.g., filtering all “Events” would include "Meetings" and "Birthdays"), but can of course also be filtered by their own sub-type.

* Automations set for the parent type will also apply to the children, unless specified otherwise.

This will save time, keep things organized, and prevent a lot of duplication when managing specialized task types.