C
Cathleen
I am finding that some resource time is being populated by the system. any
idea what causes this?
idea what causes this?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
Paul Conroy
Can you expand a little more. Is this planned work, actual work ? Have you
done any custom development/macros etc ?
Does it happen on all projects, or just a few?
done any custom development/macros etc ?
Does it happen on all projects, or just a few?
M
Marc Soester [MVP]
Hi Cathleen,
also, can you tell us what version of Project Server you are using and a
step by step explanation of what how you check the time entered would be
great.
thanks
also, can you tell us what version of Project Server you are using and a
step by step explanation of what how you check the time entered would be
great.
thanks
C
Cathleen
Version is project server 2003 - Actual work is being auto populated somehow.
No custom work that I am aware of - It only happens on a few projects.
No custom work that I am aware of - It only happens on a few projects.
J
Jackson T. Cole
IMHO, it appears one or more PMs are entering actuals in Professional, and
then republishing to overwrite actuals. Not sure of how to detect that, nor
prevent it. Are you using managed time periods?
FWIW ...
JTC
then republishing to overwrite actuals. Not sure of how to detect that, nor
prevent it. Are you using managed time periods?
FWIW ...
JTC
C
Cathleen
I am the only one that would enter time other than the user. The users only
enter time on their timesheet in PWA, not directly in project pro. The PM's
only approve/reject time in PWA and then collaborate and publish once pro is
launched. I just don't know if I am causing this prepopulation problem with
something I'm doing when I publish or republish.
One more question, since you've been so helpful. Another problem I am
having is that PM's are getting an error someonetime when they publishing the
time in pro, stating the resource is assigned outside the original dates for
task # . The duration of this fixed-duration task will change to
accomoodate the resource assignment. Any idea what is causing this?
enter time on their timesheet in PWA, not directly in project pro. The PM's
only approve/reject time in PWA and then collaborate and publish once pro is
launched. I just don't know if I am causing this prepopulation problem with
something I'm doing when I publish or republish.
One more question, since you've been so helpful. Another problem I am
having is that PM's are getting an error someonetime when they publishing the
time in pro, stating the resource is assigned outside the original dates for
task # . The duration of this fixed-duration task will change to
accomoodate the resource assignment. Any idea what is causing this?
J
Jackson T. Cole
Regarding your question about fixed duration tasks being extended, that
has happened to me many times, and the reason is actually in the error
message!. A user enters more actual time than there was work remaining on the
task. The finish date is set, normally, to the last day of work, so if work
is logged later than the current finish date, finish date HAS to change.
Being a fixed duration task, that generates the message.
Regarding the original issue, are these "pantom" actuals in colored
font, or black font? If black, that represents time that THEORETICALLY was
passed from PWA to Professional, then saved/pblished from Professional.
Colored font indicates time enter by a user in PWA, and not yert updated.
The next time you see "phantom" actuals in on a task in some week, open
the project in Professional, and use "Task Usage" view to see if those
actuals are showing up in the same week. If so, I can, with 99.9% certainty,
say the PM overseeing that project adjusted actuals in some way, and
re-published assignments with an override of actuals. I can think of no other
way, short of direct SQL manipulation! :>)
Marc is correct that a detailed description of what you are doing and
seeing would help lots!
FWIW ...
JTC
has happened to me many times, and the reason is actually in the error
message!. A user enters more actual time than there was work remaining on the
task. The finish date is set, normally, to the last day of work, so if work
is logged later than the current finish date, finish date HAS to change.
Being a fixed duration task, that generates the message.
Regarding the original issue, are these "pantom" actuals in colored
font, or black font? If black, that represents time that THEORETICALLY was
passed from PWA to Professional, then saved/pblished from Professional.
Colored font indicates time enter by a user in PWA, and not yert updated.
The next time you see "phantom" actuals in on a task in some week, open
the project in Professional, and use "Task Usage" view to see if those
actuals are showing up in the same week. If so, I can, with 99.9% certainty,
say the PM overseeing that project adjusted actuals in some way, and
re-published assignments with an override of actuals. I can think of no other
way, short of direct SQL manipulation! :>)
Marc is correct that a detailed description of what you are doing and
seeing would help lots!
FWIW ...
JTC