Lots of people disagree about deleting Work Item form TFS, although the danger of damaging the warehouse people still want to delete Work Items.
This tool use Team System API as much as possible to decrease damage to TFS warehouse.
Attention - Deleting Work Items form TFS can cause problems in upgrading to newer versions on Team System.
Visual Studio Team System 2008 Team Foundation Server Power Tools is a set of enhancements, tools and command-line utilities that improve the Team Foundation Server user experience. For an overview of what's new in this release, see New in this Release.
Download the VSTS 2008 Team Foundation Server Power Tools (6.8 MB)
Remember - If you want to install the Best Practises Analyzer, you'll need to download Powershell if it is not already on your machine. Don't worry too much about this as the installer will detect if Powershell is missing and give you a download link you can easily use.
If you're not using VSTS 2008 yet, you can still access download the VSTS 2005 Team Foundation Server Power Tools.
Last week I tried to export WIT to excel for one of our customers and two error messages appears:
I did a research in the TfsWorkItemTracking database for those errors:
select *
from TfsWorkItemTracking..RulesAreUsed
where ID in (16362, 16365)
select distinct fld.*, fldu.*
from TfsWorkItemTracking..Fields as fld
join TfsWorkItemTracking..FieldUsages as fldu
on fld.FldID = fldu.FldID
join TfsWorkItemTracking..Rules as r
on (fld.fldid = r.iffldid or fld.fldid = r.if2fldid or fld.fldid = r.thenfldid)
and r.ID in (16362, 16365)
select distinct w.*, wu.*
from TfsWorkItemTracking..WorkItemTypes as w
join TfsWorkItemTracking..WorkItemTypeUsages as wu
on w.WorkItemTypeID = wu.WorkItemTypeID
join TfsWorkItemTracking..Rules as r
on r.RootTreeID = w.ProjectID
and w.nameconstantid = r.fld1isconstid
and (wu.fieldid = r.iffldid or wu.fieldid = r.if2fldid or wu.fieldid = r.thenfldid)
and r.ID in (16362, 16365)
And I discover that Task definition under QAProject missing two fields:
IntegrationBuild & FoundIn
I definitely hitting an issue with the WIT integration with Team Build. Once the build integration fields have been put into a work item type, they cannot be removed without causing this error (it’s a bug in the V1 code).
To workaround, you have two choices:
1.) Delete the build integration fields from the server.
2.) Add the build integration fields back to the WIT from which they were removed.
#2 is the easiest.
This is the XML to add to the type definition:
<FIELD name="Found In" refname="Microsoft.VSTS.Build.FoundIn" type="String" reportable="dimension">
<HELPTEXT>The build in which the bug was found</HELPTEXT>
<SUGGESTEDVALUES>
<LISTITEM value="<None>"/>
</SUGGESTEDVALUES>
</FIELD>
<FIELD name="Integration Build" refname="Microsoft.VSTS.Build.IntegrationBuild" type="String" reportable="dimension">
<HELPTEXT>The build in which the bug was fixed</HELPTEXT>
<SUGGESTEDVALUES>
<LISTITEM value="<None>"/>
</SUGGESTEDVALUES>
</FIELD>
Subscription Maker
There is some good "Event Subscription" tools that every one can download but those tools are limited only for Core Fields and not so comfortable to use.
V-Ness develop the "Subscription Maker" for our customers so they easily create subscriptions for any field (Core or Not) without no difficulty.
Quick Details:
Project - You will have the option to select from a list the wanted Team Project and from this project all fields will be listed in the Fields list box.
Username - List of all Team System users(AD).
Email - By picking the user the email address is taken automatically.
Event - TFS Event, some event require different fields to perform subscription.(2)
Fields - The list of all existing fields in a specific Team Project.
1.
2.
