Customers are reporting that after transitioning to JSM operations, automation rules that use Opsgenie Alerts REST API to update alert priority are no longer working. Attempted to switch to JSM Ops REST API, failed as well. The automation rule is supposed to update the Opsgenie priorities that kicked off on-call forwarding, routing, and escalations. In Opsgenie, this rule used to work flawlessly.

Steps to reproduce.

In JSM Incident Management project.

• Create an Incident ticket.
• Update the incident ticket, for example from P3 to P2 priorities

Automation rule

• Create a rule with a Field value change trigger and set the field to priority.
• In the IF block, set the priority and issue type.
• Then update alert priority by using the REST API PUT command, "Send web requests".

Eg. 

• api.atlassian.com/jsm/ops/api/{cloudId}/v1/alerts/{issue_key}/priority?identifierType=Alias

Expected:

• The Alert priority is updated via the automation rule.

Actual:

• The automation rule fails and Alert priority is not updated by automation.