Issue Summary

JSM Operations webhook integration with Atlassian Statuspage only supports outgoing alerts (Statuspage → JSM) — incoming/bi-directional sync is not available, unlike the deprecated OpsGenie Statuspage integration

Steps to Reproduce:

1. In JSM Operations, navigate to a team's Integrations page and add the Statuspage integration (or configure a webhook-based sync with Statuspage)

1. Configure Statuspage to send incident/component status updates to JSM via the webhook URL — confirm alerts are created in JSM when Statuspage incidents are published

1. In JSM, acknowledge or close the resulting alert and observe whether any status update is sent back to Statuspage (e.g., updating the Statuspage incident or component status)

Expected Results:
The integration should support bi-directional communication, matching the behavior of the OpsGenie Statuspage integration. Specifically:

• When an alert is acknowledged/closed in JSM Operations, the linked Statuspage incident should be updated accordingly (or at minimum, a webhook payload should be sent back to Statuspage)

• Outgoing alert actions (ack, close, add note, escalate) should be configurable to trigger a callback to Statuspage, as was possible with OpsGenie's outgoing webhook + Statuspage integration pattern

Actual Results:
The JSM Operations integration with Statuspage is inbound-only. Statuspage can create alerts in JSM, but JSM cannot send status updates or acknowledgements back to Statuspage. There is no outgoing webhook action or bi-directional sync option available for the Statuspage integration in JSM Operations.

This is a regression from OpsGenie, where customers could configure a bi-directional integration (Statuspage → OpsGenie for alert creation, and OpsGenie → Statuspage via outgoing webhook for status updates). With OpsGenie being deprecated, customers who relied on this closed-loop workflow between their status page and their alerting/on-call platform have lost that capability with no supported alternative in JSM Operations.

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior.