Migrate from Jira Service Management Operations
Preview and migrate accessible JSM Operations teams, schedules, heartbeats, and escalations.
On this page
Current coverage
Provide your Atlassian account email, API token, Cloud ID and *.atlassian.net site. Optionally provide the Atlassian Organization ID to include team membership. HowlOps only performs read operations and never stores the token. Atlassian models the membership lookup as a read-only POST; HowlOps never calls the adjacent add/remove endpoints.
| JSM Operations | HowlOps | Important limits |
|---|---|---|
| Team | Team | With Organization ID, members are read through Atlassian's organization-scoped Teams Members API and missing people can use the normal invitation flow. Without it, the team imports as an empty shell. Team-role definitions/rights are inventoried, but the read API does not expose member-to-role assignments; team-admin recipients therefore fail closed. |
| Schedule rotations + ongoing/future overrides | Schedule layers + layer-scoped or whole-schedule overrides | One-day/one-week user rotations, finite rotation end boundaries and resolvable user overrides import. Multi-period turns and team/escalation participants are skipped; a time-restricted schedule fails closed rather than becoming 24/7. |
| Heartbeat | Team-owned heartbeat | Enabled heartbeats retain their JSM team. Disabled heartbeats remain inactive and are not imported. |
| Escalation | Escalation policy | Supported user and schedule recipients import. Team-member recipients import only after membership was read successfully; team-admin recipients fail closed because Atlassian does not expose member roles. Repeat reset/auto-close flags are disclosed but cannot yet be reproduced. |
| Compatible routing rule | Alert-routing rule | Exact AND/equality subset targeting an escalation policy or schedule. A direct schedule target becomes an equivalent private one-step policy. none, time restrictions and incompatible expressions fail closed. |
| Global/team alert and notification policy | Disabled reviewed provider-neutral policy | Supported typed filters/actions import disabled. Complex/time-based behavior stays fail-closed. |
JSM services are ownership/catalog context and do not themselves change alert routing. The documented Operations REST token flow has no service-catalog list endpoint, so the importer does not guess services, owners or service-to-policy links. Past overrides, routing rules outside the exact shared subset, complex policy behavior, integrations and alert/incident history are not imported yet. Global and team policy detail is fetched before mapping; no list summary is treated as complete behavior. Imported policies remain disabled until an owner/admin reviews a dry-run trace. The preview must not be treated as complete when Atlassian permissions hide users or objects.
Missing users are invited only when selected; pending team, rotation, and override assignments remain authentication-inert and activate after invitation acceptance. Pending assignments do not expire automatically. A re-run distinguishes unchanged, source-changed and legacy drift states and preserves the linked HowlOps object for review. Reconnect ChatOps and all provider credentials manually, validate the on-call timeline, then perform a reviewed parallel cutover.
Was this page helpful?