How to properly tie CI's to Change Requests
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2025 05:09 AM
Hey Guys,
Sorry if this is the wrong place but I wanted to know the best way to relate ci's to a change request. My company is wanting to basically tie a Service and Service offering at the Change Request level and actual CI's at the change task level. BUT also wants to stay as out of box as possible with keeping best practices in mine.
I'm concerned that this is not the proper way to do this but also don't know enough about change or the cmdb to guide us on this. Curious to hear any thoughts or opinions.
An example would be if one change request such as a deployment would change the schema of a database ( ci 1 ) and push web code to a server (CI 2 )
What would be the best practice for something like this?
Thankyou guys
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2025 05:15 AM
Hi @johansec
I worked as a Change Manager and happy to gudie you
My company is wanting to basically tie a Service and Service offering at the Change Request level and actual CI's at the change task level.
Atul:That’s incorrect. A Change must have a CI (Configuration Item), and the CI helps to detect conflicts. So, along with the Service and SO, please make sure to use the CI on the Change form.
I'm concerned that this is not the proper way to do this but also don't know enough about change or the cmdb to guide us on this. Curious to hear any thoughts or opinions.
Atul: To know more about Change
Along this best is Go to Now create ( learning.servicenow.com/nowcreate) Go to Assets --> and search for Change Management and you will get a lot of workshop deck. Best to go the same.
here are my videos
Legacy: https://youtu.be/YNT-kaQOxDs
Morden Change: https://youtu.be/UV_Tac-AVDw
DevOps Chaneg: https://youtu.be/h0nDwFONOc8
An example would be if one change request such as a deployment would change the schema of a database ( ci 1 ) and push web code to a server (CI 2 )
Atul:No, that's again incorrect. You can create the change task for different steps in the change process, but you should only use those CIs that are either on the change form or under affected or impacted CIs—nothing else.
What would be the best practice for something like this?
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************