We use visualstudio.com hosted TFS service.
I need to add a QA / tester to our TFS account, but I do not want them to have any access to our code. Simply just access to the GUI to report bugs, nothing more.
Any tips? Right now I believe when I add the user to the project, they can access our code.
You can secure the "Code" separately from the Work Items by going to the "Code" tab and selecting the dropdown next to the project name and selecting Security.
Related
The Code tab in a Team Project's TFS web portal allows users to check in/out items. Is there a way other than assigning users to the Stakeholder access level to prevent them from being able to check things in via the Web Portal if they have the permissions to actually check into a Team Project? It seems like you cannot explicitly exclude the Code tab form the Default or Advanced access levels, nor can you define a custom access level.
Our issue with the check in of an item from the Web Portal is that it does not evaluate any check in polices, nor can you associate the object you are checking in with a Work Item. We to want enforce developers using only Visual Studio to check in items into source control.
TFS doesn't provide the feature to stop users from checking in at web page. The workaround it to give the access level for your users.
Here is an user voice about your issue that you could vote and add comments: https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/19026091-prevent-users-to-check-in-changes-from-tfs-web-pag
Maybe that you could consider to user Git version control in TFS. In Git repository of TFS, it provide git branch policies that may solved your issue. This is much similar to the check in policies.
Here is a document about move from TFVC to Git: https://www.visualstudio.com/learn/migrate-from-tfvc-to-git/
I need to restrict access to source code for certain users (e.g. testers from a third-party company), but still give them access to the project for logging bugs etc. How can I achieve this? I cannot see a permission in the security tab that relates to source code access.
Assuming TFVC: Right click on the folder you want to exclude from the "Code" tab in the web and go to "Security". If you're using Git, choose "Manage Repository".
The Security area in the admin console does not show security for all aspects of the application.
I was able to achieve this in GIT TFS by removing the users from the "Contributor" Group.
We have a partner on our project who needs to be able to view TFS work items via the web interface, but we do not want them to have access to view our source code. It seems like it's possible to switch the scenario (access to source control, but not TFS tasks), but I'm not sure how to configure this. Any ideas?
Definitely. The source control permissions can be maintained separately. Go to the Source control explorer, right click on the team project > Advanced > Security. Click on the Readers group and remove the "Read" permission.
Mike
I'm using Visual Studio Team Services (http://visualstudio.com/), with Visual Studio 2012.
I'd like to add a new State Value for WorkItems. After a search I discover that i can edit the process template to achieve that. I've tried the menu item "Team\Team Project Collection Settings\Process Template manager", but i'm getting the following message:
Visual Studio could not retrieve your user permissions from Team Foundation Server.
Contact your Team Foundation Server administrator to determine the cause of the error and the steps to correct the problem.
If the problem persists, contact Microsoft Product Support Services
Details: Access Denied: marlon.brum#gmail.com needs the following permission(s) on the resource $ to perform this action: Administer
I've added my user to every adminstrator group i've found in tfs configuration, for the project and the collection, but i keep getting that message.
How can i add a custom state to WorkItems in Visual Studio Team Services?
Please note that the UI of VSTS has recently been changed. I'm updating my answer to reflect the latest changes but keeping an older copy too!
Update: As of 17th Oct 2018, on Team Services:
Account Home - Click on the Azure DevOps icon in the upper left corner.
Organization Settings - Click on this link in the lower left corner
Process - Click on Process in Boards Group in the list of settings
Select your process
Select the Work Item Type you want add the new state to
Click on States Menu item on the top
Click New State button
Adding a Gif below
For those who are still on the older UI , on Team Services...
Account Home - Click on the team services icon in the upper left
corner.
Process - Mouse over the Gear icon and choose Process
Choose the process you are working in
Click on Product Backlog Item type
Click on the States tab (between Layout and Rules)
Click the New State link
Account Home can be accessed by clicking on the Azure DevOps icon (previously Team Service) in the top-left corner. This page is also the home page of you account and can be accessed by directly jumping using the URL. For example: youraccountname.visualstudio.com/
Process can be accessed from the UI as mentioned in steps above or by using the direct URL youraccountname.visualstudio.com/_settings/process
Hope it helps!
Thanks Microsoft for making it available!
http://lajak.wordpress.com/2013/01/09/tfs-2012-versions-of-team-foundation-server/
Cons: •Can’t customize process template or workitem templates
So it is not possible to add new states on Team Foundation Services.
Nevertheless, "Team\Team Project Collection Settings\Process Template manager" just allows you to up- and download Process Templates, where you can edit the WIT XMLs. A more comfortable way is to use/install TFS PowerTools and use the WIT Editor "Tools -> Process Editor -> Work Item Types -> Open WIT from Server/File".
This feature is not supported by Visual Studio Team Services. It seems this is causing a lot of people (including myself) problems. See here for the (planned) feature request.
I suspect the reason for your permission error is not that you haven't assigned the right permission, but rather that the permission is not available to be assigned.
You need Team foundation Server Admin rights to execute witadmin tasks.
What probably you mean by following is that you have added yourself to default collection admin/project admin.
I've added my user to every adminstrator group i've found in tfs configuration, for the project and the collection,
For that you have two options:
Either request your TFS admin to do this activity for you.
Request you TFS Admin to add you to the TFS Admin Group using TFS Admin Console.
We have a team that consists of a number of non-developers - for these non-developers to create and modify Work Items, would they need to have VS 2010 / Team Explorer installed on their machines? Or is it possible to create and modify Work Items through the project's SharePoint site or some other built-in means?
I've not yet installed a full test TFS 2010 instance, so I can't check it out myself.
You can also create or edit workitems using Team System Web Access portal which will be configured as part of TFS2010 Installation. You can access this portal using this URL: http://[TFSServer]:8080/tfs/web
You can also configure users to access the restricted version of this portal(Work Item Only View) which the users can connect without using CAL. In this version, the users can add or edit the workitems only created by them.
You can create and edit work items from the sharepoint site for a team project in TFS 2010. but the users will still need a Client Access Licence (CAL) to do more than very basic work item management. The url will be something like http://[tfsServer]/sites/[tfsCollection]/[tfsTeamproject]/Dashboards/ProjectDashboard_wss.aspx. If you right click on the Team Project in Team Explorer and select "show project portal" then it will open a browser in the correct location.
I think the licence basically says that users can create and modify their own work items without a CAL. If they need to view work items created by other users, or allocate work items to other users, then a CAL is required.