Apparently there's a bug in the Process Editor when exporting a WIT. It happens when attempting to export a WIT to a file. The export was 'successful' - no error and no indication that something went wrong, and yet the export produced an empty XML. This occurs when the export took place offline, without prompting the user to re-connect to TFS.
The solution is to initiate a connection from the Team Explorer an repeat the export.
By default Microsoft Visual Studio Scrum 1.0 process template does not define the StateChangeDate field like MSF for Agile Software Development v5.0 does. In order to add it you need to modify the Work Item Types as follows:
Export the WIT (Task, Bug or Impediment) using the Process Editor or witadmin to a file.
Add the following block within the <FIELDS> element:<FIELD refname="Microsoft.VSTS.Common.StateChangeDate" name="State Change Date" type="DateTime">
<SERVERDEFAULT from="clock" />
<HELPTEXT>Date and time that the value of the State field changed.</HELPTEXT>
Save the file, and import it back to...
Every so often, when new users get introduced to TFS this question pops up:
"How can I assign a task to multiple people?"
My common answer is a task in TFS is not a grocery list, suggesting that, each task is assigned to a particular individual on certain timeframe. This task, or a bug, impediment or some other private work item depending on the project’s process template, can be reassigned when needed but it will always be assigned to a single owner.
Reasoning? Like a grocery list, each item can be picked up by single person at a time.
AIT's WordToTFS is a helpful tool, integrated as Word add-in for importing\exporting work items between TFS and Word.
On my first attempt to connect to TFS from Word, an error was raised:Missing Fields: "There are one or more mapping fields specified that are not available on the server. This might result in problems while publishing work items."
This message raised in case of mismatch between the TFS Work Item Template fields discovered upon connection to the add-in's fields of its current template.
The solution is simply switching to the correct template:
In WordToTFS tab, disconnect from the TFS.
From the Template group, select the...
The MSDN article Choose a Process Template, describes the main distinctions between MSF for Agile and MSF for CMMI but doesn’t cover the newer Microsoft Visual Studio Scrum 1.0 process template. So here it is, MSDN’s lost article: “Main Distinctions between MSF for Agile and Scrum”.