Use > Run > Problem Management > Problem Management procedures > Relate problem records

How to relate problem records

Service Management records are often linked to one another because you cannot always complete a problem without investigating incidents or their causes, or putting changes in motion. Service Management lists related records in a separate tab on the change form.

The Related records tab enables you to review, create, and delete relationships among Service Management records. The bracketed number in the tab label displays the number of related records for the current record. There are two types of related records:

  • Causes of the record are other changes, incidents, or problems that triggered the current record.

    Example: An employee requests a certain change to an email account. The request triggered an incident because there is an email server outage. You cannot complete the change until the incident status is closed.

  • Effects of the record are other changes, incidents, or problems that are the result of the current record.

    Example: The incident to repair the email server outage generates a problem record because this is a recurring outage that requires investigation. The problem resolution requires finding the root cause for the outage. When the outage is resolved, the incident is resolved. When the incident is resolved, the change request can be resolved.

Resolving a request for change, an incident, or a problem can also involve hardware or software acquisition, or even require a new service to be available. Service Management also enables you to link asset records to changes, incidents, or problems.

Related topics