Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Copy an incident or create a child incident

Copy an incident or create a child incident without manually entering the value of all the fields in the new incident.

Before you begin

  • Role required: itil, sn_incident_write, or admin
  • Select 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 at Incident > Incident Properties.

Note: An itil user can copy or create a child of any incident whereas a user without any role can copy only the incident which the user has 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 as well as add or remove fields or related list using the copy incident and create child incident properties.

Procedure

  1. Navigate to All > Incident > Open.

    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.

  2. Open an existing incident that you want to copy or from which you want to create a child incident.

  3. Perform one of the following actions.

OptionAction
Copy an incidentClick the Additional actions icon
Image omitted: context-menu.png
The Additional actions icon and then click <strong>Copy Incident</strong>.<strong>Note:</strong> After the incident is copied, the <strong>Work notes</strong> field of the new incident is updated with the following message: <code>Created from a similar incident: INCXXXXXX</code>.</td></tr><tr><td id="d137390e174"><strong>Create a child incident</strong></td><td>Click the Additional actions icon [Omitted image "context-menu.png"] Alt text: The Additional actions icon and then click <strong>Create Child Incident</strong>.<strong>Note:</strong> Ensure you have added the <strong>Parent Incident</strong> field and the <strong>Incident -&gt; Parent Incident</strong> related list to the incident form. The incident, from which you have created the child incident, is considered as the parent incident.</td></tr></tbody>
  1. Fill out the other fields, as required.

  2. Click Submit.

    The default fields and related lists that are copied from the parent incident are:

From whereWhat are 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 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 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) You cannot add any other table in this field but you can remove any of the default values.

sndocs is an independent community mirror and is not affiliated with or endorsed by ServiceNow.

ServiceNow, the ServiceNow logo, Now, and other ServiceNow marks are trademarks and/or registered trademarks of ServiceNow, Inc., in the United States and/or other countries. Other company and product names may be trademarks of the respective companies with which they are associated.

© 2026 ServiceNow, Inc. All rights reserved.

Documentation content is redistributed under the Apache License 2.0 from the ServiceNowDocs repository.