Custom fields can become messy when you have different types of work (tasks) within the same lists. For example, having a bug, feature, and an epic task all in the same list would cause them all to have the same custom fields, even though I would want specific ones for each type.
Other issues arise when fields that should only belong to the top-level task spread down to all its subtasks.
Custom fields should have the option to be added to a custom task type itself.
  • Whenever I create a new task of that type, it will come along with all its custom fields.
  • Those fields will not spread to any task that is not of that type.