---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Copy an incident or create a child incident

# Copy an incident or create a child incident {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Copy an incident or create a child incident without manually entering the value of
all the fields in the new incident.

## Before you begin

The Enable copy incident feature (com.snc.incident.copy.enable) and the Enable create child incident feature
(com.snc.incident.create.child.enable) incident properties must be selected in IncidentIncident Properties.

Role required: itil, sn_incident_write, or admin  
Note:  
An itil user can copy or create a child of any incident whereas a user without any role can copy only incidents that they created.

## About this task

The Copy Incident functionality copies the details of an existing incident record to a new incident record. The Create Child Incident functionality copies the details of the parent incident and links the new incident to the
parent incident. You can enable the options and add or remove fields or related lists using the copy incident and create child incident properties.

## Procedure

1. Navigate to AllIncidentOpen.  
   Note:  
   If the UI16 module link redirection feature is enabled in Service Operations Workspace (SOW) and the UI16 module supports the redirect configuration, navigating through UI16 paths automatically redirects you to the equivalent list or record pages in SOW instead of displaying the UI16 forms or lists. For more information, see [Redirect UI16 module links to Service Operations Workspace](https://www.servicenow.com/docs/ifUpA_Jb2RQW6HDDErQE2Q "Redirect classic UI16 module navigation links to the equivalent Service Operations Workspace (SOW) experience.").
2. Open an existing incident that you want to copy or from which you want to create a child incident.
3. Copy the incident or create a child incident.

   | Option | Action |
   | Copy an incident | Select the Additional actions icon ![]() and then select Copy Incident. Note: After the incident is copied, the Work notes field of the new incident is updated with the following message: Created from a similar incident: INCXXXXXX. |
   | Create a child incident | Select the Additional actions icon ![]() and then select Create Child Incident. Note: Ensure you have added the Parent Incident field and the Incident -\> Parent Incident related list to the incident form. The incident from which you create the child incident becomes the parent incident. |
   |-|-|

   {#copy-incident-or-create-child-incident__choicetable_rsq_41q_23b}
4. Fill in the remaining fields as needed.
5. Select Submit.  
   The following table lists the default fields and related lists that are copied from the parent incident.{#copy-incident-or-create-child-incident__table_qjs_htt_23b__entry__2}

   | From where | What is copied |
   |-|-|
   | Fields | * Category * Subcategory * Business Service * Configuration item * Impact * Urgency * Assignment group * Short Description * Description * Related lists * Caused by Change * Location * Company * Problem * Change Request * Parent incident {#copy-incident-or-create-child-incident__ul_ydk_3tt_23b} Note: If the problem, change, or the parent incident is not active, then details of those fields are not copied. |
   | Related lists | * Affected CIs * Impacted Services * Service Offerings {#copy-incident-or-create-child-incident__ul_ujz_jtt_23b} Note: The supported related tables are: * Affected CIs (task_ci) * Impacted Services (task_cmdb_ci_service) * Service Offerings (task_service_offering) * Business Applications (task_cmdb_ci_business_app) {#copy-incident-or-create-child-incident__ul_zbv_gqt_dnb} You cannot add any other table in this field but you can remove any of the default values. |
   [Table 1. Default fields and related lists copied from parent incident]

   {#copy-incident-or-create-child-incident__table_qjs_htt_23b}

*[\>]: and then