webhook "issuelink created", empty {issue.key} & {issue.id}

[Frédéric Pionnier]

Hello,

I created a webhook triggered by "issue link created" and I don't understand why issue.key & issue.id are empty.

In the webhooks documentation (https://developer.atlassian.com/cloud/jira/platform/modules/webhook/) the compatible context parameters are {project.id}, {project.key}, {issue.key} , {issue.id}

[Alexis Robert · Accepted solution]

Hi @Frédéric Pionnier , 

did you make sure to add a leading $ sign on your variables before ? The webhook URL should look like this :

Let me know if this helps, 

--Alexis

[Frédéric Pionnier]

Bonjour Alexis, 

Oui, j'ai bien ajouté le $ à mes variables

[Alexis Robert]

Looks like it actually does not work as it should, the same URL used for the event "issue created" does pass the issue key and issue id, but not for event "link created".

However, it does work when using the Automation for Jira webhook action, so I would advise using this instead of the Jira webhook :

You can use {{issue.key}} and {{issue.id}} in the webhook URL as shown in the screenshot.

It will give you the expected result with issue ID and key :

Let me know if this fixes your issue.

Thanks, 

Alexis

[Frédéric Pionnier]

It looks like the automatic rule is not triggered.
I think there are some broblems in the linked issues

[Alexis Robert]

I think you would need further debugging, I just tried it on my test instance and it works fine.

Did you make sure to create an issue on the INTEGR project, and link 2 issues from this project together ? With your rule configuration it will only work with this project, you would need to do a global rule if you need this on several different projects.

Or maybe you've already gone through the 500 cross-project rules allocated to you ? You can see this in the Automation menu and Usage :

[Frédéric Pionnier]

Hi Alexis,

The rule only works if my 2 issues are in the INTEGR project.

I was trying to link 2 from different projects

Thanks for your help

[Steven Gemmen]

This is now logged as a bug, in case anyone wants to vote/watch it.

https://jira.atlassian.com/browse/JRACLOUD-81512