Closing Resolved Change Requests

When receiving a newly assigned change request (CR), the engineer tries to reproduce the issue. At this point, the engineer can close the CR for several reasons, such as the issue applies to a third-party product, the issue is no longer applicable to the current release, or the engineer cannot reproduce the issue.

If the engineer determines that the CR is a real issue, then the engineer investigates further, implements the appropriate fix, and tests the fix. After completing the fix, the engineer closes the CR, and enters relevant information about the fix.

When closing a primary occurrence CR, an engineer can close a parent CR and all its child CRs at once, only close the parent CR, or close a child CR independently of its parent.

When closing a CR, the engineer enters information in the Resolution section of the Change Requests form. Use the following procedures to close CRs that are fixed or otherwise resolved.

To close a resolved change request

1. Navigate to the Quality screen, then the Change Request List view.

2. Select a CR record that you want to close as fixed.

3. In the Change Request form, complete the following steps:

   1. Select a value of Closed in the Status field.

   2. Select the reason for closing the CR in the Substatus field. Values include:

      • FOL. Fact of Life. Because of a limitation such as dependency on a third-party product, the development team has no control over the issue.

      • No Longer Applicable. The issue applies to an older or different version of the product, and not to the current version or the version under development.

      • Not Reproducible. You cannot reproduce the issue as described. (It is recommended that before closing the CR, you contact the CR creator to obtain clarification.)

      • Fixed. You corrected the issue.

4. In the Change Request list, drill down on the Change Request number (#) field.

5. In the More Info view, complete the fields as appropriate.

   Some fields are described in the following table.

   Field	Comments
   Approval	Select a value to track approval for the stage of the resolution.
   Special Tag	Select statuses or actions that other fields do not identify. You can use special tags for purposes such as reporting, tracking, querying, exporting, and localization. You can specify multiple tags.
   Tag Summary	Displays all the tags that you select in the Special Tag field.
   Fixed Build	Select the product version in which you implement the resolution.
   Files Fixed	Type the filename and archiving location of each modified electronic file for the resolution. This field is required when the Substatus field or Integration Status field changes to Fixed.
   Integration Status	Select the status of the CR on the integration branch. When the Integration Status field is Closed, the Integration Fixed Date field is automatically populated, and the Integration Fixed Build field is required.
   Integration Fixed Date	Select the date and time when the resolution is implemented in the integration branch.
   Integration Fixed Build	Select the integration branch build number in which the resolution is implemented.
   Comments	Type a comment that explains the resolution.

You can also close a resolved parent multiple occurrence change request.

To close a resolved parent multiple occurrence change request

1. For a parent CR, follow the steps in the procedure for closing resolved change requests in this topic.

   When you save the record, a message box appears.

2. Complete one of the following steps:

   • Click OK to close all the associated multiple occurrence CRs with the same resolution information as the primary CR.

   • Click Cancel to close only the primary CR.