Automate Rootly postmortems with Jira action item sync and template enforcement via the Rootly API
domain: docs.rootly.com/api-reference · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Retrieve available postmortem templates: GET /v1/post_mortem_templates to list templates and their IDs; note the ID of the standard template to enforce across incidents
Create a postmortem for a resolved incident: POST /v1/post_mortems with data.attributes.incident_id and data.attributes.post_mortem_template_id to apply a specific template
Fetch action items from the postmortem: GET /v1/incidents/{id}/action_items to retrieve follow-up tasks generated during the incident review
Create Jira issues for each action item: POST to the Jira REST API /rest/api/3/issue with the action item title and link back to the Rootly incident URL in the description; store the Jira issue key
Update the Rootly action item with the external Jira reference: PATCH /v1/action_items/{id} with data.attributes.external_link set to the Jira issue URL to establish bidirectional traceability
Poll or webhook: configure a Rootly webhook for the action_item.updated event to sync Jira status changes back to Rootly, or run a nightly reconciliation script using GET /v1/action_items with filter[status]
Known gotchas
Rootly's Jira integration (configured in UI under Integrations > Jira) can automate Jira ticket creation without custom code — use the API only when you need custom field mapping or multi-project routing not supported by the native integration
Postmortem templates define required sections but do not enforce mandatory completion via the API; add a workflow automation in Rootly to block incident closure until the postmortem status is completed
The Rootly API uses JSON:API filtering syntax: filter[incident_id]={id} — standard query parameters like ?incident_id= are not recognized and return all records
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?