RBS and Resource/PM relationships

[bfranci]

We're about to implement Project Server at my company. I'm the manager of our PM group.

I'm excited to use the feature where resources will be able to provide task updates. However, I'd like to have a little more control over who those task updates get sent to. Am I correct in saying that the RBS determines exactly who the task updates roll up to? That sort of forced 1 to 1 relationship doesn't exactly work for me, because depending on the project, I might want a resource's task updates published to one PM or another, it won't necessarily always be the same person.

Is this simply a limitation of Project Server I can't work around?

[ssanderlin]

Originally Posted by bfranci

We're about to implement Project Server at my company. I'm the manager of our PM group.

I'm excited to use the feature where resources will be able to provide task updates. However, I'd like to have a little more control over who those task updates get sent to. Am I correct in saying that the RBS determines exactly who the task updates roll up to? That sort of forced 1 to 1 relationship doesn't exactly work for me, because depending on the project, I might want a resource's task updates published to one PM or another, it won't necessarily always be the same person.

Is this simply a limitation of Project Server I can't work around?

Welcome to the forum!

There are two distinct time submission features in Project Server 2007. One of them is Timesheets, and the other is Task Updates. Neither of them have their approver defined by the RBS.

Task Updates are sent to the Status Manager of the Task that the user has an assignment for. This is determined by a setting in the Project Plan. It is possible to have many Status Managers within one Project Plan, but you may only have one Status Manager per task.

Timesheets are a time submission facility where users may enter time for a project, an assignment, admin time, or custom timesheet lines. However, this information is not automatically transformed into a Task Update (without the implementation of custom code). There are ways to create timesheet approval chains, but in general, a Timesheet is submitted to the user's Timesheet Manager.

Does that help?

[bfranci]

It does help, thanks!

A follow up question -- how do I change the status manager for a task? I've tried updating the Status Manager column for another PM in my department (who is part of the Project team in the file), and it won't accept the name change.

Are there certain attributes of an Enterprise user that qualify/disqualify them from being a Status Manager?

[ssanderlin]

Originally Posted by bfranci

It does help, thanks!

A follow up question -- how do I change the status manager for a task? I've tried updating the Status Manager column for another PM in my department (who is part of the Project team in the file), and it won't accept the name change.

Are there certain attributes of an Enterprise user that qualify/disqualify them from being a Status Manager?

You can only change the Status Manager to either yourself or to someone who is already a status manager on the project.

If you have PM_A as the status manager, and want to make it PM_B, you need to have PM_B open the project and change the status manager to himself.