How to make ticket updates bidirectional when using the Jira Cloud / Opsgenie integration?

[Issy Pearson]

I'm testing out the new integration between Jira Cloud and Opsgenie and so far so good.

However there is one scenario I am having trouble with that goes as follows: When an issue is created in Jira Cloud, a subsequent alert in created in Opsgenie. Then when I update the priority of the Jira Cloud issue, the priority of the subsequent alert in Opsgenie does not update. As a user I would expect the Opsgenie alert to update its' priority based on any changes made to the Jira Cloud issue. How would I go about doing this? I'm aware of the incoming integration rules that can be setup in Opsgenie, but so far I've found that it doesn't handle this scenario.

Below are the incoming automation rules that are in place at the moment:

Any help would be much appreciated and if there are any other details I can provide, please let me know.

Thanks :)

[Mubeen Mohammed · Accepted solution]

Hello @Issy Pearson 
Thank you for contacting the Atlassian community!

The ability to update the Opsgenie alert priority when the Jira ticket priority is updated is currently possible only with the Legacy Jira integrations and currently, this option is not available on new Jira Cloud Integrations. However, we have a feature request open with our engineering team and OPSGENIE-205 is the ticket ID for your reference.

I hope the information provided is helpful.

Regards

Mubeen Mohammed

Cloud Support Engineer