Predecessor tasks (on the surface) appear to be more catered towards a chained tasking system. Like, in order to finish a product; dept 1 needs to complete task A -> then dept 2 can complete task A etc. But, in my situation, I have multiple tasks in my system for the same dept. Dept 1 has task A, B, C...Z and can't start on B until A is complete. (ultimate goal is to see the total number of expected days for any given dept to complete all tasks assigned) Maybe predecessor tasks can do this, but can it do this in an automated way?
My concern is that I understand if I use a standard set of tasks then the predecessor is pre-determined.
ex. dept 1 always comes before dept 2 and dept 2 before dept 3 etc.
but I don't need completion by task A in dept 1 to trigger task A in dept 2
I need completion of task A in dept 1 to trigger task B in dept 1
and I want to sort tasks A, B, C...Z by record ID rather than a preset order
I hope this makes sense, I have been confusing myself on writing this
------------------------------
Michael Jameson
------------------------------