Relating incident requests as duplicates
You can relate an incident to another incident as a duplicate. When an incident is related as a duplicate incident to another incident, the following fields are locked and changed to read only fields for the duplicate incident:
- Status is set to Pending
- Status Reason is set to Pending Original Incident
- Operational Categorization
- Product Categorization
- Resolution Categorization
- Resolution
- Also, Relationship functions are disabled, which means you cannot add or remove relationships
When you change the status of the original incident request to Resolved, Closed, or Canceled, the system performs the following actions:
- Copies the following fields from the original request to the duplicate request:
- Operational Categorization
- Product Categorization
- Resolution
- CI
- Resolves all of the duplicate requests.
- Status Reason is set to Resolved by Original Incident.
Also, if the service indicated in the Service field of the original incident request is a registered service of the company for which the duplicate request was submitted, and the duplicate record's Service field is empty, the system copies the service from the original incident request to the duplicate.
You can also relate an incident to an incident that is already resolved or closed. If you do this, the action of relating the two requests also copies the fields listed above from the original incident to the duplicate.
When you reopen an original incident request, the related duplicate incident request gets reopened and moved to Pending status with the status reason as Pending Original Incident.
To relate an incident request as a duplicate
For information about creating relationships, see Defining-relationships.
Consider the following points when creating the relationship:
- If the current incident is a duplicate of the original incident, from the Relationship Type list, select Duplicate of.
- If the current incident is the original incident, from the Relationship Type list, select Original of.