mksql

We are using Team Project integration between Project 2007 and Team Foundation Server 2005 (but no Project Server). I would like to distribute copies of the project plan, and allow others to refresh work item status, but disable publishing changes for non-PMs. Is this possible



Re: Team Foundation Server - Work Item Tracking Disable Team Publish in MSP 2007?

Jeff McKune

Do you never want non project managers to change the work items One option is to put the work items under an area path and give the project manager read/write privileges and give non project managers read only privileges. You can do this from the Team, Team Project Settings, Areas and Iterations. Select an area node that you want to secure and press ¡°Security¡±. For more information, see the Work Item Tracking Area-Level Permissions section in the Team Foundation Server Permissions documentation (http://msdn2.microsoft.com/en-us/library/ms252587(VS.80).aspx)

Non project managers will be able to open the project plan and refresh it. If they make changes to the plan, they will not be allowed to publish.

Is this the experience you are looking for

Jeff McKune





Re: Team Foundation Server - Work Item Tracking Disable Team Publish in MSP 2007?

mksql

It may be a solution, I will have to experiment.

We do not want non-PMs to change Work Items via MSProject, but do give them the ability to update status via Team Explorer. Then MSP becomes a type of dashboard via the Team Project Refresh button - we just want to make sure someone does not make an accidental mass update via Publish.





Re: Team Foundation Server - Work Item Tracking Disable Team Publish in MSP 2007?

Swamy Subramanian [MSFT]

As Jeff mentioned above the permissions are based on the Areas and Iterations and these permissions are applicable for all the clients (say Team Explorer, MS Project, Excel or other 3rd Party clients) that access workitems. So there is no out of the box support for disabling just Publish using MS Project for certain users.