On 14.2, on-prem.
Have a project hierarchy:
- Parent A
- Child 1
- Child 2
When project manager of Parent A opens Parent A in MSP,
- the interface throws an error "You don't have edit rights to Parent A"
- the projects will eventually open
- but changes made to Parent A cannot be saved back to CA PPM
- Parent A's manager has edit rights to Parent A - so the error message is in error!
- Parent A's manager does not have edit rights to the child projects - the error message should refer to these projects!
- If I give the manager of Parent A edit rights to the child projects, everything works fine
Ideally, in our situation,
- the project manager of Parent A should have edit rights only to Parent A, not the child projects, as the child projects belong to a different part of the organization (a part that is fiercely defending their data quality by limiting edit access)
- AND the MSP Interface would not thrown an error
- AND the MSP Interface would only save changes made to projects that the Parent A manager has edit access to
But, this doesn't work - so, we have to give the project manager of Parent A edit rights to the children. Manual methods of granting instance rights or removing child projects temporarily and adding them back after MSP work is done have been rejected.
How best to do this? Preferably, not via Global or OBS - the project manager should get edit rights to the children, not to every project.
Question: Anyone else with a similar problem? If you solved it, how did you do this?
I'm thinking of having an action or workflow process that would grant instance rights for the project manager to edit the child project instances. Also, an action/process to remove instance rights if/when child projects are removed from the hierarchy.