Issue Summary

When using a variable such as ${issue.key} in a webhook endpoint, the issue link events are triggered without the variable being resolved.

For example, a webhook triggered by ABC-123, with a URL of:

https://webhook-tester/${issue.key} resolves to https://webhook-tester/ABC-123

However, this not happening.

Example:

Issue Link Webhook Failed

Posting to web hook at 'https://webhook-tester/?user_id=admin&user_key=admin', body is: {"timestamp":1744814291867,"webhookEvent":"issuelink_created","issueLink":
.....
Error - 405 when posting to web hook at 'https://webhook-tester/'

Comment Add Webhook Succeeded

Posting to web hook at 'https://webhook-tester/ABC-123?user_id=admin&user_key=admin', body is: {"timestamp":1744814079460,"webhookEvent":"comment_created","comment"...
.....
WebHook successfully sent

Issue link payload is being sent to endpoint https://webhook-tester/?user_id=admin&user_key=admin' instead of https://webhook-tester/abc-123?user_id=admin&user_key=admin'

Steps to Reproduce

1. Create an issue link created/updated/deleted webhook with a webhook URL containing a variable such as ${issue.key}. 
2. Trigger the webhook events
3. Configure and repeat the same steps for another webhook event type such as "comment added"

Expected Results

Webhooks are delivered.

Actual Results

Issue link webhook event fails to deliver due to incorrect endpoint.

Workaround

Automation for Jira can send a payload for issue link events to a dynamic URL using smart values. Example with issue key: