JIra Auatomation rules not passing the {{issue.key}} to opsgenie for opsgenie and JIRA priority sync

[Suman Saurabh]

I have written a JIRA Automation rule follow this doc 

https://confluence.atlassian.com/jirakb/update-opsgenie-alert-priority-when-the-issue-priority-in-jira-is-changed-1236929317.html

Based on this i am trying to sync Opsgenie Alert Priority and JIRA Priority , My automation sends the URL Post suecssfully , However at the OG end its not getting changed.

 https://api.opsgenie.com/v2/alerts/{{issue.key}}/priority?identifierType=alias

Using issue.key does not works at all 

However when i replace the issue key with OG alert ID the priority get updated 

 https://api.opsgenie.com/v2/alerts/ebea4129-cf01-4bab-8622-c21b56717999-1709836064349/priority?identifierType=alias

How to use alias as a field for the web request to be sent via jira . I am already having this feild in my JIRA 

• customfield_10019: "0|i1k7zb:",
• updated: "2024-03-07T19:31:09.257+0100",
• timeoriginalestimate: null,
• customfield_10491: null,
• customfield_10492: null,
• customfield_10493: null,
• customfield_10130: null,
• description: "Issue created from Opsgenie Alert Incident number: 22155 Incident URL: https://jfrog-int.app.opsgenie.com/alert/detail/ebea4129-cf01-4bab-8622-c21b56717999-1709836064349 

[Alan Violada]

Hey Suman, Alan from the Opsgenie Support team here.

Alerts that were created via the Jira integration should have the "alias" field set to the Jira issue key, which is what would make that web request to update the priority work.

If the alert was created with an alias that does not match the Jira issue key, the web request would end up failing to be parsed.

I would recommend creating a support ticket at Contact Support so that we can take a look at your instance and logs and figure out if some configuration needs to be tweaked.

Cheers,

Alan