Related question that may or may not deserve its own bug. It would be trivial to make this change.
Imagine a hierarchy of tasks
- Task A
- Task B
- Task C
Tasks A and B already have tag @foo. If A is then dropped on @foo, should Task C be tagged with @foo?
Currently, if all tasks are untagged, and A is dropped on @foo, B and C will get the tag as well. But A already has @foo, it will not recurse into subtasks.
Related question that may or may not deserve its own bug. It would be trivial to make this change.
Imagine a hierarchy of tasks
- Task A
- Task B
- Task C
Tasks A and B already have tag @foo. If A is then dropped on @foo, should Task C be tagged with @foo?
Currently, if all tasks are untagged, and A is dropped on @foo, B and C will get the tag as well. But A already has @foo, it will not recurse into subtasks.