Clicking on "Create Subtask" creates a form that inherits many fields from the parent. This sounds convenient, but anecdotally from my use and internal reports it ends up being unhelpful more often than not.
- We have a "type: task/story/epic" custom fields. The children of epics are virtually never epic themself.
- We have a "size" custom field. A subtask is rarely the same size (that's the point of breaking it up). I think the same would hold true for Points.
- On this install, long subscribers lists are rarely carried forward to sub-tasks.
- If a task is closed, I'm not sure what corner case that involves creating new subtasks would use new closed subtasks
Without data I'm unsure if the behavior is inconvenient more often, or if the annoyance burns a stronger memory than the delight.
