Team Foundation Server - Work Item Tracking Forum

Default value in new Decription fields in work item

Sun, 22 Nov 2009 12:35:28 Z

I've edit the WI's structure and added a new description field from type HTML.
I would liek this description attribute to have a default template whenver createing new WI. I only know how to define a simple default vaules for fields, like severity and status, but I don;t know how to define default template like:

Requirment Info

Please fill relevant sections according to the template below:

1. DB:

2. Operational Measurements:

3. Licensing Implications:

Please advise,

Assigned To field in Change Request in TFS 2010 Beta2

Mon, 23 Nov 2009 05:13:17 Z

I am currently having an issue in saving an existing Change Request that I copied from the CMMI 5.0 beta 2 template to customize. (The rest - Bug,Task and Risk are taken from the Agile template) - i.e while editing a CR in my application that uses the TFS APIs.

It says the status of the CR's 'Assigned To' field is 'InvalidNotEmpty', when I make a transition from any state to the 'Closed' state and try to save it (Active-->Closed, Proposed-->Closed & Resolved-->Closed). I can't find any rules related to this in the process template. The same happens with the Requirement WI also. But, Other fields and transitions work fine.

I edited a CR and requirement directly in the VS Team Explorer too, and saw the "Assigned To" field is cleared and disabled. Has this been deliberately changed in Beta2? Is this what InvalidNotEmpty means? Isn't Work Item Tracking all about retaining Assigned To and other field values, even when a work item enters the closed state?

I have posted in the forums but got no help. Contents of my ChangeRequest.xml below. Can someone tell me what am I missing? This is quite urgent too..

Thanks in advance
Tara.

<WITD application="Work item type editor" version="1.0">
  <WORKITEMTYPE name="Change Request">
    <DESCRIPTION>Includes information to track changes through the MSF for Agile Process Development</DESCRIPTION>
    <FIELDS>
      <FIELD name="Id" refname="System.Id" type="Integer">
      </FIELD>
      <FIELD name="Title" refname="System.Title" type="String">
		<HELPTEXT>Short description of the change request used to differentiate it in a list or report</HELPTEXT>
        <REQUIRED/>
      </FIELD>
      <FIELD name="Assigned To" refname="System.AssignedTo" type="String" syncnamechanges="true">
        <VALIDUSER/>
      </FIELD>
      <FIELD name="History" refname="System.History" type="History">
		  <HELPTEXT>Discussion thread and other historical information</HELPTEXT>
      </FIELD>
      <FIELD name="Area Path" refname="System.AreaPath" type="TreePath">
		  <HELPTEXT>The area of the product with which this change request is associated</HELPTEXT>
      </FIELD>
      <FIELD name="Iteration Path" refname="System.IterationPath" type="TreePath">
		  <HELPTEXT>The iteration of the product with which this change request is associated</HELPTEXT>
      </FIELD>
      <FIELD name="State" refname="System.State" type="String">
		  <HELPTEXT>The workflow state of the change request</HELPTEXT>
      </FIELD>
      <FIELD name="Reason" refname="System.Reason" type="String">
		  <HELPTEXT>The reason why the change request is in the current state</HELPTEXT>
      </FIELD>
      <FIELD name="Changed Date" refname="System.ChangedDate" type="DateTime">
      </FIELD>
      <FIELD name="Changed By" refname="System.ChangedBy" type="String" syncnamechanges="true">
        <VALIDUSER/>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Created Date" refname="System.CreatedDate" type="DateTime">
      </FIELD>
      <FIELD name="Created By" refname="System.CreatedBy" type="String" syncnamechanges="true">
      </FIELD>
      <FIELD name="Description" refname="System.Description" type="PlainText">
        <HELPTEXT>Business objective of this change, with links to supporting documents.</HELPTEXT>
      </FIELD>
      <!-- *************** Common Fields ****************   -->
      <FIELD name="State Change Date" refname="Microsoft.VSTS.Common.StateChangeDate" type="DateTime">
        <WHENCHANGED field="System.State">
          <SERVERDEFAULT from="clock"/>
        </WHENCHANGED>
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Activated Date" refname="Microsoft.VSTS.Common.ActivatedDate" type="DateTime" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Activated By" refname="Microsoft.VSTS.Common.ActivatedBy" type="String" syncnamechanges="true" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Resolved Date" refname="Microsoft.VSTS.Common.ResolvedDate" type="DateTime" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Resolved By" refname="Microsoft.VSTS.Common.ResolvedBy" type="String" syncnamechanges="true" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Resolved Reason" refname="Microsoft.VSTS.Common.ResolvedReason" type="String" reportable="dimension" />
      <FIELD name="Closed Date" refname="Microsoft.VSTS.Common.ClosedDate" type="DateTime" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Closed By" refname="Microsoft.VSTS.Common.ClosedBy" type="String" syncnamechanges="true" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Priority" refname="Microsoft.VSTS.Common.Priority" type="Integer" reportable="dimension">
        <HELPTEXT>Priority for incorporating the change request, based on business goals</HELPTEXT>
        <REQUIRED/>
        <ALLOWEDVALUES>
          <LISTITEM value="1"/>
          <LISTITEM value="2"/>
          <LISTITEM value="3"/>
          <LISTITEM value="4"/>
        </ALLOWEDVALUES>
        <DEFAULT from="value" value="2"/>
      </FIELD>
      <FIELD name="Triage" refname="Microsoft.VSTS.Common.Triage" type="String" reportable="dimension">
        <HELPTEXT>Status of triaging the change request</HELPTEXT>
        <REQUIRED/>
        <ALLOWEDVALUES>
          <LISTITEM value="Pending"/>
          <LISTITEM value="More Info"/>
          <LISTITEM value="Info Recv"/>
          <LISTITEM value="Triaged"/>
        </ALLOWEDVALUES>
        <DEFAULT from="value" value="Pending"/>
      </FIELD>
      <!-- **************** Build Integration Fields *******************************************  -->
      <FIELD name="Integration Build" refname="Microsoft.VSTS.Build.IntegrationBuild" type="String" reportable="dimension">
		  <HELPTEXT>The build in which the change request was completed</HELPTEXT>
        <SUGGESTEDVALUES>
          <LISTITEM value="None"/>
        </SUGGESTEDVALUES>
      </FIELD>
      <!-- **************** Scheduling Fields *************************************************  -->
      <FIELD name="Remaining Work" refname="Microsoft.VSTS.Scheduling.RemainingWork" type="Double" reportable="measure"  formula="sum">
		  <HELPTEXT>An estimate of the work remaining to complete the change request</HELPTEXT>
      </FIELD>
      <FIELD name="Completed Work" refname="Microsoft.VSTS.Scheduling.CompletedWork" type="Double" reportable="measure" formula="sum">
		  <HELPTEXT>The work that has been expended for this change request</HELPTEXT>
      </FIELD>
      <FIELD name="Original Estimate" refname="Microsoft.VSTS.Scheduling.OriginalEstimate" type="Double" reportable="measure" formula="sum">
        <HELPTEXT>The original estimate of work required.</HELPTEXT>
      </FIELD>
      <FIELD name="Blocked" refname="Microsoft.VSTS.CMMI.Blocked" type="String" reportable="dimension">
        <ALLOWEDVALUES>
          <LISTITEM value="Yes"/>
          <LISTITEM value="No"/>
        </ALLOWEDVALUES>
        <DEFAULT from="value" value="No"/>
      </FIELD>
      <FIELD name="Justification" refname="Microsoft.VSTS.CMMI.Justification" type="HTML">
      </FIELD>
      <FIELD name="Impact on Architecture" refname="Microsoft.VSTS.CMMI.ImpactOnArchitecture" type="HTML">
      </FIELD>
      <FIELD name="Impact on User Experience" refname="Microsoft.VSTS.CMMI.ImpactOnUserExperience" type="HTML">
      </FIELD>
      <FIELD name="Impact on Test" refname="Microsoft.VSTS.CMMI.ImpactOnTest" type="HTML">
      </FIELD>
      <FIELD name="Impact on Development" refname="Microsoft.VSTS.CMMI.ImpactOnDevelopment" type="HTML">
      </FIELD>
      <FIELD name="Impact on Technical Publications" refname="Microsoft.VSTS.CMMI.ImpactOnTechnicalPublications" type="HTML">
      </FIELD>
    </FIELDS>
    <WORKFLOW>
      <STATES>
        <STATE value="Proposed">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <EMPTY/>
            </FIELD>
          </FIELDS>
        </STATE>
        <STATE value="Active">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedReason">
              <EMPTY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <REQUIRED/>
            </FIELD>
          </FIELDS>
        </STATE>
        <STATE value="Resolved">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedReason">
              <COPY from="field" field="System.Reason" />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <REQUIRED/>
            </FIELD>
          </FIELDS>
        </STATE>
        <STATE value="Closed">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <EMPTY/>
            </FIELD>
          </FIELDS>
        </STATE>
      </STATES>
      <TRANSITIONS>
        <TRANSITION from="" to="Proposed">
          <REASONS>
            <DEFAULTREASON value="New"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="System.AssignedTo">
              <DEFAULT from="currentuser"/>
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Proposed" to="Active">
          <REASONS>
            <DEFAULTREASON value="Accepted"/>
            <REASON value="Investigate"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Active" to="Proposed">
          <REASONS>
            <DEFAULTREASON value="Investigation Complete"/>
          </REASONS>
        </TRANSITION>
        <TRANSITION from="Active" to="Resolved">
          <REASONS>
            <DEFAULTREASON value="Code Complete and System Tested"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Active" to="Closed">
          <REASONS>
            <DEFAULTREASON value="Abandoned"/>
            <REASON value="Out-of-scope"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Resolved" to="Active">
          <REASONS>
            <DEFAULTREASON value="Validation Test Failed"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Resolved" to="Closed">
          <REASONS>
            <DEFAULTREASON value="Validation Test Passed"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Proposed" to="Closed">
          <REASONS>
            <DEFAULTREASON value="Rejected"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Closed" to="Active">
          <REASONS>
            <DEFAULTREASON value="Closed in Error"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <COPY from="field" field="Microsoft.VSTS.Common.ClosedBy"/>
            </FIELD>
          </FIELDS>
        </TRANSITION>
      </TRANSITIONS>
    </WORKFLOW>
    <FORM>
      <Layout>
        <Group>
          <Column PercentWidth="100">
            <Control Type="FieldControl" FieldName="System.Title" Label="&amp;Title:" LabelPosition="Left"/>
          </Column>
        </Group>
        <Group Label="Classification">
          <Column PercentWidth="100">
            <Control Type="WorkItemClassificationControl" FieldName="System.AreaPath" Label="&amp;Area path:" LabelPosition="Left"/>
            <Control Type="WorkItemClassificationControl" FieldName="System.IterationPath" Label="&amp;Iteration path:" LabelPosition="Left"/>
          </Column>
        </Group>
        <Group Label="Status">
          <Column PercentWidth="50">
            <Control Type="FieldControl" FieldName="System.AssignedTo" Label="Assi&amp;gned To:" LabelPosition="Left"/>
            <Control Type="FieldControl" FieldName="Microsoft.VSTS.Common.Priority" Label="&amp;Priority:" LabelPosition="Left"/>          
            <Control Type="FieldControl" FieldName="Microsoft.VSTS.Common.Triage" Label="&amp;Triage:" LabelPosition="Left"/>
          </Column>
          <Column PercentWidth="50">
            <Control Type="FieldControl" FieldName="Microsoft.VSTS.CMMI.Blocked" Label="&amp;Blocked:" LabelPosition="Left"/>
            <Control Type="FieldControl" FieldName="System.State" Label="&amp;State:" LabelPosition="Left"/>
            <Control Type="FieldControl" FieldName="System.Reason" Label="&amp;Reason:" LabelPosition="Left"/>
          </Column>
        </Group>
        <TabGroup>
          <Tab Label="Description">
            <Control Type="HtmlFieldControl" FieldName="System.Description" Label="&amp;Description:" LabelPosition="Top" Dock="Fill"/>
          </Tab>
          <Tab Label="Justification">
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.Justification" Label="&amp;Justification:" LabelPosition="Top" Dock="Fill"/>
          </Tab>
          <Tab Label="Analysis">
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnArchitecture" Label="&amp;Impact on architecture:" LabelPosition="Top" Dock="Fill"/>
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnUserExperience" Label="Impact on &amp;user experience:" LabelPosition="Top" Dock="Fill"/>
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnTest" Label="Impact on &amp;test:" LabelPosition="Top" Dock="Fill"/>
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnDevelopment" Label="Impact on &amp;design/development:" LabelPosition="Top" Dock="Fill"/>
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnTechnicalPublications" Label="Impact on technical &amp;publications:" LabelPosition="Top" Dock="Fill"/>
          </Tab>
          <Tab Label="History">
            <Control Type="WorkItemLogControl" FieldName="System.History" Label="&amp;History:" LabelPosition="Top" Dock="Fill"/>
          </Tab>
          <Tab Label="Links">
            <Control Type="LinksControl">
              <LinksControlOptions>
                <WorkItemLinkFilters FilterType="exclude">
                  <Filter LinkType="Microsoft.VSTS.TestCase.SharedStepReferencedBy" />
                  <Filter LinkType="Microsoft.VSTS.Common.TestedBy" FilterOn="reversename" />
                </WorkItemLinkFilters>
              </LinksControlOptions>
            </Control>
          </Tab>
          <Tab Label="Attachments">
            <Control Type="AttachmentsControl"/>
          </Tab>
          <Tab Label="Details">
            <Group>
              <Column PercentWidth="50">
                <Group Label="Build">
                  <Column PercentWidth="100">
                    <Control Type="FieldControl" FieldName="Microsoft.VSTS.Build.IntegrationBuild" Label="&amp;Integrated in:" LabelPosition="Left"/>
                  </Column>
                </Group>
              </Column>
              <Column PercentWidth="50">
                <Group Label="Effort (Hours)">
                  <Column PercentWidth="100">
                    <Control Type="FieldControl" FieldName="Microsoft.VSTS.Scheduling.OriginalEstimate" Label="Original &amp;Estimate:" LabelPosition="Left"/>
                    <Control Type="FieldControl" FieldName="Microsoft.VSTS.Scheduling.RemainingWork" Label="&amp;Remaining work:" LabelPosition="Left"/>
                    <Control Type="FieldControl" FieldName="Microsoft.VSTS.Scheduling.CompletedWork" Label="&amp;Completed work:" LabelPosition="Left"/>
                  </Column>
                </Group>
              </Column>
            </Group>
          </Tab>
        </TabGroup>
      </Layout>
    </FORM>
  </WORKITEMTYPE>
