Creating Multiple Occurrence Change Requests

In the course of resolving a change request (CR), an engineer might find the same problem in another testing environment, another language version, or another product release version. For this situation, users can create parent-child relationships between CRs. With this functionality, users can create multiple occurrence CRs, and link these CRs to a parent CR.

Multiple occurrence CRs have the same functional description but apply to multiple critical factors such as environment, language, or product. Alternatively, multiple occurrence CRs can describe different symptoms that originate from the same problem and that require the same resolution. Multiple occurrence CRs must have the same owner and the same files or other components to fix.

The ability to create multiple occurrence CRs allows users to manage related issues from a single source, eliminate double-counting of product issues, and track together the linked CRs.

To create a new multiple occurrence CR (child) for an existing primary occurrence CR (parent), use the following procedure.

To create a multiple occurrence change request

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

2. Select a CR record for the parent to multiple occurrences.

3. In the Change Request form, click the menu button, and select Create Multiple Occurrence.

   The original record is copied with a new CR number. The number of the original CR (the parent) appears in the Primary Occurrence field.

4. In the new CR record, change the field values for information that is different from the original CR.

   Some fields in the Change Requests view are listed in the table in Closing Resolved Change Requests.

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

6. In the Comments field of the More Info form, record the action you took, and note any additional relevant information.

   The parent and child CRs are linked, and the new CR is a multiple occurrence CR.