Exalate updates the status whenever there is an update on the ticket triggered by ScriptRunner

[Kevin]

Hey team,

We are using Scriptrunner for the scripted fields, when the user of Sciptrunner does a change on one of this fields an event is triggered by Exalate that is changing the status on the remote side.

We would like to know if there is a way to prevent Exalate from syncing to the remote side if the latest change was done by user of Scriptrunner.

Looking forward to your update.

[Sonal_Otwani]

I think the same question raised here:

Need to Exclude update of one user

We have a requirement regarding our current integration setup between Jira Cloud and ServiceNow. We are using the ScriptRunner add-on in Jira Cloud, and we’ve observed that whenever ScriptRunner performs an update on a Jira issue, Exalate syncs that update to ServiceNow. This behavior is causing issues on the ServiceNow side. To address this, we would like to exclude or skip updates made by the ScriptRunner user from being sent through the Exalate outgoing sync. ScriptRunner Add-on User ID: 55…

[Manoj]

Yes, thank you for updating