R
Reefcherie
Has anyone else experienced the following problem described below (and if you
have, how did you resolve it)?
1. A resource reports Actual Work of 8 hrs on 11/10, 8hrs on 11/11 and 8 hrs
on 11/12 via their My Tasks view (Timesheets are not currently being used).
2. The project manager accepts their update without any visible problems.
The project is Saved and Published.
3. At some subsequent time, the values for Actual Work for that task change
to ".05hr" stretched out to November of 2010!
This is just the craziest example I've seen. This is happening a lot
recently - a bug I believe was introduced with the recent Infrastructure
update to Project Server 2007 and MS Project Pro 2007, or perhaps the update
just before that one. The value of Actual Work always remains accurate - the
distribution of it is what changes. It doesn't always stretch into the
future. If the task began several months ago, the Actual Work is changed for
the whole duration of the task.
Any thoughts or comments on this?
have, how did you resolve it)?
1. A resource reports Actual Work of 8 hrs on 11/10, 8hrs on 11/11 and 8 hrs
on 11/12 via their My Tasks view (Timesheets are not currently being used).
2. The project manager accepts their update without any visible problems.
The project is Saved and Published.
3. At some subsequent time, the values for Actual Work for that task change
to ".05hr" stretched out to November of 2010!
This is just the craziest example I've seen. This is happening a lot
recently - a bug I believe was introduced with the recent Infrastructure
update to Project Server 2007 and MS Project Pro 2007, or perhaps the update
just before that one. The value of Actual Work always remains accurate - the
distribution of it is what changes. It doesn't always stretch into the
future. If the task began several months ago, the Actual Work is changed for
the whole duration of the task.
Any thoughts or comments on this?