J
JB
We have a 3 month old implementation of Project 2003 EPM. We're running SP1
for Sharepoint, Project server, and Project Pro installations.
We've found a possible bug in permission delegation between Project Web
Access and Project Pro for Sharepoint rights.
Right now, default permissions are set so that if a user is assigned a task
in the project plan, upon publishing of the schedule, permissions are
provisioned to that user in the corresponding Sharepoint site for that
project. When using the Professional client, this works fine.
There is a "Delegate Task" feature in Project Web Access that allows users
to delegate tasks that are assigned to them to a different resource.
However, even when the project plan is updated and published, if the resource
is assigned the task through the Delegate Task function, permissions are
*not* provisioned to that user in the corresponding Sharepoint site for the
project.
I suppose there is a chance we're somehow not configured right too.
Any advice is appreciated.
Thanks,
Brandon
for Sharepoint, Project server, and Project Pro installations.
We've found a possible bug in permission delegation between Project Web
Access and Project Pro for Sharepoint rights.
Right now, default permissions are set so that if a user is assigned a task
in the project plan, upon publishing of the schedule, permissions are
provisioned to that user in the corresponding Sharepoint site for that
project. When using the Professional client, this works fine.
There is a "Delegate Task" feature in Project Web Access that allows users
to delegate tasks that are assigned to them to a different resource.
However, even when the project plan is updated and published, if the resource
is assigned the task through the Delegate Task function, permissions are
*not* provisioned to that user in the corresponding Sharepoint site for the
project.
I suppose there is a chance we're somehow not configured right too.
Any advice is appreciated.
Thanks,
Brandon