CI History Timeline Fields

[Paul Coste2]

I have a few questions about the CI History Timeline view.

1. Does this view display a change whenever any audited field is updated in the history?  
2. Aside from excluding the auditing on the CI fields, is there a way to exclude a specific field from being detected as a "Planned/Unplanned Change" while still showing the audited event in the history list view?
3. Is there a way to change the criteria for whether the CI update is associated with a Change?   Currently, the updated field is considered to be associated with a Change only when the update occurred in between the Actual Start and Actual End times.   We would like to consider setting the Actual End at the time the Change is marked as Completed, but allow for some sort of time buffer for the CI record to be updated after the Change is marked as Completed.   Perhaps the discovery schedule hasn't kicked in yet.   Or perhaps there are manual updates that need to be made to some attributes which would not be detected in discovery.   In some cases, the CI itself could be a logical CI that is updated manually.   There seem to be several valid cases where a CI record may need to be updated after the Change itself is completed.   What is the current expectation around these cases and how should I accommodate them?

[smantravadi]

Chuck Tomasi - please can you answer the above questions or redirect as appropriate?

[Paul Coste2]

I ran across an answer to this but forgot to bookmark it.  Several people had told me that this couldn't be done but I ran across an API that seems to allow you to define a script, and if that script exists it will override the default logic for detecting unplanned changes.  If someone could point me to that I would appreciate it.  While the start and end time of the change in conjunction with the date/time of the CI update is a good starting point, it falls short in a few ways and I would like to see about modifying.

[Paul Coste2 · Accepted solution]

I found it:

Create or edit a planned change validation script

Can you confirm that this is the right path?  Seems to be, but I have not tried this yet.  Would be good to know if others have had success using this capability.