Enable JSM Operations in your Jira Service Management project and navigate to Operations > Settings to generate an API integration key for receiving alerts
Create alert routing rules in JSM Operations by navigating to Operations > Alert Rules; routing rules evaluate incoming alert payloads and assign them to teams or on-call schedules based on conditions
Send a test alert to the JSM Operations inbound API endpoint to verify routing; the integration key is included in the API URL path or as a header depending on the integration type
Create on-call schedules: define rotation layers with participant users, rotation type (daily, weekly), and time restrictions via the JSM Operations schedules UI
Create an escalation policy: link schedule layers with escalation timeouts so that if the primary on-call does not acknowledge within N minutes, the alert escalates to the next layer
Verify the full flow: trigger an alert, confirm it routes correctly, acknowledge via the mobile app or API, and check that escalation does not fire prematurely
Known gotchas
JSM Operations is the migration target for standalone Opsgenie but API endpoint structures differ — do not assume Opsgenie API call patterns work identically in JSM Operations; test each integration after migration
JSM Operations alert APIs require the Atlassian cloud site context; unlike Opsgenie's standalone api.opsgenie.com, JSM Operations is scoped to your Atlassian organization and uses different authentication flows
Complex alert policy conditions that used Opsgenie's policy scripting may need to be rewritten as JSM automation rules — review Opsgenie policies for any scripted logic before migrating
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp