Approval process re-shows all hidden tasks

[Stephan Steiner]

Hi

Whenever we approve timesheets in Project Server 2003, all tasks that have
been hidden by resources are reset to visible status - is this supposed to
happen?

In fact this even happens for assignments that had no hours reported... you
can have one single line to approve in a project and it resets the hidden
flag for all the tasks.. thus our resources have to hide those tasks again
every single week.

Regards
Stephan

 

[Jonathan Sofer [MVP]]

Stephan,

A quick search on this newsgroup and I found an old response to this same
issue by Dale Howard, here is the link to this post:

http://groups.google.com/group/micr...0cb2e2eea7/5c8000f46ec0bf2f?#5c8000f46ec0bf2f

Hope that helps,

Jonathan Sofer

 

[Stephan Steiner]

Jonathan

Thanks for the link. It is good that I finally have confirmation that
Republish Assignments does exactly what I though (based on experience) it
does.

We however do not use this mechanism except in the cases Dale mentioned, and
we understand the implications of Republish Assignments and rarely ever use
it (only to if the project manager changes - and we inform affected
resources when we expect their timesheet to show tasks that they have
previously hidden).

In order to rule out any outside interference, I created a new project
manually yesterday with just a few task lines and one resource (myself). I
saved then published the project (Collaborate - Publish - Project Plan) then
went into my timesheet, entered actuals on one task, and hid another task. I
then logged in as the project manager for that project, went to the update
page, and approved the reported change. Then I went back to the timesheet
using my own account, and the task I hid was back there.

I verified that we have no macros that could influence the approval process
by increasing macro security to the highest level. I then even went as far
as to remove any and all macros (in addition to still have macro security to
the highest level ensuring that our non trusted macros cannot possibly be
run) and tested again and I was still able to reproduce the issue.

So I'm afraid Dale's comments did not help in my case, except confirm that
what I see happening shouldn't happen.

We're running Project Server 2003 SP3 by the way.

Regards
Stephan