Integration with Other Applications > Integrated Software Management > Software Configuration Management Integrations > Working with Windchill Integrations for Embedded Software Objects > Managing Software Builds > Relationship between Software Builds and Windchill Objects > Automatic Association of Defects with a Software Build
  
Automatic Association of Defects with a Software Build
Windchill Integrations for Embedded Software provides for an automatic association of defects that are either reported in or submitted to a software build. Defect-tracking adapters, such as Integrity Defects, Bugzilla and Atlassian JIRA are configured for a product or a project are queried during the automatic association process. If the query returns defects in the defect-tracking systems for which there is no associated defect object in Windchill Integrations for Embedded Software, it is then associated with the software build. In addition, if the state of a defect is updated in Windchill Integrations for Embedded Software, the state of the associated remote defect is automatically updated in the defect-tracking system.
You can enable automatic association of defects with software builds in the following ways:
Clicking Update Defect Associations from the actions menu of the Associated Defects table that appears on the software defect information page.
Using the AutoAssociateDefectToBuildWindchill Integration for Software Build Tools command.
For the automatic association process to work successfully, the Build Label attribute must match the values specified for the version fields in the remote defect-tracking system. For example, in the case of JIRA, the Build Label attribute must match either the Affected Version or the Fixed Version values in JIRA. Automatic association happens in the following cases:
When the Affected Version value of the remote defect matches the build object’s Build Label attribute. Such a defect is automatically associated to the build in Windchill Integrations for Embedded Software with Reported In as the association type.
When the Fixed Version value of the remote defect matches the build object’s Build Label attribute. Such a defect is automatically associated to the build in Windchill Integrations for Embedded Software with Submitted To as the association type.
For Integrity, the Affected Version and Fixed Version fields are not available OOTB.
The Integrity administrator must add a new customized field for both, cf_affectedVersion and cf_Fixed Version.
A Windchill administrator must update the attributeMap.xml file by adding the following lines of code:
<DtsPdmMap type="String" dts="cf_FixVersion" pdm="FixVersion"/>
<DtsPdmMap type="String" dts="cf_AffectedVersion" pdm="AffectedVersion"/>
The creation of these fields is required for enabling the automatic association on Integrity originated defects with a Software Build using an Integrity DTS adapter.
For Bugzilla, the Affected Version and Fixed Version fields are not available OOTB. The Integrity administrator must add a new customized field for both, cf_affectedVersion and cf_Fixed Version.
For Bugzilla, the Fixed Version field is not available. A Bugzilla administrator must add a new customized field, cf_FixedVersion, in Bugzilla. A Windchill administrator must update the attributeMap.xml file by adding the following line of code:
<DtsPdmMap jira="Fixversions" bugzilla="cf_FixedVersion" pdm="FixVersion" type="String" />