I'm a first time user of this site. Apologies in advance if I hadn't searched well enough for my question.
I'm looking at tweaking TFS 2010's bug creation abilities slightly. I'd like to force the 'Comment' field linked to the History. Basically, after someone makes a series of changes, I want to force that person to enter some details before committing the changes.
Does anyone have any experience with this?
Thanks,
Chris
You must right click on your team project, choose "Team Project settings" and then "Source Control". This launches the "Source Control Settings" window with three tabs.
1. Check out Parameters
2. Check in policy <- your target (Select “Changeset Comments Policy”)
3. Check in Note
when you select your rule, you click OK et you can test
Related
Everytime I try to edit the Lab Process Settings in a lab management template in Visual Studio 2013, I get the following error:
Has anyone seen this appearing? I tried creating a new build definition targeting the same template, but the error appears again.
OS: Windows 8.
VS: 2013 Update 2
You are most likely running TFS update 3 which changed the back-end of TFS to create work items for both the Test Plan and Test Suites now. There is something odd going on in your project, it may be that you have not "enabled" the features on the project so those things are done behind the scene.
To verify this, go the TFS portal and click on the little gear in the right hand corner, then click the control panel link (up top left) and select the project you are working under and finally select Manage the project administration page and click the overview tab. Is there an "enable features" button there?
If you go the home page of you project and click the little question mark on the top right corner and select about, what version do you have there?
You have changed the Process template to have the state "In progress" rather than "In Progress" and the default configuration is choking. If you go through your process template and make sure that the casing is correct ("In Progress") your issue should go away.
Full details and solutions: http://nakedalm.com/find-mappings-states-defined-test-suit-work-item-type/
I need to review many shelvesets using Visual Studio every day. I have added the TfsPendingChanges command to the my toolbar, but the rest of the procedure to access a shelveset (Actions/Find Shelvesets) still feels clumsy. In fact, shelveset review has nothing to do with my own pending changes. And VS11 just made it even one step longer than it already was.
Is there any way to add "Find Shelvesets" in some form directly to a menu or to a toolbar, in Visual Studio 2012?
If you go to right click and then "Customize" on any toolbar, it will bring up a dialog. Press the "Keyboard" button on it, choose File.TfsUnShelvePendingChanges and assign a Hot Key to it. I do believe that the Source Control Explorer window needs to be open and active for your hot key to work.
OR...This may not be exactly what you are looking for, but if you have the Source Control Explorer window open and active, then ALT-F ALT-R ALT-F ALT-F ALT-S will bring up the dialog. That is actually navigating File/Source Control/Find/Find Shelvesets.
The easiest way to work with Shelvesets is to use the new My Work feature. By suspending and resuming work Visual Studio will automatically do all the Shelveset magic for you with a simple drag/drop of the task that you want to have in progress.
The same applies to reviews, Suspend your current work, or create a new temporary workspace, open the Review Request, let it unshelve the changes automatically and when you're done go back to where you were by resuming your previous tasks.
It's really great once you get the hang of it. That it uses Shelvesets under the hood is nice to know, but this way you don't really need to know, it just works.
As for TWA Diff, there've been great improvements with TFS 2012 Update 2 which is almost ready to be released...
If this is only for reviews then maybe Team Web Access would be better for you?
Just navigate to http://:8080/tfs/web/, select team project, then click Source Tab and Find Shelvesets. You can then open each shelveset in new browser window and it will list all changes and allows you to quickly do compare etc.
Command that you are looking for is TfsUnshelvePendingChanges under File.
Right click on any toolbar, click on customize and a dialog will open. Go to 'Commands' tab on the top.
Choose appropriate button out of Menu Bar | Toolbar | Context Menu. Select the desired option under that. My favorite is to add it to Toolbar>Work Item Tracing (toolbar where New Item/Open Item appears).
After choosing from above step appropriately, click on 'New Command'. Then select to File>TfsUnShelvePendingChanges. This will add a shortcut to unshelve changes.
Thanks to #Alex for pointing out the correct command name. Writing here separately for people looking for answers in future.
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.
Warning - newbie question....
I had a vision that I could select what workitem I was working on, and when I checked in the code, I could associate the changeset with the workitem automatically.
I'm assuming that:
I would select a work item and state that I'm starting to work on it,
make my changes to the code base as I see fit,
each time a file is checked out, it is associated with the current work item, and
when I check in I can state that I've stopped working on that work item.
Then if I review a work item, I can see what changeset is associated with that workitem, getting the full fidelity of what changes were made for that specific work item.
Is this possible? Is it automatic? All that I have found so far is a manual association of a changeset with a work item.
The order is: make changes, choose pending changes to check-in, select work item, do check-in. You can enable a check-in policy that forces the change to associate with a work item.
Update
With TFS2012/TFS2013 Premium and Ultimate there is a much cooler way, using the "My Work" page. Before you start coding you select a work item from "Available Work Items" to "In Progress". From there you can directly jump to the "Pending Changes" page by clicking "Check In". It is also possible to suspend your work where the state of the IDE is saved.
Demo: http://go.microsoft.com/fwlink/?LinkID=251849
What you're asking for is not a good idea. That pretty much only allows you to work on one work item per team project at a time. If you can do that, then you must be living a quiet life.
Instead, TFS allows you to associate a changeset with one or more work items - when you create the changeset. This makes it easy to see exactly which code changes were made in order to address a particular work item.
It also allows automated builds to be associated with work items, and enables Test Impact analysis. I don't think any of these things would make sense if you were simply associating a work item with the code you assumed you were going to have to change to address it.
Actually at the project level you can enable "require work item" with checkin. This means that the work item be defined first so that you have somthing to associate with when a checkin takes place.
I know there is an easy way to do this with SVN so there must be a similar way with TFS.
Basically, I want to have a list of every file a particular username ever edited (IE: checked out & changed or added). This is on TFS 2008.
I found one way to do it:
Go to Source Control Explorer in Visual Studio
Right click on the project root
Select Find in Source Control -> Changesets
Enter the username you are looking for in the 'By User' field
Click find
This returns a list of changesets from the user. You can then click the details button to expand the changeset.
The answers so far return a list of changesets, not a list of files. Try:
Get-TfsItemHistory $/ -r -user username -all | Select-TfsItem | sort -unique path
Using the Powershell cmdlets also included with the Power Tools.
Bryan - the answer you provided is one way. You can also do this in fewer steps by installing the free Team Foundation Server Power Tools - October 2008 Release from MSDN. There are a number of great out-of-band updates to the Team Explorer feature set, but the one you are interested in is called the Team Members feature:
Team Members Node http://img34.imageshack.us/img34/7195/image21k.png
This will allow you to quickly search for all check-in's by a given Team Member. Look around at the other features as I am sure you will find some other handy things as well. Personally, I like the "Show Shelvesets" as it makes it much easier to use the Shelveset feature for code reviews, etc.
I know how to do this in VS2010 and I'm sure it works the very similar in VS 2008 --
In Visual Studio, open "Team Explorer" window.
Expand your main TFS branch.
Expand "Team Members" branch. Under this branch you will see the names of all TFS members.
Right-click a member, and select "Show Checkin History". This will list all the files changed (checked in) by the selected member.
I hope this helps. Good luck!