Timesheet & Task Approvals

[David F-H]

Project Server 2007 (SP1 + Aug Cum hotfixes) & SQL Server 2005

A couple of questions :

Timesheet Manager - When away (on leave, etc), what is the preferred method
of delegating timesheet approvals to someone else ? The best method I can
figure out is to select all of his/her resources (in Resource Center), click
"Bulk Edit" and assign all to a new Timesheet Manager. Is there a better way
?

Project Manager - Can any project manager (or Resource Manager) that has the
ability to open a project (whether they are the project owner or not) also
approve task updates that have been submitted by project team members ? What
will they see in PWA if they go into Task Approvals?

Thanks

 

[Dale Howard [MVP]]

David F-H --

1. If your organization does not use Fixed Approval Routing, an option set
for Timesheets by the Project Server administrator, then this means that
resources can select an alternate approval manager when they submit their
timesheets. All members of the Resource Managers group will appear on the
list of alternate approvers. This is assuming, however, that you are not
using a rigid RBS security model so that members of the Resource Managers
group can see all of the resources in the Enterprise Resource Pool. If you
are using Fixed Approval Routing, or have a very restricture RBS security
model that only allows Resource Managers to see their own resources, then
the only the solution to your problem is the one you posed.

2. To hand off the approval of task updates in any project, the substitute
project manager must open the project, set him/herself as the Status Manager
for tasks in the project, and then save and publish the project. Hope this
helps.

 

[David F-H]

Thanks Dale, that certainly sheds some light on the situation.

For 1. We do have a rigid RBS model, but could still open up timesheet
approval across the "My organization" category for Resource Managers I guess.
We'll think about it, but maybe better to dictate who should be approving
(otherwise people may forget and submit to manager that is on leave anyway).

For 2. I am aware that there is some pain around setting the Status Manager
- I would prefer to just set the Project Owner and have them responsible for
all approvals in a project - but apparently Project Server does not work this
way.
As one example, I (as administrator) do the imports for all projects, which
I believe sets me as status manager on all tasks. Another status manager can
only be assigned when I re-assign the project owner to him/her - then the new
project owner would need to either update all tasks or reset the status
manager to themselves on all tasks. Can you confirm that my understanding is
correct ?

 

[Dale Howard [MVP]]

David F-H --

1. Because of how Project Server 2007 handles Timesheet Approvers, you will
probably need to rethink your RBS security model.

2. Yes, you are correct that after you import a project into Project Server
2007, you are the Owner and Status Manager for that project. You must
designate the new PM as the Owner and then the PM must designate him/herself
as the Status Manager for every task in the project. Clumsy, but that's how
it works. It was a little simpler in 2002 and 2003...or was it?

Hope this helps.

 

[David F-H]

Thanks Dale.
For 1. Our security model suits our org in that we don't want Resource
Managers to have access to resources that belong to other regions.

For 2. Thanks - confirms my thoughts/fears ...

 

[Dale Howard [MVP]]

David F-H --

You are more than welcome for the help, my friend! Remmeber: We have
nothing to fear but fear itself...and Project Server 2007 as well!