Best Practice: linking multiple CIs to a Change Request

jjavier
Kilo Contributor

 

For a change request involving multiple CIs, where do we link all these CIs, since the Configuration Item field only allows one (1) entry? We were initially advised to use the Affected CIs tab for this purpose, but, I read in one of the forum replies that this tab should be used to identify other CIs that may be affected/related to the CI linked in the Configuration Item field.  Example used:  switch is down - CI is switch, affected CIs are servers, databases, apps.

find_real_file.png

find_real_file.png

2 REPLIES 2

Dominik Simunek
Tera Guru

In all change management implementations I have seen so far everybody used Affected CIs for all CIs affected by a change request. The reference field on the form stores either main configuration item or just simply one of them.

It is advised to use this Affected CIs list because then all out-of-box features for change management are using it. For example Conflict detection can be executed also for Affected CIs.

Thanks, Dominik!  Appreciate the reply and information!