Is there a way to disable user parameters appended as part of outbound webhook

[AA]

I wish to call an endpoint configured as part of webhook when any issue is created or updated. Unfortunately, it is failing with "Invalid Query Parameters" since the webhook appends user parameters as part of outbound URL when sending out the request. Please provide a workaround to disable these parameters.

[Andy Heinzer]

Howdy!

I understand that you want to be able to send a web hook/request to another address, but that doing so is always including parameters such as user_key and username.  We have a suggestion ticket about this over in JRACLOUD-40910.  It appears that this is by design within Jira Cloud's webhook system as documented in https://developer.atlassian.com/server/jira/platform/webhooks/

That said, I might have found a work-around here.  Normally when you create a webhook in Jira Cloud you can do this under  > System. Under Advanced, select WebHooks.  But let's try to use an alternative means of sending these requests. Instead I think you could use the automation within Jira Cloud to send this web request.

You can see in Jira Software Cloud: Automation Actions that web request is an action you can select when creating an automation rule in Jira Cloud.  If you have never setup an automation rule, then you might want to start over at Automate your Jira Cloud processes and workflows just to understand better what this does and how it works.

It appears that the web request/webhook that automation sends out uses different parameters here.  And from my own testing, it does not appear to send out user_key or username objects like the other method does.

Does this help?  Try that out and let me know the results.

Andy