MMDeveloper
20-09-11, 09:38 AM
I would like to modify how task dependencies work a little (unless there is already a GUI way to achieve this).
When you setup the task dependencies (I've just been using the Parent Task drop menu), I would like the "child tasks" to NOT appear in their owners queue until the parent task has been 100% completed. I'll demonstrate a real-world case:
A project is created to make a code change on a production website we host. Managers discuss amongst themselves the need for the modification. They then create the ticket and create the task hierarchy which includes our Change Management team and the workers doing the code changes.
The programmer is unaware of the discussion at this point. Now the programmer could either NOT SEE the task in their queue until it's time, OR they see the task, but just cannot open it to start work. What happens is that the tasks are created for the individual Change Management team members to put their approval stamp on it. Only when 100% of the CM team have completed their approvals, THEN the actual "work task" would appear in the programmers queue.
I don't know if I'm wording in clearly but basically setting task dependencies, child tasks are hidden from their owners until its parent task is 100% completed.
When you setup the task dependencies (I've just been using the Parent Task drop menu), I would like the "child tasks" to NOT appear in their owners queue until the parent task has been 100% completed. I'll demonstrate a real-world case:
A project is created to make a code change on a production website we host. Managers discuss amongst themselves the need for the modification. They then create the ticket and create the task hierarchy which includes our Change Management team and the workers doing the code changes.
The programmer is unaware of the discussion at this point. Now the programmer could either NOT SEE the task in their queue until it's time, OR they see the task, but just cannot open it to start work. What happens is that the tasks are created for the individual Change Management team members to put their approval stamp on it. Only when 100% of the CM team have completed their approvals, THEN the actual "work task" would appear in the programmers queue.
I don't know if I'm wording in clearly but basically setting task dependencies, child tasks are hidden from their owners until its parent task is 100% completed.