Trigger Webhook only when certain users did an update

[olivier.vanheste]

Hi,

I was wondering if it is possible to only trigger a webhook when certain users did an update or prevent the webhook being triggered when certain users did an update.

So our use case is the following, When users create/update or delete a comment, a webhook is being triggered. Now the script that get's triggered adds a comment to that issue stating it was processed succesfully. that again triggers the webhook and the script.

I can check on the user inside the script to prevent an infinite loop, but I was wondering if it was possible to even prevent the trigger happening in the firstplace? 

[Marc - Devoteam · Accepted solution]

Hi @olivier.vanheste 

Welcome to the community.

How is the setup, if this is set in an automation rule, you could add a condition in the automation rule before executing the webhook/webrequest.

User the User Condition and set the value on user who triggered the event and then validate this to a specified list of users or a group of users or else..

[olivier.vanheste]

Hi @Marc - Devoteam 

The setup is just in the webhooks page. Then we use JQL to filter the issue where it can be triggered on and select the events to trigger on.

[Marc - Devoteam]

Hi @olivier.vanheste 

There this is not possible, with an automation rule you could accomplish this.

[Bill Sheboy]

Hi @olivier.vanheste -- Welcome to the Atlassian Community!

In the suggestion from @Marc - Devoteam he noted using automation rules to detect the initiating user.  That can be re-implemented for an external process / service using a webhook...

If we assume you are triggering some external process / service based on a webhook configured within Jira, your external process / service could immediately call the Jira REST API endpoint to get the changelog entries and check who performed the change (i.e., the author) to perform the filtering.  There is the potential for timing issues in the case when other issue changes happen soon after, and thus the changelog may need to be parsed to identify the correct field change entry.

Kind regards,
Bill

[olivier.vanheste]

Hi @Bill Sheboy

Thank you, yes! We are already doing this in our external process, but as an optimalisation I was looking for a solution to not unnecessarily trigger the process.

Now as it was just an optimalisation, I'll leave it this way for now. 

Thank you for your input!

Kind regards,

Olivier