Default Field Mappings for OpenText PPM and QC 10.00

The following sections describe the default field mappings that are available for integration with Quality Center defects and requirements.

Default Field Mappings for Quality Center 10.00 Defects

The table below describes the default defect mappings that can be modified for the integration between the Defects Module in Quality Center and the ALM - Defect Template with Quality Center Integration request type in OpenText PPM. The Override column indicates which field is dominant by default—OpenText PPM (if set to PPM), Quality Center (if set to QC), or neither (if set to BIDIRECTIONAL). For more information, see Creating the Mapping Between OpenText PPM and QC Fields.

Table 6-6. Default defect mappings you can modify
Quality Center Field Name, Database ID, and Field Type	OpenText PPM Field Name, Database ID ^a, and Field Type	Override
Reproducible BG_REPRODUCIBLE Y/N	Reproducible REPRODUCIBLE Y/N	QC
Project BG_PROJECT List	Application APPLICATION_CODE List	QC
Actual Fix Time BG_ACTUAL_FIX_TIME Date	Actual Fix Time (days) ACTUAL_FIX_TIME Date	QC
Closed in Version BG_CLOSING_VERSION List	Closed in Version CLOSING_VERSION Text (40)	QC
Severity BG_SEVERITY Enumeration	Severity SEVERITY Drop-down list	BIDIRECTIONAL
Closing Date BG_CLOSING_DATE Date	Closed on CLOSING_DATE Date	QC
Detected in Version BG_DETECTION_VERSION List	Detected in Version DETECTION_VERSION Text (40)	BIDIRECTIONAL
Planned Closing Version BG_PLANNED_CLOSING_VER List	Planned Closing Version PLANNED_CLOSING_VER List	BIDIRECTIONAL
Estimated Fix Time BG_ESTIMATED_FIX_TIME Number	Estimated Fix Time (days) ESTIMATED_FIX_TIME Numeric Text (10 digits)	BIDIRECTIONAL
Comments BG_DEV_COMMENTS Memo	Developer Comments DEV_COMMENTS Text (1800)	PPM
Detected on Date BG_DETECTION_DATE Date	Created On CREATION_DATE Date	PPM
Priority BG_PRIORITY Enumeration	Priority DEFECT_PRIORITY_CODE Drop-down list	BIDIRECTIONAL
Description BG_DESCRIPTION Memo	Detailed Description DEFECT_DESCRIPTION Text (1800)	BIDIRECTIONAL
Detected By BG_DETECTED_BY Quality Center users list	Detected in Quality Center by QC_DETECTED_BY Text (40)	QC
Status^{b, c} BG_STATUS Enumeration	Request Status^b STATUS_ID List	PPM^b
Status^{b, c} BG_STATUS Enumeration	Quality Center Defect Status^c KNTA_QC_DEFECT_STATUS Text (300)	QC^c
Summary BG_SUMMARY Text (255)	Summary DESCRIPTION Text (200)	BIDIRECTIONAL
a. The listed OpenText PPM database IDs are the same as in the PPM Workbench. The exact database IDs are displayed by the integration tool. b. When the Request Status field is updated in OpenText PPM, the new status is sent to Quality Center. If the new status matches one of the defect status in Quality Center, the Status field in Quality Center is updated; if not, the update is ignored by Quality Center. c. When the status of a defect is updated in Quality Center, the associated Quality Center Defect Status field in OpenText PPM is updated accordingly if the value sent by Quality Center is a valid workflow step transition in OpenText PPM.

Default Field Mappings for Quality Center 10.00 Requirements

The table below describes the default requirement mappings that can be modified for the integration between the Requirements Module in Quality Center and the ALM - Request for Change (RFC) request type or the ALM - Release Management request type in OpenText PPM. The Override column indicates which field is dominant by default—OpenText PPM (if set to PPM), Quality Center (if set to QC), or neither (if set to BIDIRECTIONAL). For more information, see step 8.

Table 6-7. Default requirement mappings you can modify
Quality Center Field Name, Database ID, and Field Type	OpenText PPM Field Name, Database ID ^a, and Field Type	Override
Priority RQ_REQ_PRIORITY Enumeration	RFC Priority PRIORITY_CODE Drop-down list	PPM
Author^b RQ_REQ_AUTHOR User list	Created By CREATED_BY User list	PPM
ITG Request Status^{c, d} RQ_USER_XX^e Enumeration	RFC Status^c STATUS_ID List	PPM^c
ITG Request Status^{c, d} RQ_USER_XX^e Enumeration	Quality Center Status^d KNTA_QC_REQUIREMENT_STATUS Text (300)	QC^d
Name RQ_REQ_NAME Text (255)	RFC Summary DESCRIPTION Text (200)	PPM
ITG Request Description RQ_USER_XX^e Memo	RFC Description RFC_DESCRIPTION Text (1800)	PPM
Assigned To RQ_USER_XX^e User list	Quality Center Assigned To User KNTA_QC_ASSIGNED_TO	PPM
a. The listed OpenText PPM database IDs are the same as in the PPM Workbench. The exact database IDs are displayed by the integration tool. b. The Author field in Quality Center displays the name of the user who created the request in OpenText PPM. Quality Center can accept any name, but OpenText PPM cannot. If you configure this field to be bidirectionally updateable and a user selects a user name in Quality Center that does not exist in OpenText PPM, the operation will fail. User name lists must therefore be synchronized. c. When the RFC Status field is updated in OpenText PPM, the new status is sent to Quality Center. If the new status matches one of the requirement statuses in Quality Center, the ITG Request Status field in Quality Center is updated; if not, the update is ignored by Quality Center. d. When the status of a requirement is updated in Quality Center, the associated Quality Center Status field in OpenText PPM is updated accordingly if the value sent by Quality Center is a valid workflow step transition in OpenText PPM. e. The Quality Center fields with the database ID of RQ_USER_XX are user fields that are added to Quality Center when using the integration tool to enable a project. The value of XX is determined when the user field is added to Quality Center.