We are implementing integration with BMC Remedy.
Remedy has an OOTB feature which sends a comment to Jira every time an update is sent from Jira.
Example: when Summary is updated in Jira and sent to Remedy, Remedy sends back a comment "Summary was updated in Remedy".
We were told that this can't be disabled. This is now causing a problem at our side because it triggers again the Update webhook and the same information gets sent back to Remedy.
The solution is to add JQL in the webhook to exclude updates done by the Remedy ID. We used Last Updated By but found out that it searches the entire history. If any update was done previously by the Remedy ID, the webhook won't fire anymore.
We added a time parameter but the minimum is 1 minute. This means that when our Jira users update a field, they need to wait at least 1 minute before they can do another save. Otherwise the data won't be sent to Remedy.
Anyone encountered this before and how did was the issue solved?
We are thinking of using some sort of update flag but updating this flag triggers the update webhook as well.