</WITD>

Merging TFS 2008 DB's

Wed, 25 Nov 2009 08:05:17 Z

Hi!

We are running two different TFS installation on same network and domain. Now it is required to merge both TFS's and make them one. Both installation of TFS are almost of same configuration and single server installations. We specifically need to merge the work items created on both installation. Rest source control is being used from single server.

I would be more interested if some one can suggest a way to merge TFS DB's...????

Thanks!

How do I implement the transition workflows of a work item's states in my application?

Tue, 17 Nov 2009 05:29:23 Z

I am developing a windows app that performs some common TFS tasks using the 2010 Beta 2 API (like creating new team projects, new work items, selective build, etc. ).

In the process of editing existing work items, I should be able to automatically set the 'Reason' field's values according to state change of the WI (mimic-ing Visual Studio). (eg)- When I edit a bug, when state changes from Active to Resolved, the default Reason is 'Fixed' and similarly the default Reason='Deferred' when state goes from Active to Closed. (As defined in the work item type definition xml file. ) This transition is easy to capture and implement inside a simple event handler on the form, since the initial state will be Active when the Bug is edited for the first time.

I want to know how to implement the remaining transitions like Resolved to Closed (Reason=Fixed), Resolved to Active (Reason=Test failed/Not fixed) or Closed to Active (Reason=Reactivated/Regression).

I know there is a method called WorkItem.GetNextState(current_state,action), but this doesn't help as it requires a specific action.

What I have done so far is shown below:

void cmbBugState_SelectedIndexChanged(object sender, EventArgs e)
        {
            //private enum bugWorkFlows{"Fixed","Deferred","Duplicate","As Designed","Cannot Reproduce","Obsolete","Test Failed","Not Fixed","Reactivated","Regression"}
            string[] activeToResolvedReasons = { "Fixed", "Deferred", "Duplicate", "As Designed", "Cannot Reproduce", "Obsolete" };
            string[] resolvedToActiveReasons = { "Test Failed", "Not fixed" };
            string[] resolvedToClosedReasons = activeToResolvedReasons;
            string[] closedToActiveReasons = { "Reactivated", "Regression" };
            string[] activeToClosedReasons = activeToResolvedReasons;

            cmbBugReason.Items.AddRange(activeToResolvedReasons);
            // Set the default reason according to change of state of the work item.
            if (cmbBugState.SelectedItem.ToString() == "Resolved")
            {
                cmbBugReason.Enabled = true;
                cmbBugReason.SelectedItem = activeToResolvedReasons[0];
            }
            if (cmbBugState.SelectedItem.ToString() == "Closed")
            {
                cmbBugReason.Enabled = true;
                cmbBugReason.SelectedItem = activeToResolvedReasons[1];
            }
        }

Can anyone show how to handle these events on the form?

Thanks,
Tara.

Search work items > Result does not display expected result

Tue, 24 Nov 2009 09:06:18 Z

/* Sorry for the Title, it's difficult to translate my though in english...*/

Hi TFS Expert,

I get a very strange behvaviour when using query. Let me explain what I get and if anyone can explain me what's going wrong I will appreciate.
I open a new query with the following:

