We are using TFS 2010 and use work items and the changesets that are linked to them as the unit of change that gets deployed. I would like to put a work item into a "frozen" state, preventing any new changesets from being linked to it. Is this possible?
You can't lock individual Work Items so your best bet would be to set security on a particular area path and remove edit permissions to Work Items in that area for the required users.
When a Work Item is frozen it is put into that area and normal contributors wouldn't have access to edit it.
Team Foundation Server 2010 Permissions
You can set these permissions by right-clicking the project in Team
Explorer, clicking Areas and Iterations, and on the Area tab, clicking
Security.
Related
I'm relatively new to developing with tfs (only used git before).
I'm connecting to a server, which contains a decent amount of projects.
When I create a new work item, I can select only the server below 'classification' and not the specific project.
How can I allocate a work item directly to a project instead of the server?
Thanks!
You could directly create work item under the specific team project. The simplest and effective way is through web portal.
Project--Work--New Work Item--Work Item Type
After this the a work item directly allocated to this project instead of the server.
In work item, several features depend on the team project or team that
you have selected. For example, dashboards, backlogs, and board views
will change depending on the context selected.
When you add a work item, the system references the default area and
iteration paths defined for the team context. Work items you add
from the team dashboard (new work item widget) and queries page are
assigned the team default iteration. Work items you add from a team
backlog or board, are assigned the team default backlog iteration.
You navigate to your team context from the top navigation bar.
If you are new to tfs work item, suggest you take a look at related tutorial in MSDN: Plan and track your project with work items. Besides in TFS, there is a concept of permission, also make sure your account have enough permission for the project and adding work item.
I have created a team underneath the Team Members section (in Team Explorer), but I cannot select this team from the drop down in my Bug. This drop down (highlighted text in image below) has no teams listed in it.
What am I doing wrong?
We are using the http://www.scrumforteamsystem.co.uk/ template for TFS 2008.
The bug that you have in the image is a customized bug. Someone in the organization (maybe you) have changed to bug and added the Team field to the bug. The team that is available in the team explorer cannot be used in the work item, but you can use link that John added to show groups in the dropdown.
Another approach is to use a global list to determine the values for the team field. Adding a new team means that you have to add it to Team Explorer and to the global list.
In the new version of TFS (TFS 11), which you can preview at http://tfspreview.com, you can see that the team has become a first class citizin. If you want to see it in action, you can either go to one of the sessions of //BUILD/ or sign up for an account on TfsPreview.com.
Go to TFS explorer, go to your project and right click on the project title and Select "Show Project Portal"
Once its loaded up in your browser, click on "Team Project Administration" Tab.
The team option is the second box on this page. Add your teams to there, and they will then appear in the dropdown within TFS Solution Explorer.
You will need to save any bugs first before you can assign it to a team though.
See the blog post Assigning a work item to a group in TFS.
This does require some minor customization of the work item types you're interested in changing.
I am trying to figure out how to modify the work items permissions on a specific TFS project to inaccessible?
I want to make the work items 'invisible' to all users.
The MSDN documentation is a little unclear (at least for a newbie):
http://msdn.microsoft.com/en-us/library/ms252587.aspx
it mentions TFSSecurity could be used from command line and I think i need to deny WORK_ITEM_READ for that project - could someone provide the syntax for that?
Thanks!!!
You can do it with TFSSecurity. But unless you enjoy command line pain, just use Team Explorer (via Visual Studio).
Right click on a project in Team Explorer and select "Team Project Settings" then select "Areas and Iterations".
In the resulting dialog make sure that the root Area (called "Area") is selected then select the "Security" button in the bottom of the dialog box (next to close).
That will launch the security options for the work items under that Area. From there you can uncheck "View work items in this node" for everyone in the list.
However you will be unable to remove Collection admin's rights to view the work items. You may be able to do that via TFSSecurity.exe but it would be abnormal to do so.
We have a few developers who don't work here anymore, but didn't check all theirs changes into Team Server before they left.
Now their usernames don't exists anymore, and I can't access their pending changes to undo them....
I found a way, not needing command line.
With Power Tools installed (both in 2008 and in 2010 version), Visual Studio shows a node for Team Members in each project. If you right-click on one of the members, you can choose to view all their pending changes. Till now nothing new. BUT, I suddenly saw, in the right hand upper corner of the pending change list, a link that says "Modify Query".
I opened the window, and in it was an input field that let me change the username. I changed it to the username I wanted, and I got his list of pending changes!
Here's a link to the TFS 2008 Power Tools:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=FBD14EEA-781F-45A1-8C46-9F6BA2F68BF0
and the TFS 2010 Power Tools:
http://visualstudiogallery.msdn.microsoft.com/en-us/c255a1e4-04ba-4f68-8f4e-cd473d6b971f
Edit by woppers:
I don't have enough Rep to comment so I have to make an edit. I had the same issue as the OP but I am working in TFS 2013 so the procedure is slightly different. Here's what I did.
Go to:
Source Control Explorer
right click on the collection you are working in
Find
Find Changesets...
Enter your LanID in the “By user:” field
Click search
Click find
That will show you all of your pending changes.
Highlight one of them and click “Details...” to view the info in them.
As an administrator of TFS you should have some option of global check in.
something like that in the command line: tf lock /lock:none /workspace:workspace;username $/code/foo.cs /s:http://server:8080
or better yet:
tf undo /workspace:workspace;username $/code/foo.cs /s:http://server:8080
To expand a bit on the awesome answer provided by xr280xr... I needed to undo pending changes of a former employee, and this worked for me on a TFS 2013 server, using VS2015 on my own desktop:
Right click the folder in Source Control Explorer > Find > Find
by Status and enter * as a wild card. You can reduce the results to
a specific user if you know the user name.
When the results appear, you can right-click and select Undo. The
Output window should confirm success.
Note that if the former employees' workspace is on another PC, you'll continue to see the pending changes they have, but they will no longer prevent checkout, build, etc.
I'm guessing that deleting the former employees workspace will get rid of the pending (now-undone) changes, but I haven't tried it yet.
In the visual studio Source Control Explorer window, I can see my own "add" operations, but do not see the "add" operations for other users. I can see all other operations (rename, edit, etc), but cannot see any add's.
Anyone know how to turn this on, or how to view add's otherwise?
I don't think there's a way to view other people's pending adds. The items shown in SCE represent the latest state on the server, modulo any changes that are pending in the currently selected workspace. In other words, if you switch to another workspace in the dropdown at the top, you won't even see your own pending adds.
Closest substitute I can think of is the "Team Members" feature introduced in the Fall '08 power tools. In short, you can quickly view anyone's pending changes (along with shelvesets & checkin history) by right clicking on their name in Team Explorer.