- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2024 02:09 AM
Hello,
I just wanted to know if is there any OOB functionality exists as an incident for a Change request closes automatically after some days
or we need to write the custom script for that
Thanks,
Atik Bagwan
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2024 02:26 AM
Hi @Atik,
As you'd expect, the change process differs from Incident, and for that reason, (and to answer your question directly) there is no auto-close per se.
However, typically (and baseline configuration which also depends on the type of change), once a Change is moved to the state of implementation, a Change Task is created. Once the Change Task(s) are closed a Change will move to a Review state.
Depending on the maturity of your organization and the process adopted, it is not uncommon for changes to automatically close when Change Tasks are closed - however baseline configuration all changes are reviewed by a Change Manager before closing.
To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.
Thanks, Robbie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2024 02:33 AM
Hi @Atik
As a change manager, I will say write a custom script to close the changes but that should be applicable for all changes.
1. Failed changes should not auto closed.
2. Emergency changes should not auto closed.
3. High Risk changes should not auto closed.
also, even though changes get auto closed , still i recommend, review changes manually and then close.
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]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2024 02:26 AM
Hi @Atik,
As you'd expect, the change process differs from Incident, and for that reason, (and to answer your question directly) there is no auto-close per se.
However, typically (and baseline configuration which also depends on the type of change), once a Change is moved to the state of implementation, a Change Task is created. Once the Change Task(s) are closed a Change will move to a Review state.
Depending on the maturity of your organization and the process adopted, it is not uncommon for changes to automatically close when Change Tasks are closed - however baseline configuration all changes are reviewed by a Change Manager before closing.
To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.
Thanks, Robbie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2024 02:31 AM
Hi @Atik
As per your question, there is no out-of-the-box functionality for a Change request to automatically close after a certain number of days, similar to how it operates for incidents. To implement such functionality, customization is required to align with your organizational requirements. Typically, the closure of a change request occurs after all associated tasks have been closed. However, it's common for change managers to have the capability to review and approve changes before final closure
If this solution resolves your query, kindly mark it as the accepted solution and give it a thumbs up.
Feel free to connect with me on LinkedIn.
Best Regards,
Krushna Birla
Senior Software Engineer
Globant, Pune
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2024 02:33 AM
Hi @Atik
As a change manager, I will say write a custom script to close the changes but that should be applicable for all changes.
1. Failed changes should not auto closed.
2. Emergency changes should not auto closed.
3. High Risk changes should not auto closed.
also, even though changes get auto closed , still i recommend, review changes manually and then close.
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]
****************************************************************************************************************