Team Project = @Project
And Work Item Type = Bug
And Symptom Contains nurs* (I want to search for all WI Bug which contains value 'nurse', 'nurses', 'nursing' in [Symptom] field.

The result is 5 work items. Then I edit a work item from the result tab. I confirm that [symptom] display in my example value 'nurse'.
Well in this specific work item I decide to change the value from 'nurse' to 'nURse' then I saved.

I return to the result tab then refresh by pressing F5.
Result: I get 4 work items
Expected result: I should get 5 works items.

I can close my Visual or refresh my Project, I still get 4 work items ;(

The most amazing is that IF i wait for a couple of minutes (I cannot determine exactly, sometimes i need to wait 10 min, sometimes less) without any user action (let's suppose I phone to my lovely wife) then when pressing F5 to refresh the result I get again my 5 work items !!.

Strange isn't it ? My teamate also confirm this behaviour. After a couple of minutes, refreshing the result tab provides correct results. Is it something related with SQL which is not able to refresh its data ? FYI I am using TFS 2008.

Does anyone experiment such behaviour ?

Many Thx
Terry

TFS Project Alerts sending to user specified in field

Tue, 24 Nov 2009 20:57:43 Z

So here's a scenario that I find to be extremely common yet no one has asked this question yet.

Lets say I want everyone in my group to be alerted anytime their name is selected in the Assigned To field but only to alert the selected user and not the whole group. It seems as though I need to set up a new alert for each scenario for each user? Other products I've seen have a simple "Current User" selection where it will send the alert to whoevers name is selected in the field specified. I find it hard to believe that the TFS alert system was this poorly designed as to provide such limited capability. Please tell me I'm overlooking something.

Is there a way to create an alert to check that a non-core field "contains" a value or to create a new core field?

Tue, 24 Nov 2009 20:31:17 Z

Is there anyway to create an alert that checks that a non-core field "CONTAINS" a value? The option does not exist from the alert editor and was wondering if anyone had a workaround to achieve the same results.

If not, is there a way to create a new custom core field? (Core fields allow me to use the "contains" option)

Question regarding setting up custom web service application to extend TFS 2008 functionality

Tue, 24 Nov 2009 16:00:40 Z

I've been following the following two article to try to create my own web service application that will extend the functionality of TFS.

http://msdn.microsoft.com/en-us/magazine/cc507647.aspx - basic steps
http://blogs.southworks.net/mszklanny/2006/04/14/extending-visual-studio-team-system-automatically-send-e-mail-to-user-when-assigning-a-work-item/ - code to extend tfs

I've never coded web services so my first question is once I've created my project/solution how do I do the following step:
"After Visual Studio has created the project, adjust the project's properties so that the project URL uses port 8080 (do this via the Web tab in the Project designer). Then, using the IIS management tools, create an IIS application for your project under the Team Foundation Server Web. Ensure that you put your IIS application in the Microsoft® Team Foundation Server Application Pool. After you've done this, try to debug your service to make sure you got the configuration correct."

I believe I have set the project URL correctly, however I don't seem to be able to create an IIS application under TFS Web. I also am unsure how to ensure the IIS application is under the correct AppPool directory.

Also, I've tried to make my cs code very basic to see if it can just find a workitem assigned to myself for testing purposes however since I am unable to setup the web service yet I was wondering if the following code is still valid for TFS 2008

[SoapDocumentMethod(Action = 
    "http://schemas.microsoft.com/TeamFoundation/
     2005/06/Services/Notification/03/Notify",RequestNamespace="http://schemas.microsoft.com/TeamFoundation/2005/06/    Services/Notification/03")][WebMethod]public void Notify(string eventXml, string tfsIdentityXml) { //… }

I have tried searching the web and cannot find any references or code samples for TFS 2008.

Any guidance is greatly appreciated.

TFS & MSProject - inability to remove the System.AssignedTo mapping

Tue, 24 Mar 2009 23:36:34 Z

Hi

I've taken the standard mappings for a CMMI project and attempted to remove the line

<Mapping WorkItemTrackingFieldReferenceName="System.AssignedTo" ProjectField="pjTaskResourceNames" />

and whilst it validates and uploads correctly, when I attempt to connect to the project via MSP I get the standard 80070 error.

I can't find any MS documentation stating that this field in particular is mandatory, and I am able to remove other System fields (e.g. Title), or add additional custom fields.

Is this actually an undocumented 'feature', or am I missing something?

Cheers

Giles

Not able to open WI in excel

Wed, 11 Nov 2009 18:06:04 Z

I had TFS 2008 installed. On top I have installed TFS 2010 and Controllers and Agents. Today I uninstalled the Controller and Agent was successful...!!!

Now i am unable to open the WI using TFS 2008 in my Excel 2007...any solutions????

This file is missing from the location C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies - TFSOfficeAdd-in.dll

Cheers'

Jadoo

Field [Build.FoundIn] > How to suggest last value

Mon, 23 Nov 2009 15:49:59 Z

Hi TFS Expert,

I have a question related to field [Build.FounIn]. This field display all build generated by my developper.
In my business, there is a daily build automatically generated. And sometimes more than one !
Default behaviour for this field is to display 'empty value'.

Question: I wonder if there is any chance to display the last value generated by developper (take care, I do not want the last item in ths alphabetical order, but really the last one builded). Is it possible ? So that my QA Engineer will not use the drop down list and looking for the last value.

Error when editing and saving Change Requests in 2010 Beta2

Fri, 20 Nov 2009 08:46:29 Z

Hello,

I am aware that there have been significant changes in Beta 2, and I want to know what all parts of Process Templates and Work Item Tracking have major changes in them.

I am currently having an issue in saving an existing Change Request that I copied from the CMMI 5.0 beta 2 template to customize. (The rest - Bug,Task and Risk are taken from the Agile template)

It says the status of the CR's 'Assigned To' field is 'InvalidNotEmpty', when I make a transition from any state to the 'Closed' state (Active-->Closed, Proposed-->Closed & Resolved-->Closed). I can't find any rules related to this in the process template. The same happens with the Requirement WI also. But, Other fields and transitions work fine.

I ve posted the contents of ChangeRequest.xml below:

Can someone tell me what am I missing? This is quite urgent too..

Thanks,
Tara.

<WITD application="Work item type editor" version="1.0">
  <WORKITEMTYPE name="Change Request">
    <DESCRIPTION>Includes information to track changes through the MSF for Agile Process Development</DESCRIPTION>
    <FIELDS>
      <FIELD name="Id" refname="System.Id" type="Integer">
      </FIELD>
      <FIELD name="Title" refname="System.Title" type="String">
		<HELPTEXT>Short description of the change request used to differentiate it in a list or report</HELPTEXT>
        <REQUIRED/>
      </FIELD>
      <FIELD name="Assigned To" refname="System.AssignedTo" type="String" syncnamechanges="true">
        <VALIDUSER/>
      </FIELD>
      <FIELD name="History" refname="System.History" type="History">
		  <HELPTEXT>Discussion thread and other historical information</HELPTEXT>
      </FIELD>
      <FIELD name="Area Path" refname="System.AreaPath" type="TreePath">
		  <HELPTEXT>The area of the product with which this change request is associated</HELPTEXT>
      </FIELD>
      <FIELD name="Iteration Path" refname="System.IterationPath" type="TreePath">
		  <HELPTEXT>The iteration of the product with which this change request is associated</HELPTEXT>
      </FIELD>
      <FIELD name="State" refname="System.State" type="String">
		  <HELPTEXT>The workflow state of the change request</HELPTEXT>
      </FIELD>
      <FIELD name="Reason" refname="System.Reason" type="String">
		  <HELPTEXT>The reason why the change request is in the current state</HELPTEXT>
      </FIELD>
      <FIELD name="Changed Date" refname="System.ChangedDate" type="DateTime">
      </FIELD>
      <FIELD name="Changed By" refname="System.ChangedBy" type="String" syncnamechanges="true">
        <VALIDUSER/>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Created Date" refname="System.CreatedDate" type="DateTime">
      </FIELD>
      <FIELD name="Created By" refname="System.CreatedBy" type="String" syncnamechanges="true">
      </FIELD>
      <FIELD name="Description" refname="System.Description" type="PlainText">
        <HELPTEXT>Business objective of this change, with links to supporting documents.</HELPTEXT>
      </FIELD>
      <!-- *************** Common Fields ****************   -->
      <FIELD name="State Change Date" refname="Microsoft.VSTS.Common.StateChangeDate" type="DateTime">
        <WHENCHANGED field="System.State">
          <SERVERDEFAULT from="clock"/>
        </WHENCHANGED>
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Activated Date" refname="Microsoft.VSTS.Common.ActivatedDate" type="DateTime" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Activated By" refname="Microsoft.VSTS.Common.ActivatedBy" type="String" syncnamechanges="true" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Resolved Date" refname="Microsoft.VSTS.Common.ResolvedDate" type="DateTime" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Resolved By" refname="Microsoft.VSTS.Common.ResolvedBy" type="String" syncnamechanges="true" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Resolved Reason" refname="Microsoft.VSTS.Common.ResolvedReason" type="String" reportable="dimension" />
      <FIELD name="Closed Date" refname="Microsoft.VSTS.Common.ClosedDate" type="DateTime" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Closed By" refname="Microsoft.VSTS.Common.ClosedBy" type="String" syncnamechanges="true" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY/>
        </WHENNOTCHANGED>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Priority" refname="Microsoft.VSTS.Common.Priority" type="Integer" reportable="dimension">
        <HELPTEXT>Priority for incorporating the change request, based on business goals</HELPTEXT>
        <REQUIRED/>
        <ALLOWEDVALUES>
          <LISTITEM value="1"/>
          <LISTITEM value="2"/>
          <LISTITEM value="3"/>
          <LISTITEM value="4"/>
        </ALLOWEDVALUES>
        <DEFAULT from="value" value="2"/>
      </FIELD>
      <FIELD name="Triage" refname="Microsoft.VSTS.Common.Triage" type="String" reportable="dimension">
        <HELPTEXT>Status of triaging the change request</HELPTEXT>
        <REQUIRED/>
        <ALLOWEDVALUES>
          <LISTITEM value="Pending"/>
          <LISTITEM value="More Info"/>
          <LISTITEM value="Info Recv"/>
          <LISTITEM value="Triaged"/>
        </ALLOWEDVALUES>
        <DEFAULT from="value" value="Pending"/>
      </FIELD>
      <!-- **************** Build Integration Fields *******************************************  -->
      <FIELD name="Integration Build" refname="Microsoft.VSTS.Build.IntegrationBuild" type="String" reportable="dimension">
		  <HELPTEXT>The build in which the change request was completed</HELPTEXT>
        <SUGGESTEDVALUES>
          <LISTITEM value="None"/>
        </SUGGESTEDVALUES>
      </FIELD>
      <!-- **************** Scheduling Fields *************************************************  -->
      <FIELD name="Remaining Work" refname="Microsoft.VSTS.Scheduling.RemainingWork" type="Double" reportable="measure"  formula="sum">
		  <HELPTEXT>An estimate of the work remaining to complete the change request</HELPTEXT>
      </FIELD>
      <FIELD name="Completed Work" refname="Microsoft.VSTS.Scheduling.CompletedWork" type="Double" reportable="measure" formula="sum">
		  <HELPTEXT>The work that has been expended for this change request</HELPTEXT>
      </FIELD>
      <FIELD name="Original Estimate" refname="Microsoft.VSTS.Scheduling.OriginalEstimate" type="Double" reportable="measure" formula="sum">
        <HELPTEXT>The original estimate of work required.</HELPTEXT>
      </FIELD>
      <FIELD name="Blocked" refname="Microsoft.VSTS.CMMI.Blocked" type="String" reportable="dimension">
        <ALLOWEDVALUES>
          <LISTITEM value="Yes"/>
          <LISTITEM value="No"/>
        </ALLOWEDVALUES>
        <DEFAULT from="value" value="No"/>
      </FIELD>
      <FIELD name="Justification" refname="Microsoft.VSTS.CMMI.Justification" type="HTML">
      </FIELD>
      <FIELD name="Impact on Architecture" refname="Microsoft.VSTS.CMMI.ImpactOnArchitecture" type="HTML">
      </FIELD>
      <FIELD name="Impact on User Experience" refname="Microsoft.VSTS.CMMI.ImpactOnUserExperience" type="HTML">
      </FIELD>
      <FIELD name="Impact on Test" refname="Microsoft.VSTS.CMMI.ImpactOnTest" type="HTML">
      </FIELD>
      <FIELD name="Impact on Development" refname="Microsoft.VSTS.CMMI.ImpactOnDevelopment" type="HTML">
      </FIELD>
      <FIELD name="Impact on Technical Publications" refname="Microsoft.VSTS.CMMI.ImpactOnTechnicalPublications" type="HTML">
      </FIELD>
    </FIELDS>
    <WORKFLOW>
      <STATES>
        <STATE value="Proposed">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <EMPTY/>
            </FIELD>
          </FIELDS>
        </STATE>
        <STATE value="Active">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedReason">
              <EMPTY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <REQUIRED/>
            </FIELD>
          </FIELDS>
        </STATE>
        <STATE value="Resolved">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <EMPTY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedReason">
              <COPY from="field" field="System.Reason" />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <REQUIRED/>
            </FIELD>
          </FIELDS>
        </STATE>
        <STATE value="Closed">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <REQUIRED/>
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <EMPTY/>
            </FIELD>
          </FIELDS>
        </STATE>
      </STATES>
      <TRANSITIONS>
        <TRANSITION from="" to="Proposed">
          <REASONS>
            <DEFAULTREASON value="New"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="System.AssignedTo">
              <DEFAULT from="currentuser"/>
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Proposed" to="Active">
          <REASONS>
            <DEFAULTREASON value="Accepted"/>
            <REASON value="Investigate"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Active" to="Proposed">
          <REASONS>
            <DEFAULTREASON value="Investigation Complete"/>
          </REASONS>
        </TRANSITION>
        <TRANSITION from="Active" to="Resolved">
          <REASONS>
            <DEFAULTREASON value="Code Complete and System Tested"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Active" to="Closed">
          <REASONS>
            <DEFAULTREASON value="Abandoned"/>
            <REASON value="Out-of-scope"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Resolved" to="Active">
          <REASONS>
            <DEFAULTREASON value="Validation Test Failed"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Resolved" to="Closed">
          <REASONS>
            <DEFAULTREASON value="Validation Test Passed"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Proposed" to="Closed">
          <REASONS>
            <DEFAULTREASON value="Rejected"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Closed" to="Active">
          <REASONS>
            <DEFAULTREASON value="Closed in Error"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <COPY from="currentuser"/>
              <VALIDUSER />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <COPY from="field" field="Microsoft.VSTS.Common.ClosedBy"/>
            </FIELD>
          </FIELDS>
        </TRANSITION>
      </TRANSITIONS>
    </WORKFLOW>
    <FORM>
      <Layout>
        <Group>
          <Column PercentWidth="100">
            <Control Type="FieldControl" FieldName="System.Title" Label="&amp;Title:" LabelPosition="Left"/>
          </Column>
        </Group>
        <Group Label="Classification">
          <Column PercentWidth="100">
            <Control Type="WorkItemClassificationControl" FieldName="System.AreaPath" Label="&amp;Area path:" LabelPosition="Left"/>
            <Control Type="WorkItemClassificationControl" FieldName="System.IterationPath" Label="&amp;Iteration path:" LabelPosition="Left"/>
          </Column>
        </Group>
        <Group Label="Status">
          <Column PercentWidth="50">
            <Control Type="FieldControl" FieldName="System.AssignedTo" Label="Assi&amp;gned To:" LabelPosition="Left"/>
            <Control Type="FieldControl" FieldName="Microsoft.VSTS.Common.Priority" Label="&amp;Priority:" LabelPosition="Left"/>          
            <Control Type="FieldControl" FieldName="Microsoft.VSTS.Common.Triage" Label="&amp;Triage:" LabelPosition="Left"/>
          </Column>
          <Column PercentWidth="50">
            <Control Type="FieldControl" FieldName="Microsoft.VSTS.CMMI.Blocked" Label="&amp;Blocked:" LabelPosition="Left"/>
            <Control Type="FieldControl" FieldName="System.State" Label="&amp;State:" LabelPosition="Left"/>
            <Control Type="FieldControl" FieldName="System.Reason" Label="&amp;Reason:" LabelPosition="Left"/>
          </Column>
        </Group>
        <TabGroup>
          <Tab Label="Description">
            <Control Type="HtmlFieldControl" FieldName="System.Description" Label="&amp;Description:" LabelPosition="Top" Dock="Fill"/>
          </Tab>
          <Tab Label="Justification">
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.Justification" Label="&amp;Justification:" LabelPosition="Top" Dock="Fill"/>
          </Tab>
          <Tab Label="Analysis">
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnArchitecture" Label="&amp;Impact on architecture:" LabelPosition="Top" Dock="Fill"/>
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnUserExperience" Label="Impact on &amp;user experience:" LabelPosition="Top" Dock="Fill"/>
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnTest" Label="Impact on &amp;test:" LabelPosition="Top" Dock="Fill"/>
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnDevelopment" Label="Impact on &amp;design/development:" LabelPosition="Top" Dock="Fill"/>
            <Control Type="HtmlFieldControl" FieldName="Microsoft.VSTS.CMMI.ImpactOnTechnicalPublications" Label="Impact on technical &amp;publications:" LabelPosition="Top" Dock="Fill"/>
          </Tab>
          <Tab Label="History">
            <Control Type="WorkItemLogControl" FieldName="System.History" Label="&amp;History:" LabelPosition="Top" Dock="Fill"/>
          </Tab>
          <Tab Label="Links">
            <Control Type="LinksControl">
              <LinksControlOptions>
                <WorkItemLinkFilters FilterType="exclude">
                  <Filter LinkType="Microsoft.VSTS.TestCase.SharedStepReferencedBy" />
                  <Filter LinkType="Microsoft.VSTS.Common.TestedBy" FilterOn="reversename" />
                </WorkItemLinkFilters>
              </LinksControlOptions>
            </Control>
          </Tab>
          <Tab Label="Attachments">
            <Control Type="AttachmentsControl"/>
          </Tab>
          <Tab Label="Details">
            <Group>
              <Column PercentWidth="50">
                <Group Label="Build">
                  <Column PercentWidth="100">
                    <Control Type="FieldControl" FieldName="Microsoft.VSTS.Build.IntegrationBuild" Label="&amp;Integrated in:" LabelPosition="Left"/>
                  </Column>
                </Group>
              </Column>
              <Column PercentWidth="50">
                <Group Label="Effort (Hours)">
                  <Column PercentWidth="100">
                    <Control Type="FieldControl" FieldName="Microsoft.VSTS.Scheduling.OriginalEstimate" Label="Original &amp;Estimate:" LabelPosition="Left"/>
                    <Control Type="FieldControl" FieldName="Microsoft.VSTS.Scheduling.RemainingWork" Label="&amp;Remaining work:" LabelPosition="Left"/>
                    <Control Type="FieldControl" FieldName="Microsoft.VSTS.Scheduling.CompletedWork" Label="&amp;Completed work:" LabelPosition="Left"/>
                  </Column>
                </Group>
              </Column>
            </Group>
          </Tab>
        </TabGroup>
      </Layout>
    </FORM>
  </WORKITEMTYPE>
</WITD>

During Checkin Associate work item required fields message not display on the dialog check in box

Fri, 20 Nov 2009 18:39:38 Z

Hi,

We have customize few custom WI fields on our Team project as required fields. It works fine when we assign a work item as we fill in the required fields if not it will show the exception messge display on top of the WI template. Problem come in when we check in the changesets associated with the WI and as normal steps we open the WI direct from the check in dialog box and it did not show us the required WI fields message on the dialog box. If that a bug or a setting we can enable to show those message.?

How to Export manual test cases written in Excel to TFS

Tue, 03 Nov 2009 08:44:14 Z

Hi,

I am using excel to mailntain our test cases. Now we are moving to TFS for storing test cases.
So does anyone knows any Micro(excel) / tool to directly export test cases from Excel to TFS

Copy attributes to the linked work item?

Tue, 17 Nov 2009 14:20:54 Z

Hello everybody,

I hava a custom field build into every work item "Short description" now when I go click on the work item in the list and selecte "Add related work item" I would like that the short description is copied to the related work item.

I noticed that it happens with the Description field. Is it a rule that the System.* fields are copied ?
Can I somehow customize it that the value is copied from the work item?

Thanks,
Cheers

Is there a way to restrict access to a specific work item type?

Wed, 18 Nov 2009 15:17:03 Z

I would like to provide access to certain members of my organization but only allow them access to a specific work item type (ie. bug). I don't want them to have access to other work item types such as tasks or scenarios.

I cannot restrict the permission level by area or iterations because the specific work item type they should have access to can be from any of the areas/iterations and I'd prefer to not have duplicate entries for security purposes.

I can prevent them from creating any of other work item type by adding transition and work item field security, however that still allows them to query for all other work item types and I'd like to prevent them from being able to query them and viewing individual work item types that they should not have access to.

Any help would be great.

Add date when file is uploaded to bug work item screen

Fri, 20 Nov 2009 13:05:20 Z

Hi,

In bug work item screen, in File Attachment tab i have multiple files uploaded. I want to show custom uploaded date field next to name of file. Later sort the files by date(sorting is not issue). I was looking at fields available and i could see only "AttachFileCount". Can we add custom field for "AttachmentControl" control type.

Thanks

When link uri is too long, TF26201 exception is fire in TeamExplorer2005.

Thu, 19 Nov 2009 13:42:55 Z

Hi~~
With TeamExplorer 2005 I add new Version Item Link with Change set (C# source in Version Control).
But when this link Uri is too long (many depth and foler named Korean) , Team Explorer fire exception TF26201.
When link uri is short, saving is ok.
And Same Link add in TeamExplorer 2008, saving is ok.

Is it bug? How do we solve this problem.
We can't change Version Control construction.

Can we add new value to System.State field in work item template?

Thu, 19 Nov 2009 04:40:20 Z

Can we add new value to System.State field in work item template?

System.State has only these 3 values - Active, Resolved and Closed. We want to add one more value - "In Progress".

When I try add new value and save the WIT, it's giving an error saying "allowed values" is not allowed in System.State field.

I am using TFS 2005 version.

Please suggest.

Thanks, Srinivas.

TF26177 error with no basis in reality

Tue, 17 Nov 2009 19:36:29 Z

I've been customizing our defect process and I'm adding a state of "Verified" for when a defect fix has been tested and passed. I added the field of "Verified Date" and then placed that everywhere I needed to in the XML file. When I attempt to do the witimport I get the message "TF26177: the field Microsoft.VSTS.Common.VerifiedDate cannot be renamed from 'Verfied Date' to 'VerifiedDate'." I have searched through all of my xml config files and there is no other place that references the "Verified Date" field. I also searched through the xml file I'm currently trying to edit and nowhere do I have 'Verfied Date'. There is also no other area that calls the Verified Date. Does anyone have any suggestions? I'm getting to the point where I'm going to recommend dropping TFS and go to some other tracking system because of constant issues when trying to customize the tool to work for us. Any help you could give would be appreciated greatly.

Invalid list value for State field while adding or editing Bugs in TFS 2010 Beta 2?

Thu, 12 Nov 2009 08:46:47 Z

I am trying to create/edit work items through the TFS API in my Windows application. I get an error "Invalid list value for State field" when I try creating a new Bug itself. The process template has been only slightly modified from the "MSF for Agile Software Development v5.0 - Beta2" process template. \

Shouldn't it accept "Active", "Resolved" and "Closed" as mentioned in the bug.xml file? Below is its contents:

<?xml version="1.0" encoding="utf-8"?>
<witd:WITD application="Work item type editor" version="1.0" xmlns:witd="http://schemas.microsoft.com/VisualStudio/2008/workitemtracking/typedef">
  <WORKITEMTYPE name="Bug">
    <DESCRIPTION>Describes a divergence between required and actual behavior, and tracks the work done to correct the defect and verify the correction.</DESCRIPTION>
    <FIELDS>
      <FIELD name="Id" refname="System.Id" type="Integer" />
      <FIELD name="Title" refname="System.Title" type="String">
        <HELPTEXT>Stories affected and how</HELPTEXT>
        <REQUIRED />
      </FIELD>
      <FIELD name="System Info" refname="Microsoft.VSTS.TCM.SystemInfo" type="HTML" >
          <HELPTEXT>Test context, provided automatically by test infrastructure</HELPTEXT>
      </FIELD>
      <FIELD name="ReproSteps" refname="Microsoft.VSTS.TCM.ReproSteps" type="HTML">
          <HELPTEXT>How to see the bug. End by contrasting expected with actual behavior.</HELPTEXT>
      </FIELD>
      <FIELD name="Assigned To" refname="System.AssignedTo" type="String" syncnamechanges="true">
        <HELPTEXT>The person currently working on this bug</HELPTEXT>
        <VALIDUSER />
      </FIELD>
      <FIELD name="Area Path" refname="System.AreaPath" type="TreePath">
        <HELPTEXT>The area of the product with which this bug is associated</HELPTEXT>
      </FIELD>
      <FIELD name="Iteration Path" refname="System.IterationPath" type="TreePath">
        <HELPTEXT>The iteration within which this bug will be fixed</HELPTEXT>
      </FIELD>
      <FIELD name="History" refname="System.History" type="History">
        <HELPTEXT>Discussion thread plus automatic record of changes</HELPTEXT>
      </FIELD>
      <FIELD name="State" refname="System.State" type="String">
        <HELPTEXT>Change on reviewing, fixing or verifying the fix. Active = not yet fixed; Resolved = fix not yet verified; Closed = fix verified.</HELPTEXT>
      </FIELD>
      <FIELD name="Reason" refname="System.Reason" type="String">
        <HELPTEXT>The reason why the bug is in the current state</HELPTEXT>
      </FIELD>
      <FIELD name="Changed Date" refname="System.ChangedDate" type="DateTime" />
      <FIELD name="Changed By" refname="System.ChangedBy" type="String" syncnamechanges="true">
        <ALLOWEXISTINGVALUE />
        <VALIDUSER />
      </FIELD>
      <FIELD name="Created Date" refname="System.CreatedDate" type="DateTime" />
      <FIELD name="Created By" refname="System.CreatedBy" type="String" syncnamechanges="true" />
      <FIELD name="State Change Date" refname="Microsoft.VSTS.Common.StateChangeDate" type="DateTime">
        <WHENCHANGED field="System.State">
          <SERVERDEFAULT from="clock" />
        </WHENCHANGED>
        <WHENNOTCHANGED field="System.State">
          <READONLY />
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Activated Date" refname="Microsoft.VSTS.Common.ActivatedDate" type="DateTime" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY />
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Activated By" refname="Microsoft.VSTS.Common.ActivatedBy" type="String" syncnamechanges="true" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY />
        </WHENNOTCHANGED>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Resolved Date" refname="Microsoft.VSTS.Common.ResolvedDate" type="DateTime" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY />
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Resolved By" refname="Microsoft.VSTS.Common.ResolvedBy" type="String" syncnamechanges="true" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY />
        </WHENNOTCHANGED>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Resolved Reason" refname="Microsoft.VSTS.Common.ResolvedReason" type="String" reportable="dimension" />
      <FIELD name="Closed Date" refname="Microsoft.VSTS.Common.ClosedDate" type="DateTime" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY />
        </WHENNOTCHANGED>
      </FIELD>
      <FIELD name="Closed By" refname="Microsoft.VSTS.Common.ClosedBy" type="String" syncnamechanges="true" reportable="dimension">
        <WHENNOTCHANGED field="System.State">
          <READONLY />
        </WHENNOTCHANGED>
        <ALLOWEXISTINGVALUE />
      </FIELD>
      <FIELD name="Priority" refname="Microsoft.VSTS.Common.Priority" type="Integer" reportable="dimension">
        <HELPTEXT>Business importance. 1=must fix; 4=unimportant.</HELPTEXT>
        <ALLOWEDVALUES expanditems="true">
          <LISTITEM value="1"/>
          <LISTITEM value="2"/>
          <LISTITEM value="3"/>
          <LISTITEM value="4"/>
        </ALLOWEDVALUES>
        <DEFAULT from="value" value="2" />        
      </FIELD>
      <FIELD name="Severity" refname="Microsoft.VSTS.Common.Severity" type="String" reportable="dimension">
        <HELPTEXT>Assessment of the effect of the bug on the project</HELPTEXT>
        <ALLOWEDVALUES expanditems="true">
          <LISTITEM value="1 - Critical"/>
          <LISTITEM value="2 - High"/>
          <LISTITEM value="3 - Medium"/>
          <LISTITEM value="4 - Low"/>
        </ALLOWEDVALUES>
        <DEFAULT from="value" value="3 - Medium" />
      </FIELD>
      <FIELD name="Stack Rank" refname="Microsoft.VSTS.Common.StackRank" type="Double" reportable="dimension">
        <HELPTEXT>Work first on items with lower-valued stack rank. Set in triage.</HELPTEXT>
      </FIELD>
      <!-- **************** Team Build Integration Fields **************  -->
      <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="&lt;None&gt;" />
        </SUGGESTEDVALUES>
      </FIELD>
      <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="&lt;None&gt;" />
        </SUGGESTEDVALUES>
      </FIELD>
    </FIELDS>
    <WORKFLOW>
      <STATES>
        <STATE value="Active">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <EMPTY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <EMPTY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedReason">
              <EMPTY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <EMPTY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <EMPTY />
            </FIELD>
          </FIELDS>
        </STATE>
        <STATE value="Resolved">
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <EMPTY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <EMPTY />
            </FIELD>         
            <FIELD refname="Microsoft.VSTS.Common.ResolvedReason">
              <WHEN field="System.Reason" value="Fixed">
                <COPY from="value" value="Fixed" />
              </WHEN>
              <WHEN field="System.Reason" value="Deferred">
                <COPY from="value" value="Deferred" />
              </WHEN>
              <WHEN field="System.Reason" value="Duplicate">
                <COPY from="value" value="Duplicate" />
              </WHEN>
              <WHEN field="System.Reason" value="As Designed">
                <COPY from="value" value="As Designed" />
              </WHEN>
              <WHEN field="System.Reason" value="Cannot Reproduce">
                <COPY from="value" value="Cannot Reproduce" />
              </WHEN>
              <WHEN field="System.Reason" value="Obsolete">
                <COPY from="value" value="Obsolete" />
              </WHEN>
            </FIELD>
          </FIELDS>
        </STATE>
        <STATE value="Closed" />
      </STATES>
      <TRANSITIONS>
        <TRANSITION from="" to="Active">
          <REASONS>
            <REASON value="Build Failure" />
            <DEFAULTREASON value="New" />
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <COPY from="currentuser" />
              <VALIDUSER />
              <REQUIRED />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <SERVERDEFAULT from="clock" />
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <COPY from="currentuser" />
              <VALIDUSER />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Active" to="Resolved">
          <ACTIONS>
            <ACTION value="Microsoft.VSTS.Actions.Checkin" />
          </ACTIONS>
          <REASONS>
            <DEFAULTREASON value="Fixed" />
            <REASON value="Deferred" />
            <REASON value="Duplicate" />
            <REASON value="As Designed" />
            <REASON value="Cannot Reproduce" />
            <REASON value="Obsolete" />
          </REASONS>
          <FIELDS>
            <FIELD refname="System.AssignedTo">
              <COPY from="field" field="System.CreatedBy" />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <READONLY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <READONLY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <COPY from="currentuser" />
              <VALIDUSER />
              <REQUIRED />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <SERVERDEFAULT from="clock" />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Resolved" to="Active">
          <REASONS>
            <REASON value="Test Failed" />
            <DEFAULTREASON value="Not fixed" />
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <COPY from="currentuser" />
              <VALIDUSER />
              <REQUIRED />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <SERVERDEFAULT from="clock" />
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <COPY from="field" field="Microsoft.VSTS.Common.ResolvedBy" />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Resolved" to="Closed">
          <REASONS>
            <DEFAULTREASON value="Fixed" />
            <REASON value="Deferred" />
            <REASON value="Duplicate" />
            <REASON value="As Designed" />
            <REASON value="Cannot Reproduce" />
            <REASON value="Obsolete" />
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <READONLY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <READONLY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <READONLY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <READONLY />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <SERVERDEFAULT from="clock" />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <COPY from="currentuser" />
              <VALIDUSER />
              <REQUIRED />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Closed" to="Active">
          <REASONS>
            <REASON value="Reactivated" />
            <DEFAULTREASON value="Regression" />
          </REASONS>
          <FIELDS>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <COPY from="currentuser" />
              <VALIDUSER />
              <REQUIRED />
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <SERVERDEFAULT from="clock" />
            </FIELD>
            <FIELD refname="System.AssignedTo">
              <COPY from="field" field="Microsoft.VSTS.Common.ResolvedBy" />
            </FIELD>
          </FIELDS>
        </TRANSITION>
        <TRANSITION from="Active" to="Closed">
          <REASONS>
            <DEFAULTREASON value="Deferred"/>
            <REASON value="Obsolete"/>
            <REASON value="Duplicate"/>
            <REASON value="As Designed"/>
            <REASON value="Unable to Reproduce"/>
            <REASON value="Fixed"/>
          </REASONS>
          <FIELDS>
            <FIELD refname="System.AssignedTo">
              <COPY from="field" field="System.CreatedBy"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedDate">
              <READONLY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ActivatedBy">
              <READONLY/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedBy">
              <COPY from="currentuser"/>
              <VALIDUSER/>
              <REQUIRED/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ResolvedReason">
              <COPY from="field" field="System.Reason"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedDate">
              <SERVERDEFAULT from="clock"/>
            </FIELD>
            <FIELD refname="Microsoft.VSTS.Common.ClosedBy">
              <COPY from="currentuser"/>
              <VALIDUSER/>
              <REQUIRED/>
            </FIELD>
          </FIELDS>
        </TRANSITION>
      </TRANSITIONS>
    </WORKFLOW>
    <FORM>
      <Layout>
        <Group>
          <Column PercentWidth="100">
            <Control FieldName="System.Title" Type="FieldControl" Label="&amp;Title:" LabelPosition="Left" />
          </Column>
        </Group>
        <Group>
          <Column PercentWidth="50">
            <Group Label="Status">
              <Column PercentWidth="100">
                <Control FieldName="System.AssignedTo" Type="FieldControl" Label="Assi&amp;gned To:" LabelPosition="Left" />
                <Control FieldName="System.State" Type="FieldControl" Label="&amp;State:" LabelPosition="Left" />
                <Control FieldName="System.Reason" Type="FieldControl" Label="&amp;Reason:" LabelPosition="Left" />
              </Column>
            </Group>
          </Column>
          <Column PercentWidth="50">
            <Group Label="Classification">
              <Column PercentWidth="100">
                    <Control FieldName="System.AreaPath" Type="WorkItemClassificationControl" Label="&amp;Area:" LabelPosition="Left" />
                    <Control FieldName="System.IterationPath" Type="WorkItemClassificationControl" Label="&amp;Iteration:" LabelPosition="Left" />
              </Column>
            </Group>
          </Column>
        </Group>
        <Group>
          <Column PercentWidth="100">
            <Group Label="Planning">
              <Column PercentWidth="33">
                <Control FieldName="Microsoft.VSTS.Common.StackRank" Type="FieldControl" Label="Stack Ran&amp;k:" LabelPosition="Left" NumberFormat="DecimalNumbers" MaxLength="10" />
              </Column>
              <Column PercentWidth="33">
                <Control FieldName="Microsoft.VSTS.Common.Priority" Type="FieldControl" Label="&amp;Priority:" LabelPosition="Left" />
              </Column>
              <Column PercentWidth="33">
                <Control FieldName="Microsoft.VSTS.Common.Severity" Type="FieldControl" Label="Se&amp;verity:" LabelPosition="Left" />
              </Column>
            </Group>
          </Column>
        </Group>
        <TabGroup>
          <Tab Label="Details">
            <Group>
              <Column PercentWidth="50">
                    <Control FieldName="Microsoft.VSTS.TCM.ReproSteps" Type="HtmlFieldControl"
     Label="Steps to Repro&amp;duce:" LabelPosition="Top"  MinimumSize="(100,200)"  Dock="Fill"/>
              </Column>
              <Column PercentWidth="50">
                    <Control FieldName="System.History" Type="WorkItemLogControl" Label="&amp;History:" LabelPosition="Top" Dock="Fill" />
              </Column>
            </Group>
          </Tab>
          <Tab Label="System Info">
                <Group>
                  <Column PercentWidth="50">
                    <Control FieldName="Microsoft.VSTS.Build.FoundIn" Type="FieldControl" Label="&amp;Found in Build:" LabelPosition="Left" />
                  </Column>
                  <Column PercentWidth="50">
                    <Control FieldName="Microsoft.VSTS.Build.IntegrationBuild" Type="FieldControl" Label="In&amp;tegrated in Build:" LabelPosition="Left" />
                  </Column>
                </Group>
                <Control FieldName="Microsoft.VSTS.TCM.SystemInfo" Type="HtmlFieldControl" Label="System I&amp;nfo:" LabelPosition="Top" Dock="Fill" />
          </Tab>
          <Tab Label="Test Cases" >
              <Control Type="LinksControl" Name="TestedBy" Label="Test &amp;Cases testing this Bug:" LabelPosition="Top">
              <LinksControlOptions>
                <WorkItemLinkFilters FilterType="include">
                  <Filter LinkType="Microsoft.VSTS.Common.TestedBy" FilterOn="forwardname" />
                </WorkItemLinkFilters>
                <WorkItemTypeFilters FilterType="include">
                  <Filter WorkItemType="Test Case" />
                </WorkItemTypeFilters>
                <ExternalLinkFilters FilterType="excludeAll"/>
                <LinkColumns>
                  <LinkColumn RefName="System.ID" />
                  <LinkColumn RefName="System.WorkItemType" />
                  <LinkColumn RefName="System.Title" />
                  <LinkColumn RefName="System.AssignedTo" />
                  <LinkColumn RefName="System.State" />
                  <LinkColumn LinkAttribute="System.Links.Comment" />
                </LinkColumns>
              </LinksControlOptions>
            </Control>
          </Tab>
          <Tab Label="All Links" >
                <Control Type="LinksControl" Name="GeneralLinks">
                  <LinksControlOptions>
                    <LinkColumns>
                      <LinkColumn RefName="System.ID" />
                      <LinkColumn RefName="System.WorkItemType" />
                      <LinkColumn RefName="System.Title" />
                      <LinkColumn RefName="System.AssignedTo" />
                      <LinkColumn RefName="System.State" />
                      <LinkColumn LinkAttribute="System.Links.Comment" />
                    </LinkColumns>
                  </LinksControlOptions>
                </Control>
          </Tab>
          <Tab Label="Attachments">
            <Control Type="AttachmentsControl" LabelPosition="Top" />
          </Tab>
        </TabGroup>
      </Layout>
    </FORM>
  </WORKITEMTYPE>
</witd:WITD>

Is there any problem in this xml file?

Thanks,

Tara.

Make linking to another workitem required?

Wed, 11 Nov 2009 13:51:21 Z

Hey,

I found an old thread on how to make it required to link to another work item:
http://social.msdn.microsoft.com/forums/en-US/tfsworkitemtracking/thread/2253f293-3966-4c5f-87cf-0c763ae6e771/

I've added this code to one of my work items (2010 Beta 2), but it seems, like the "Is Item Linked" field never changes to "yes". There are two different ways which I've tried:

a) Create a new MustHaveLink WorkItem. Yellow info bar tells me, that the "Is Item Linked" contains the value "No". So I add a link, nothing changes.

b) Create a new task. Add a new linked WorkItem (the MustHaveLink WorkItem), so that the link is part of the work item as soon as it is created. But also there the yellow info bar tells me, that the "Is Item Linked" contains the value "No".

Any idea?

Dependent picklist aren't working using WHEN through TSWA or WIWA

Wed, 11 Nov 2009 21:09:49 Z

I am trying to make a field in my custom work item to change depending on the value selected in the area path. I've tried and tried but I think I'm missing something.

Can anyone see what is wrong with my code?

<FIELD name="Client OS" refname="TFS.ClientOS" type="String" reportable="dimension">
  <HELPTEXT>Used to highlight client OS associated with the escalation.</HELPTEXT>
  <REQUIRED />
  <WHEN field="System.AreaId" value="183">
     <ALLOWEDVALUES expanditems="true">
       <GLOBALLIST name="Client OS - A"/>
     </ALLOWEDVALUES>
  </WHEN>
  <WHEN field="System.AreaId" value="219">
     <ALLOWEDVALUES expanditems="true">
       <GLOBALLIST name="Client OS - B"/>
     </ALLOWEDVALUES>
  </WHEN>
</FIELD>

This may not even be the best solution for my problem because my Area Path currently looks like this:

Project\A\a1,a2,a3,a5,a5\a5.1,a5.2 etc
Project\B\b1,b2,b3,b4

My Area Path tree has at least 2 branches from the main project branch, and within each those there are varying number of child branches and within those grandchild branches.

And I'm trying to make my pick list dependent on the two branches from the main project branch.

Any assistance or suggestions are greatly appreciated.

Updated Nov 12,2009:
I noticed that the WHEN and WHENNOT clause appear to work as expected on the winforms but not through TSWA or WIWA.
Can someone give this a try and tell me if I've missed something or if I'm doing something incorrect?

Updated Nov 12, 2009 #2:
I was able to get TSWA working but adding the following code

<WHENCHANGED field="System.AreaPath">
<COPY from="value" value="" />
</WHENCHANGED>

The community content on this link explains that others ran into the same issue and this was their workaround for the getting TSWA working.

I still cannot get WIWA working and I'm not sure why since I thought it was a subset of TSWA. I tried refreshing the cache through WIWA menu option and restarting my browser but I couldn't get it to work.

I'll leave it for now and see if it will start working tomorrow.

Problem with WorkItem History

Tue, 27 Oct 2009 11:59:37 Z

Hi,

We have done migration of TFS from another server. All user accounts were recreated after migration. The SID for local users was regenerated. The only problem am having is with work item history. For example if a work item was created by user YY then its showing "Created by Unknown user on behalf of YY". I ll really appreciate if some can help me out.

Can you use the WHEN clause not in an absolute comparison? (ie. substring)

Thu, 12 Nov 2009 20:57:52 Z

I am trying to use the WHEN clause to create dependent pick lists however I was wondering if there was a way to make the WHEN clause not be an absolute comparison?

For example at the moment I have

<WHEN field="Microsoft.VSTS.Build.FoundIn" value="Product A Version 7.0.0">

However, I'd like to create the WHEN clause to be more generic if possible to create the pick list for "ANY" value that has "Product A" within the string.

Is this possible? I can't find anything anywhere I've looked, but that could just be that I'm looking in the wrong place. (*always have to try to be optimistic)

Another thought is that if I could add more than one value to the WHEN clause. Such as

<WHEN field="Microsoft.VSTS.Build.FoundIn" value="Product A Version 7.0.0" or value="Product A Version 8.0.0">

I wanna set Alert Definition when specific Field is changed.

Fri, 06 Nov 2009 01:45:55 Z

Hi~~
I wanna set when 'AreaId/AreaPath' value is changed, call subscription (e-mail or webservice).
So I edit alert like below.

1) Set with Event Subscription Tool
"CoreFields/StringFields/Field[ReferenceName='System.AreaPath']/NewValue" <> "CoreFields/StringFields/Field[ReferenceName='System.AreaPath']/OldValue"

2) Set with Alert Editor in TFS PowerTool
Field - 'AreaId' , Operator - 'Changes' --- FileterExpression -----> "ChangedFields/IntegerFields/Field[ReferenceName='System.AreaId']/NewValue" <> 'null'

But 2 cases all call alert when any field'value changed.

Is it possible to set when 'AreaId/AreaPath' value is changed?

And when I define new alert, when this alert is adjusted? realtime? or by scheduling?

Cannot open WIT from Server, error states 'Inaccessible Logs: Security"

Thu, 05 Nov 2009 21:21:25 Z

I am an administrator and should have full permissions to open a WIT from the Server for editing. Did I miss a step/install?

Creating custom TFS Web Part for Portal Page

Mon, 09 Nov 2009 19:47:22 Z

I want to create a custom Web Part for a TFS Project Portal Page. I have gone through the examples for creating a generic (non-TFS) Web Part for Sharepoint.
2
My question is: If I create a Web Part for my TFS Portal Page, then how do I get the values of the TFS server name, the name of the project for which the portal is loaded etc. from Sharepoint so that I can execute queries accordingly.

Other info:
- I am developing in VS'08.
- My web-part needs to be compatible with both VSTS'08 and VSTS'10.

Dependent HtmlFieldControl tab in work item does not get highlighted when required

Thu, 29 Oct 2009 19:38:10 Z

I am creating a custom work item. I've created two tabs with a HtmlFieldControl on each tab. I've made Tab 1 be required on the transition from="" to="active" and there is a triange and exclamation point in it's tab label to indicate that it is a required field.

Tab 2 I've made required IF another field (which has two possible values) is equal to value A. When value A is selected for the field though, the tab label does not display the triangle and exclamation point.

If I create Tab 2 to have a fieldControl element type instead of a htmfieldcontrol element type with the exact same dependency, I get the triangle and exclamation point on the tab label with the field is set to "A".

Can anyone explain why I can't get the icon notification when the tab uses an htmlfieldcontrol?

Custom Work Item Form For Each State

Mon, 09 Nov 2009 22:30:22 Z

Is there any way to make a custom form for each state of my workflow or do I have to resort to using Required and ReadOnly to get the job done? please tell me they're planning on adding this as a feature sometime in the extremely near future.

move work items between tfs projects

Sat, 07 Nov 2009 14:00:40 Z

I need to move a bulk of work items from one team project to another with history intact, thus I'm making an application to do it.
I've written the code to retrieve work items from the workitemstore, and need to copy these to the new project. The workitemtype is identical in both projects.
I found the workitem.Copy() method which appears to be what Im looking for ( http://msdn.microsoft.com/en-us/library/bb140419.aspx ), I'm however at loss how the new copy of the workitem is connected to the new project? Do I fetch the workitemtype from the new project and give that as the parameter to the copy method thereby creating the link, and then call Save() on it? Will this copy all the pertinent information?

Thanks for the help.

EDIT: Well, I did some testing and it seems to work fine.

custom work item field

Tue, 03 Nov 2009 16:23:35 Z

I have added a custom (integer) field to a modified task workitem. The problem is when the user is looking at the detail record by opening the item in team explorer the integer value shows as 80. in the work item list for that type the column shows as 70. My question is, is the work item query data pulled from the cube instead of the database? Our cube is set to update once per hour and that's the only thing that I can think of.. Do any of the other templates (standard ones support a field (computed) called % complete and if so where is it computed from..

thanks

How do I subscribe a list of individuals to be alerted about the creation/change of a specific work item?

Thu, 29 Oct 2009 18:24:29 Z

Hello,

When creating a work item (i.e. defect), it is sometimes helpful if I can include multiple people to be alerted about the defect being created, as well as automatically receive e-mail anytime a change occurs to that defect.

I understand there are ways to create alerts for 'buckets' of defects (areas, or the result of queries), but this does not seem to scale well if I want a specific individual to follow one specific bug (short of creating a new alert for every single defect of interest to them, individually).

The user scenario I am looking to solve is this:

Joe opens up a new defect and assigns it to John. Joe thinks that Mary would be interested in what happens to this bug, so puts her on a list of 'people to be notified'.

When the bug is saved, John and Mary both get e-mails about it.

When ever the bug is modified, John and Mary gets e-mails about it.

John later thinks that David should also get e-mails about this bug, and adds him onto the list of people to be notified.

(and so on).

To those who use Bugzilla, this is similar to the 'CC list' option.

Does anyone have any suggestion on how this can be done? (Please note: Am using TFS 2008).

Thank you.

Is there a way on entry to WIWA to check if a clients computer has custom control libraries installed and if not to download and install them?

Thu, 29 Oct 2009 13:46:24 Z

I may be missing a key piece of the puzzle but it seems silly (a defect on the TFS WIT side) that clients who only occassionally will use WIWA have to install custom control libraries in order for their web interface to be able to see custom controls.

Is there a way to check on logging into WIWA if the client computer has the libraries and if not to download and install them?

With any web application it should be that I only need to install everything on the server side and clients should be access the intended information. Even with other Microsoft products such as Excel and macros created, it only needs to be created on the original file and anyone else opening the file will be prompted about whether or not they choose to allow the macro.

I believe that checking the computer on login is the best solution for the following reasons:
1. Only users who access WIWA will be prompted to install the libraries
2. rolling out software onto every client does not consider those who will never use WIWA
3. those who get new systems after the roll out and will require the libraries again
4. Users accessing WIWA on their home computers connected through VPN will not be included in any software roll outs

Transition automation based on field values

Wed, 04 Nov 2009 19:52:07 Z

Is it possible to automate a state change based on a field value? So when I have my Priority set to 2 when it enters a certain state, have it automatically trigger a transition from that state to another state because the Priority is set to 2?

How reportable="measure" formula="sum" is working

Thu, 05 Nov 2009 07:53:57 Z

I have the field with [reportable="measure" formula="sum"] properties but im not able to get the sum after adding related / link items with values. May I know how the formula='Sum' is working ?

my field

<HELPTEXT>The estimated effort required to resolve this bug</HELPTEXT>

</FIELD>

Muralidharan

NodeCollection -> TreeNodeCollection

Wed, 16 Jan 2008 15:08:27 Z

Hi!
I'm working now at query builder for work items(like Team Explorer), major portion is left. For Area Path i make my own control using combobox and tree view. I want add into TreeView project nodes.

ProjectCollection collection = store.Projects;
TreeNodeConverter c = TreeNodeConverter.;
foreach (Project p in collection)
{
NodeCollection nodes = p.AreaRootNodes;
foreach (Node node in nodes)
{
......
}

Project.AreaRoots return NodeCollection object and i need TreeNodeCollection to and it's into TreeView.
How can i convert NodeCollection into TreeNodeCollection?

Thanks.

Team Foundation Excel Add In hangs for 5 minutes to retrieve work items

Tue, 09 Jun 2009 16:41:30 Z

Hello experts:

I am experiencing this when retrieving work items using the Excel Add In (Office 2007, Visual Studio 2008, Windows Vista).

I enabled the Excel log functionality as explained here and here are the relevan log results:

[Verbose, PID 4624, TID 4596, 16:17:34.972] Middle tier URL:

http://dptc04tfscomputer1.dpt.ad.company.com:8080/WorkItemTracking/v1.0/ClientService.asmx
[Verbose, PID 4624, TID 4596, 16:17:34.972] Middle tier configurationUrl:

http://dptc04tfscomputer1.dpt.ad.company.com:8080/WorkItemTracking/v1.0/ConfigurationSettingsService.asmx
[Verbose, PID 4624, TID 4596, 16:17:34.972] Default cache directory: C:\Users\vsoto\AppData\Local\Microsoft\Team Foundation\2.0\Cache
[Verbose, PID 4624, TID 4596, 16:17:34.972] InstanceInfo Id: e4876485-33d6-4433-ad14-10e6a575ec52
[Verbose, PID 4624, TID 4596, 16:17:35.566] Middle tier URL:

http://dptc04tfscomputer1.dpt.ad.company.com:8080/WorkItemTracking/v1.0/ClientService.asmx
[Verbose, PID 4624, TID 4596, 16:17:35.566] Middle tier configurationUrl:

http://dptc04tfscomputer1.dpt.ad.company.com:8080/WorkItemTracking/v1.0/ConfigurationSettingsService.asmx
[Verbose, PID 4624, TID 4596, 16:17:35.566] Default cache directory: C:\Users\vsoto\AppData\Local\Microsoft\Team Foundation\2.0\Cache
[Verbose, PID 4624, TID 4596, 16:17:35.566] InstanceInfo Id: e4876485-33d6-4433-ad14-10e6a575ec52
[Verbose, PID 4624, TID 4596, 16:17:39.769] Entering WorkItem(PS.DatastoreItem psDSI, WorkItemStore store)
[Verbose, PID 4624, TID 4596, 16:17:39.785] Entering WorkItem.PartialOpen, id = 256
[Verbose, PID 4624, TID 4596, 16:21:59.663] Constructor Field(PS.Field psField, WorkItem item, int revision). Id=10018
[Verbose, PID 4624, TID 4596, 16:21:59.663] Entering Field.Value/Get. Id=10018
[Verbose, PID 4624, TID 4596, 16:21:59.663] Leaving Field.Value/Get. Id=10018, Value=No
[Verbose, PID 4624, TID 4596, 16:21:59.663] Constructor Field(PS.Field psField, WorkItem item, int revision). Id=10012
[Verbose, PID 4624, TID 4596, 16:21:59.678] Entering Field.Value/Get. Id=10012
[Verbose, PID 4624, TID 4596, 16:21:59.678] Entering Field.FieldDefinition/Get. Id=10012
[Verbose, PID 4624, TID 4596, 16:21:59.678] Leaving Field.Value/Get. Id=10012, Value=

As you can see, there is an almost 5 minute lag beteween those calls.

Any help will be very much appreciated.

Vini

how to work with When Condition?

Thu, 29 Oct 2009 12:26:32 Z

Hi there

1- Is is possible to assign more than one vlaue in VALUE for WHEN?

2- I want to set condition for WI in following order:

If Product A selected in Product Field then set Allow and Suggested Value to GlobalList -> Component A
If Product B selected in Product Field then set Allow and Suggested Value to GlobalList -> Component B
Else set Alow and Suggested Value to GlobalList -> Components

I made first and second step but I can not set the else condition to see correct behavior...

Any Idea?

<FieldReference refname="System.Common.Component">
  <WHEN field="System.Common.Product" value="Product A">
    <ALLOWEDVALUES>
      <GLOBALLIST name="Component A" />
    </ALLOWEDVALUES>
    <SUGGESTEDVALUES>
      <GLOBALLIST name="Component A" />
    </SUGGESTEDVALUES>
  </WHEN>
  <WHEN field="System.Common.Product" value="Product B">
    <SUGGESTEDVALUES>
      <GLOBALLIST name="Component B" />
    </SUGGESTEDVALUES>
    <ALLOWEDVALUES>
      <GLOBALLIST name="Component B" />
    </ALLOWEDVALUES>
  </WHEN>
</FieldReference>

(TF210004) Custom Control not working anymore (VS2010 Beta 1 -> Beta 2)

Wed, 04 Nov 2009 10:33:22 Z

Hey,

I have a project with a few custom controls. At the moment we are using two of them.

Both are almost the same. One is a simple checkbox, just saving a "yes" or "no" value. The other one is almost the same, just uses a graphic instead of the checkbox (and saves some other data, too).

The one with the graphic is still working without a problem, but the simple checkbox is not. I always get this error:

TF210004: The control could not be loaded from the assembly.

I found some threads about the same error with the update from 2005 to 2008, the solution was to recompile the project with the new version of VS. But I already recompiled it with VS2010 Beta 2... no help.

Any ideas?