Creating and managing relationships between change requests

Users create related change requests and also assign sequence numbers to dependent change requests.

To define a dependent change request with a sequence number

When you create change requests with a relationship as dependent, you should specify the sequence in which change requests are to be completed. When you specify a sequence for the dependent change requests, you must complete a change request with the sequence number 0 before you can start a change request with the sequence number 1.

In the following example, you have two related change requests. The change request to update the I/O device software has dependent relationships to two other change requests.

1. Open the change request to upgrade the operating system, and then click the Relationships tab.
2. Select the dependent change request from the Relationships table.
   The default sequence number for the dependent change request is 0.
3. Click View.

4. In the dependent change request, click the Relationships tab.

5. In the Sequence field, enter a number (for example, 1).
   The sequence number indicates the order in which the dependent change request must be completed relative to the original change request.
6. (Optional) If necessary, add any additional information about the Change form to finish relating the change request.
7. Save your work, and then close the change request.
   You return to the original change request.

8. To view the updated sequence number, refresh the table.
   The record now shows a sequence of 1. The sequence number indicates the order in which you must complete the current request relative to the dependent request. In this example, you must now complete the change request (sequence 1) to remove the old software before you can start work on installing the new software (sequence 2).

9. Save the change request.

To define a change request related to another change request, with no dependency

When you work with a change or release, you might need to define another related change request. For example, you might need to define related change requests that address similar problems. A set of related change requests can result from many changes needed by one requester at the same time.

For a release request, a related change is a manifest included within the release. For information about creating a change request related to a release request, see Creating a release manifest.

1. Open the change request, and then click the Relationships tab.
2. Select the entry from the Relationships table.

3. From the Quick Actions list, select Create Related Request > Infrastructure Change.
   In the Change form, fill in the details on the Change form as described in Create change requests in the Initiation and Recording stage.

   Important

   If you want to create the related change request by using a change template, then you must first apply the template and then create the relationship. The relationship is not created if this sequence is not followed.

4. Click Save.
5. Return to the original change request by using the breadcrumb bar.
6. Save the original change request.

To relate a change request to another change request

When you work with a change request, you might also need to relate a change request to it. Relating change requests enables the support staff to work with multiple change requests for the same requester at once. With related change requests, you can optionally designate if the current change request exists in a dependent relationship to a change request.

1. Open the change request, and then click the Relationships tab.
2. Select the entry from the Relationships table.
3. In the Request Type field, select Infrastructure Change, and then click Search.
4. In the Change Relationship Search form, use the various tabs to choose the appropriate search criteria.
5. To use more specific search criteria, click the Advanced Search tab, enter the appropriate search criteria, and then click Search.
6. In the Change Results table, select the item to relate.
7. In the Relationship Type field, select how to relate the current request to the selected change request.
   • Related To indicates the two changes are related to each other.
   • Dependent indicates the current change request depends on the original change. Dependent changes can be assigned sequence numbers to specify the sequence in which the dependent change requests should be completed.
8. Click Relate, and then click OK.
   If you create a dependent relationship, the sequence appears in the Relationships table.
9. Save the change request.

To remove a related change request

This procedure removes the change request from the relationship with another change request. It does not delete any change requests.

1. Open the change request in the Change form, and then click the Relationships tab.
2. Select the request to unrelate, and then click the Remove icon.
3. Save the change request.

To view change dependencies

1. Open the change request in the Change form, and then click the Relationships tab.
2. In the Show Related field, select Infrastructure Change.
   A list of change requests appears in the table. Changes with a dependent relationship to the current request are shown as Dependent under the Relationship Type column. The table shows the status of each request and enables you to monitor the progress of the change request implementation.
3. To view a request, select it, and then click View.