Choosing Configuration Items in a Change Request Process

[adminperson]

Choosing Configuration Items in a Change Request Process

I have a few questions about choosing configuration items on a change request.
When creating a change request, users must select a Configuration Item (CI) from a CMDB with over 1000+ options.

What is the best practice for users to navigate through 1000s or even 10,000s of CIs?

When looking at the options, some do not have a name but have the "next hop rule" class or MSFT SQL Instance class. What do people generally do with those classes? Hide them? Stop discovering them?

At the end of the day, how do we help change request submitters easily find information on the CI on the change request form?

[Dr Atul G- LNG]

 HI @adminperson 

Greetings!!

On change we add as many as CI but primary CI will be one only. So its on user / requestor which CI is main which is going to be impacted most with this change and rest CI can be added under affected CI / Impacted Service/CI list.