Associate CIs with an incident

task australia Updated Sep 10, 2026 1 min read associate-cis-with-incident.md
Raw file servicenow.com

Associate affected or impacted configuration items (CIs) with an incident record to find out how the incident affects other CIs with dependent relationships.

Before you begin

Role required: admin

About this task

Use the Configuration Item field when a single, primary CI is the cause of the incident. Use the Affected CIs or Impacted Services/CIs related list when multiple CIs are affected.

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 the incident record to which you want to associate CIs.

  3. Perform the following actions:

Options

Procedures

Configuration item

  1. Select the lookup icon [Omitted image "look-up-icon.png"] Alt text:.
  2. Select a configuration item.

Note: By default, Service Offering is filtered out and CIs with Principal Class are selected. The Principal Class filter functionality applies to new customers starting with the Paris release.

Affected CIs

  1. Select Add.
  2. Select configuration items.

Note: By default, Service Offering is filtered out and CIs with Principal Class are selected. The Principal Class filter functionality applies to new customers starting with the Paris release.

[Omitted image "affected-ci-offering-filter.png"] Alt text: Filter in Affected CIs related list

  1. Select Add Selected.

Impacted Services/CIs

  1. Select Add.
  2. Select configuration items.

Note: By default, Service Offering is filtered out.

  1. Select Add Selected.
Search documentation
Search document titles and file paths on the australia branch