Overview of Attribute Mapping
In many cases, a project manager may want to associate defects from different repositories in Windchill Integrations for Embedded Software. In such cases, the repositories could use different values for the same attributes. For example, the severity of a defect can be <High;Medium;Low> in repository A. It could be <Red;Yellow;Green> in repository B.
Windchill Integrations for Embedded Software defines an attribute mapping policy to work with attributes for defects in different repositories. It also defines a mapping policy for working with attributes belonging to the third-party defect-tracking systems. Administrators can add, change, and capture fields pertaining to attribute names and values of defect-tracking systems like Integrity Defects, Bugzilla and Atlassian JIRA in Windchill Integrations for Embedded Software. This process is called attribute mapping.
Attribute mapping and field-type definition can be done using one of the OOTB mapping files located in "$wt_home/codebase/registry/swlink/dts folder. The mapping file can be any user-defined name provided it satisfies the “attributeMap.dtd” structure rules. For example, the XML file can be called attributeMap.xml.
The attribute names and values defined in this file are used for populating fields with drop-down lists in the New Defect and the Edit Defect windows. The attribute name and value fields that are mapped between Windchill Integrations for Embedded Software and the defect-tracking systems can be one of the following types:
• A string value.
• A mapped drop-down list—Predefined out-of-the-box (OOTB) list of values in Windchill Integrations for Embedded Software. The values are mapped to the values in the defect-tracking system. In some cases, the fields are unavailable in the mapped values based on the imported content of the defect.
• A pass-through drop-down list—Populated list of values or data based on the selected defect-tracking adapter.
In all these cases, an administrator can perform the following tasks while defining attribute maps:
• Add additional fields to the OOTB list and map it to values in the defect-tracking system.
• Define the OOTB pass-through fields to be mapped fields and create mapping for them.
• Define mapped fields as pass-through fields.
• Define a map between a defect-tracking system project and a Windchill Integrations for Embedded Software context using the attributeMap.xml or one of the other OOTB mapping files.
For Integrity Defects, the “issue types” which are treated as defect types must be identified. Refer to the OOTB "$wt_home/codebase/registry/swlink/dts/integrityMappingFile.xml" file.
You select the attribute mapping file in the
Adapters Administration utility when associating a context to an adapter. Refer to
Associating a Context to an Adapter for additional information.