Is there a way to Link a WorkItem to a Label. Under "All Links" when I create a new WorkItem in Visual Studio I can select many diffrent Link Types, like Changeset, VersionedItem, etc, but theres no type for Label.
The reason why I want to do it is, that I label my releases (like Version 1.0, Version 1.1) and I want to associate a Bug to a specific version of my software.
Isn´t it support to link a WorkItem to a Label or how should I associate a Bug to a version of my software?
Update:
I´m following the Single Team Branching Model (one Dev and one Main branch) documented in the Visual Studio TFS Branching Guide 2010.
You cannot link to a label. However you can achieve your goal in other ways.
First of all, I suggest to use branching instead of labelling to keep track of multiple released versions. In my opninion using branches is a better mechanism then labelling. See also the branching guidance on codeplex
To link your bug to a version of your software, use the Iteration Path in the work item. This field is exactly for that purpose.
Using iteration path field is one option and it gives you the ability to track a work item between versions.
But if you want higher resolution, there is another way:
Team Build marks source code with a label before every build. The bug item type in CMMI project template contains fields called "Found In" and "Fixed In". In these fields you can select from build labels.
Use of these fields allow you to mark any work item with two specific builds. One for when it was found and one for when it was fixed.
Additionally Team Build updates "Fixed In" field of every work item with the label of the build, after the build completes successfully and all tests are ran without a problem.
If you don't have these fields on your work item type, you can always add them using the work item template editor that comes with TFS Power Tools.
Related
I am coming from a ClearCase (SCM) perspective but can you filter the (TFS) Source Control Explorer in Visual Studio based upon a label or exclude projects based upon a label? Where I work they use TFS and have over a thousand projects. It would certainly be nice to be able to only view active projects.
I don't think labels do what you think they do. Labels are intended to "tag" a specific version of code. Like, for example, if you release version 3.0 of an application and you don't want to create a branch for it but want the ability to retrieve all of the source that went into it at a later time, you can label that version of the source.
So no, you can't filter by a label. There's no way to filter the source control explorer view other than by being denied read permissions.
I have several checkins related to a single work item. Is there a way to get a summary of all these checkins, so I can see the difference between files before I've started working on them (like, at the moment of changeset A), and their final form (changeset B)? I would use View history and compare the folders of changeset A and changeset B, but that will give me lots of diffs that were made by other people in different files that are of no interest to me.
Edit: As suggested by Patrick-MSFT, I tried to use TFS Sidekicks, but for some reason I don't seem to get any result whatever combination of filters I use.
You can achieve this by using TFS Sidekicks. You can search for your single work item and it will give you a consolidated view.
Install sidekicks for your relevant TFS version
Open side kicks and connect it to TFS (usual tfs dialogue)
Click Tools -> Code Review Sidekick
Click by Work Items and select the appropriate Project and Query (TFS explorer workitem query). Alternatively, you can search by
changesets
Select the appropriate work item.
This will show all the changes for that work item
In your case , you want to compare all of the changes to a file,
from its state before the first checkin of this workitem and the
last checkin of the workitem (collapse all of the changes)
enter code here
Right click the file you are reviewing, the one associates with the
highest changeset number, and select 'compare with previous (not in
view)' This will show you the complete difference in your VS configured
diff tool.
Note: If the file is new and has multiple checkins, select the
one with the maximum changeset it, and select 'compare with oldest
in the view'
You can use tf difference command to compare the changes between two changesets for a specified file.
tf difference /version:669~672 program.cs /format:Context
Working with TFS 2010 Power Tools, and able to edit template Fields via Process Editor.
However the Fields tab in the editor does not show "all" fields in that Project Collection.
For example if you create a field CompanyName.FooField in Team-Project-A, you will not see it when opening the Process Editor for Team-Project-B within the same collection.
Yet, you are not allowed to create a new field with the same Name or RefName. TFS insists on Name & RefName to be unique in the Project Collection.
You are allowed to create a New field in Team-Project-B using the same Name & RefName for FooField - I'm assuming field is somehow re-used across 2 Team-Projects.
After doing some research, TFS allows for fields to be re-used as long as they are within the same Project Collection (can be in dif. team projects).
Work Item Field Explorer (Tools/ProcessEditor) shows a READ-ONLY view of all fields.
Its obvious that TFS maintains a "Global" Field definition on the Project Collection Level, yet there seem to be additional association with individual Team Project.
It would be extremely helpful if there was a similar way to EDIT all fields at once within a Project Collection as opposed to bouncing between Process Editor windows for each Team Project.
Is there anyway to do that or has anyone faced a similar problem?
It is impossible because two collection projects are necessarily created on two different data bases, so the difficulty of achieving what you want, but betweentwo projects it is possible because they are on the same database instance.
link : http://msdn.microsoft.com/en-us/library/vstudio/dd236915.aspx
I feel like there should be an easy way to do this but can't find it. Whenever I use the Parse.com framework for an iOS project, I have to add at least 10 different frameworks, and as far as I can tell I can only add 1 at a time through the Linked Frameworks and Libraries options in Xcode.
Any faster way to do this, besides creating a template project?
More specifically, the issue is that if I pick a framework, then search for another and hold CMD to select multiple, searching erases all previously selected frameworks (so I have to just scroll through the list).
Searching (as you discovered) kills the current selection. You can cmd-click to select multiple, but only if you don't use search. It's annoying as hell.
Similar to the "add file to project" dialog that forces you to click the checkbox for every single target manually (no "select all targets").
One of those annoying parts of Xcode that apple hasn't prioritized as having enough user impact to fix (since most people add one framework, or just have one or two targets for the other example).
I'm currently trying to eliminate the need for check in comments in TFS 2010 as the information about each change we make is already documented within an associated work item. The only issue with this is when you look at the file change history, the "Comments" column is blank thus making it difficult to find the change you are looking for.
To resolve this we enter the name of the work item in the check in comments but I am wondering if there is a way that I can have TFS automatically do this.
For example:
If I have a Change Request work item called "Add New Feature 1" and I check in the changes against this, I would like the check in comments to automatically have "Add New Feature 1" included in them.
Anyone know if this is possible and if so how I can accomplish this?
Thanks
You'd need to either write a Server Plugin or maybe a policy (not sure if policies can change the checkin comment though).
Checkout the following plugin which associates workitems based on the checkin comment.
http://embeddedworkitems.codeplex.com/ It's the reverse of what you want but should be adaptable.