Work Item Tracking Feature Details
Below is a list of some of the key features of the Work Item Tracking portion of the Migration and Sync Toolkit.
When importing work items from a source system into TFS, it is unlikely that the work item type definitions are the same. If the type definitions are similar, it is unlikely that the field names will match each other, despite having the same content. In order
to create TFS work items from data migrated from another system, the ability to change the mapping of fields is provided by the Toolkit.
After a MigrationWorkItem has been defined, the configuration file for the toolkit enables the mapping of TFS fields to the source system's fields. Field Mappings are defined so that they may be reused for multiple migration sessions, or they can be unique
for each migration session.
In the case of at TFS to TFS migration, synchronization of work item types should be disabled for any types for which field mappings are used. Type synchronization will copy the types from the source to the target TFS which will not make use of the field mappings.
Only part of the transformation of work items includes the remapping of fields. Accompanying this is the mapping of values. Value mapping is best described with an example.
Suppose in the source system, there is a field called "Priority", and the values can be "High", "Medium", or "Low". By default, the "Priority" field in TFS is an integer field, with values of "1",
"2", or "3". A value mapping would allow the correct mappings between these fields to be created, as shown in the table below.
Policies and Conflicts
Instead of having a list of default settings (as in version control), the work item tracking portion of the toolkit specifies a list of policies for how various synchronization events should be handled. These policies are defined on the
Work Item Tracking Policies
Work items that are synchronized by the Toolkit are susceptible to several types of conflicts. The Toolkit has several policies defined to allow the users to configure how these conflicts should be resolved. Included in these policies are the mechanisms to
resolve attachment, field, and link conflicts.
Hierarchies (Areas and Iterations)
For migrated work items which contain nodes under the Areas and Iterations hierarchies, any node encountered by the Toolkit will be migrated if it does not exist on the target TFS. Note that any Areas or Iterations nodes that do not have work items that belong
to that node will not be migrated by the Toolkit.