locked
TFS Permissions on Work Item Type level RRS feed

  • Question

  •  

    People,

     

    Is there any way to set permissions at work item type level in TFS?

     

    For example, we need that a user has permissions to create Tasks, but not Risks, Bugs and so on.

     

    Thanks in advance.

    Arsen

    Thursday, February 28, 2008 4:49 PM

Answers

  • Arsen,

    I believe the only way to implement granular permissions like that is through the work item workflow.  Essentially, you would set the initial transition 'For' option to the group who is allowed to create the work item type.  This is done through the Power Tools and the Work Item Editor.

    Hope this helps,


    Steve - www.platinumbay.com
    Thursday, February 28, 2008 6:03 PM
  • User does not have permissions per work item type.

     

    The permissions in WI in TFS are done through Areas/Iterations. You can specify permissions for specific area so it will be read-only for one set of users and completely invisible for another set of users. That way you can partition you project into separate modules.

     

    Alternatively, you can specify logic in the WI template; for example, limit users allowed to set Created state of the WI to specific group, and make Created a default state for WI. It can be different user group depending on your template.

     

    Cheers,

    Eugene

     

    Friday, February 29, 2008 8:28 PM

All replies

  • Arsen,

    I believe the only way to implement granular permissions like that is through the work item workflow.  Essentially, you would set the initial transition 'For' option to the group who is allowed to create the work item type.  This is done through the Power Tools and the Work Item Editor.

    Hope this helps,


    Steve - www.platinumbay.com
    Thursday, February 28, 2008 6:03 PM
  • User does not have permissions per work item type.

     

    The permissions in WI in TFS are done through Areas/Iterations. You can specify permissions for specific area so it will be read-only for one set of users and completely invisible for another set of users. That way you can partition you project into separate modules.

     

    Alternatively, you can specify logic in the WI template; for example, limit users allowed to set Created state of the WI to specific group, and make Created a default state for WI. It can be different user group depending on your template.

     

    Cheers,

    Eugene

     

    Friday, February 29, 2008 8:28 PM
  • Thank you guys for the idea. It works.

    Sunday, March 2, 2008 10:04 AM
  • Hello,

     

    Looks like you achieved the WI type level permissions.

    Could you provide me the exact scenario that how you implemented? Example will help too.

     

    Thanks

    Mahesh

     

    Tuesday, August 12, 2008 2:33 PM