Field Map File Schema
The field map file lets you to specify how ClearQuest fields are mapped to work item fields.
Field Map File Schema
A sample field map file is shown here:
<FieldMaps>
<FieldMap from="Criticality" to="Severity">
<ValueMaps defaultValue="3">
<ValueMap from="1-Critical" to = "1"/>
<ValueMap from="2-Major" to = "2"/>
</ValueMaps>
</FieldMap>
</FieldMaps>
The nodes and attributes that you can use in this file are as follows:
<FieldMaps> Top level container node that contains all the mappings. There is only one instance of this node per file.
<FieldMap> Child node of <FieldMaps>. Specifies one field mapping. Use multiple nodes to specify multiple mappings. The mappings are specified as attributes of this node. The attributes are:
**from **The field name in ClearQuest. Set the value to the field name in ClearQuest for which you want to specify the mapping.
to The field name in Team Foundation. Set the value to the name of the friendly name of the field in Team Foundation that the ClearQuest field should be mapped to. You must use the friendly field name, not the reference field name.
exclude Whether or not to include this field in migration. Set it to false.
<ValueMaps> Optional, unless you are specifying child <ValueMap> nodes. Child node of <FieldMap> and only one <ValueMaps> node is supported per <FieldMap> node. Contains all the value mappings for the field specified in the <FieldMap> node.
<ValueMap> Optional. Child node of <ValueMaps>. Specifies one value mapping. Create multiple nodes to specify multiple mappings. The value mapping is specified with the following attributes:
from The field value in ClearQuest. Set to the field value in ClearQuest that you want to create the mapping for.
to The field value in Team Foundation. Set the value to what the converter should use to replace the specified ClearQuest value while migrating data to Team Foundation.