Change Enablement - Actual Start Date
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2023 10:08 AM
Hello All,
At what point would a change ticket need to be reverted to new in order to change the Planned Start Date (PSD)? I have an employee who's change ticket PSD is now one day off due to unforeseen circumstances. I was speaking to the employee about modifying the ticket, where I tell him to simply place the actual day of the event within the "Actual Start/End Date" field under "Closure Information". The change itself is well known and widely accepted in the organization, nor will the action really affect much of anything.
The employee in question states the ticket needs to be re-done with the correct Planned Start Date - since it's one day on a well understood change, I disagree and believe it's perfectly fine to use the "Actual Start Date" instead. I'd understand if the week was different or if it was a change encompassing multiple days...Thoughts from the gallery? Thank you all!
-Michael

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2023 02:58 PM - edited 07-26-2023 03:09 PM
@MC_Teknaut For any change type it is a best practice to follow the schedule which is Actual Start and End should fall with in Plan start and end.
- One main reason when other users are creating CRs for the same CI it will not show the conflict in the schedule, it may cause some risk for example same CI getting rebooted in different CR while you have not completed your actual work.
- Also if there is planned outage or maintenance based on the the CR schedule would also get impacted.
- It is a ITSM process violation
If my response helped please mark it correct and helpful