Using Parent and Child relationship, you can view the relationship hierarchy. You can define inter-dependency between two Incidents, Configuration Items (CIs), Work Orders, and so on.
Example: If multiple Incidents are created for the same issue, you can set the first Incident as a Parent Incident and the other Incidents as Child Incidents of the Parent Incident. If the Parent Incident is updated, the respective Child Incidents are also updated (see: Parent and Child Incidents IM). Similarly, in case of Parent-Child relationship for CIs, if the Parent CI is down, it will automatically impact the Child CIs (see: CI Relations_CMDB) .
Advantages
By establishing a relationship between Incidents, multiple Incidents of similar nature can be handled and updated at the same time.
Quick and easy identification of issues due to the established Parent- Child relationships.
How to Set Parent-Child Relationships?
Under the RELATIONSHIP tab of Incidents, Work Orders, Service Requests, Problem Records, Knowledge Records, CIs, and Change Records, you can link Incidents, Service Requests, Work Orders, Assets, Problem Records, and so on.
