C
Christina
MS Project 2003, PS 2003
Say you have a resource assigned to a task that should be completed over the
course of 2 days and takes 4 hours of work. The resource enters 0 hours of
work for each day they are assigned the task since they were pulled to work
on a higher priority task. Once the resource submits this task update
(indicating no work has been done), the PM does not receive this as a task
update to approve. The result is that the work on the task doesn't get
re-allocated and reflects as PAst Due.
However, if the Resource enters 1 hour in Actual Work the first day, and
zeroes for the rest of the week, and submits the update, the PM can approve
the update, and the remaining 3 hours are reallocated for the following week.
In the first situation, if the resource enters a note to indicate why the
work wasn't done, it appears this "counts" as a real update and the PM
receives the update for approval.
Is there any way for the resource's entry of 0 hours across a time period to
be processed without a note being attached to each update? We are not at a
point where we can standardize how often task updates are submitted to limit
them to, say, once a week. I have requested notes be attached to explain
variances but it's not second-nature to our resources yet.
Thanks!
Christina
Say you have a resource assigned to a task that should be completed over the
course of 2 days and takes 4 hours of work. The resource enters 0 hours of
work for each day they are assigned the task since they were pulled to work
on a higher priority task. Once the resource submits this task update
(indicating no work has been done), the PM does not receive this as a task
update to approve. The result is that the work on the task doesn't get
re-allocated and reflects as PAst Due.
However, if the Resource enters 1 hour in Actual Work the first day, and
zeroes for the rest of the week, and submits the update, the PM can approve
the update, and the remaining 3 hours are reallocated for the following week.
In the first situation, if the resource enters a note to indicate why the
work wasn't done, it appears this "counts" as a real update and the PM
receives the update for approval.
Is there any way for the resource's entry of 0 hours across a time period to
be processed without a note being attached to each update? We are not at a
point where we can standardize how often task updates are submitted to limit
them to, say, once a week. I have requested notes be attached to explain
variances but it's not second-nature to our resources yet.
Thanks!
Christina