P
Paul Schaefer
All,
I have been looking at the books too long to try and solve my problem. I
think there is a very simple way to solve my problem.
Problem:
I need a task (let's call it "project A Consulting") that I can assign
multiple people to that has zero work. The task needs to be used by everyone
on my team "just in case" they need to log time for that project but we are
not trying to forecast that work. It is really a consulting task if you
will. Though rarely used, some team members might spend an hour or two a
week "consulting" from one project to another.
Issue:
I set the task up as a fixed duration task and zero work. When users update
via PWA, Project recalculates the work column, not just the units column
like I thought it was supposed to do.
Result:
After the post, the consulting task I set up is adding "work" for that task
to the plan. So now Bob Jones has extra work and this shows up as an over
allocation.
Should I be using a different approach?
Thanks!!
Paul Schaefer
I have been looking at the books too long to try and solve my problem. I
think there is a very simple way to solve my problem.
Problem:
I need a task (let's call it "project A Consulting") that I can assign
multiple people to that has zero work. The task needs to be used by everyone
on my team "just in case" they need to log time for that project but we are
not trying to forecast that work. It is really a consulting task if you
will. Though rarely used, some team members might spend an hour or two a
week "consulting" from one project to another.
Issue:
I set the task up as a fixed duration task and zero work. When users update
via PWA, Project recalculates the work column, not just the units column
like I thought it was supposed to do.
Result:
After the post, the consulting task I set up is adding "work" for that task
to the plan. So now Bob Jones has extra work and this shows up as an over
allocation.
Should I be using a different approach?
Thanks!!
Paul Schaefer