Changes to the `Configuration Item` field in an Incident caused comments from other tasks to sync

[SooraC]

Hi team,

I would appreciate your guidance on best practices for debugging this issue.

When a user changed the 'Configuration Item' field under an incident, comments from two different catalog items (both associated with the same 'Configuration Item' value) were synced and added to the incident. I believe the change in the 'Configuration Item' field is the trigger since the comments were carried over at the exact same time/second. I am currently investigating where this logic is being implemented.

1. Incident History Logs: Would there be a history log of the incident that could help identify which business rule, client script, or UI action caused the sync?

2. Relevant Configuration Settings: Under which configuration or module might this action typically fall, to help narrow down where I should investigate this logic?

Any insight or recommendations you could provide would be greatly appreciated.

[Bert_c1]

Client Scripts is one place to check, those defined on the incident table and type 'onChange'. Also, there are business rule that can be involved. Maybe some other means. More details on how updating an incident causes updates from catalog items is needed. what are the steps to reproduce?