Republish - Become the manager for these tasks flag

[Paul Linscott]

Hi,

Environment
MSP Prof 2003
PWA 2003

Hopefully someone could shed some light on the following
problem. I setup the security rights in PWA so that only
the project managers can read/write their own project
plans in MSP Prof 2003. All other PMs can only read a
project plan from another PM. This works very nicely. The
problem comes when the manager (person who receives the
task updates from the resources)is transferred from one PM
to another using the Collaborate menu Republish option
flag "Become the manager for these tasks". After the
republish, both PMs can read/write to the project plan
whereby before the republish only one PM was able to
read/write to the project plan.

Setup
PM 1 had read/write access to project XY
PM 2 had read only access to project XY

Security settings in category my projects and my org
- PM 1 and PM 2 were placed in my projects category
with "Allow users in this category to view all projects
they manage" - all other options in project section are
not activated.
- PM 1 and PM 2 were placed in my org category with open
project activated. Save project was not checked.

Steps taken
- PM 1 updates all changes made to project plan using
Update menu in PWA
- PM 2 republishes project plan with Become manager flag
set. Transfer works fine. All future task changes will be
sent to PM 2.
- Project owner was changed from PM 1 to PM 2

Results
PM 1 and PM 2 have read/write access to project XY in MSP
Prof.

Is the behavour correct? Is there a way that I could block
PM 1 from having write access to project plan XY without
having to change the security settings? Afterall the owner
of the project plan and tasks no longer belong to PM 1. It
appears that because an update task change was done by PM
1 to project plan XY prior to the republish, PM 1 will
always have write access to project plan XY.

Thanks for your help

Paul

 

[Gary L. Chefetz \(MVP\)]

Paul:

The minute you transfer ownership of one task in a project plan from one PM
to another, the project instantly becomes one of the Project Plans managed
by the transferee, thus meeting the criteira to allow PMs to save all
projects they manage. This is absolutely necessary because a Project Manager
cannot update a plan without being able to save it. Make sense?

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts

-

 

[Guest]

Gary,

I understand the logic and reasoning behind the transfer
of ownership, however, if I transfer the ownership of the
entire project to another PM, then I should no longer be
considered a manager of the project, thus I should not be
able to modify the project. I should only be able to view
the project. What is happening is just the opposite. I
transferred the complete ownership of the project to
another PM, but after the transfer, I am still able to
modify the project plan. I think if I transfer complete
ownership of the entire project plan to another PM, then I
should not have write access to the project plan any
longer.

thx...Paul