This is greatly needed and the reason I was forced to use a different product before. Now I'm back and this is still an existing issue. Not seeing a filtered task in context is completely useless for getting an over view. If I have tasks of the same type, like "requirements gathering", that are assigned to different people on different projects and that task is nested under multiple parent tasks (I and other work in a hierarchy structure instead of 80 separate lists for project components) then I can't see the context of that task/assignee without extra drill down. I could tag each task with users in another field, but then that is extra work to acheive the results that should be produced by simply assigning the work a single time. Filtering and searching through subtasks, as a nested structure and not flattened and devoid of context, should have been one of the first and most logical functions developed if a subtask feature is provided.

I also find that a very important feature. Otherwise, you are always forced to register the representative in all higher-level tasks up to the main task.

Assuming that I want to add an assignee to the subtask of a subtask, then I currently also have to enter him in all “parent” tasks. The representative is now responsible for 3 tasks at once.

On the one hand, this is time-consuming because I simply want to assign an agent to a task.

On the other hand, this also makes the person responsible for all higher-level subtasks - which in turn can be directly incorrect (or at least confusing) and creates the wrong picture of the distribution of tasks.

Hi Rochelle,

Thanks so much for the feedback! We will discuss as a team :)