You can associate additional CIs or services to change requests through related lists
on the Change Request form. You can also associate CIs with a change request from the dependency
The Affected CIs and Impacted Services/CIs
related lists enable you to manage CI changes.
When you first access a change request and work with these related lists, you can identify
CIs across CI classes using configuration class. You can change the configuration class
manually to filter the list and narrow the selection of CIs. For example, to filter for Linux
servers only, select Linux Servers as the Configuration
You can also create and save filters to provide quick access to common CI searches. The next
time you access the change request, the Configuration Class field
displays the last associated CI class. This automatic filter ensures that relevant CIs are
After identifying the CIs affected by a change request, you can add them to the
Affected CIs related list on the change request. After saving
affected CIs, you can open the form context menu and select the Refresh Impacted
Services option. This option populates the Impacted
Services/CIs related list based on the primary CI i.e. the CI that is mentioned
on the form.
The Impacted Services/CIs
related list represents a many-to-many
relationship between the Task [task] and CMDB [cmdb_ci] tables. The related list displays CIs,
such as business services or other CI classes, that are impacted. You can add this related
list to any task form such as an incident or problem form. You can also enter the details of
the impacted services manually, as required.
Note: The manually added CIs are not deleted each
time the impacted services are refreshed. However, business services related to the CIs are
displayed on the Impacted Services/CIs related list.