On this page
Quick answer
Every RubixKube RCA already holds what a post-mortem needs: the timeline, the root cause with evidence, the impact, contributing factors and the follow-ups. Export it as Markdown, or ask Rubix to write it into Notion and open the follow-ups as Jira issues, with your approval.
After the incident comes the paperwork: the post-mortem nobody has time to write, the tickets nobody remembers to file, the follow-ups that live in a meeting note. Most of it is copying what the investigation already found. Let Rubix do the copying.
What is already written
- Timeline from the first change to the recovery.
- Root cause with the evidence behind each step.
- Impact, current state and contributing factors.
- Tasks: the Fix and the Follow-ups, each with an owner and a status.
Three ways to get it out
- Export as Markdown from any RCA, and paste it into your post-mortem template.
- Write it into Notion. Connect Notion in Customize > Integrations. In Assist, ask "Write RCA-31 up as a post-mortem in our Incidents space", check the approval, and the page is there.
- Open the follow-ups in Jira. Connect Jira through Atlassian Rovo, then ask "Open TSK-52's follow-ups as issues in OPS". Writes follow your mode, so nothing is created without your approval in Assist.
Make it one command for the team: save a /postmortem command in Customize > Commands with your template, and anyone can run it on an incident.
It reads your history too
Connected Notion gives Rubix your runbooks, service notes and past post-mortems, so new RCAs use your team's own knowledge. Jira and Linear can also open incidents: an issue labelled incident becomes one, and resolving the issue resolves it.
Keep leadership in the loop
- Status updates and review timelines Rubix writes in chat can be saved as artifacts and shared.
- A weekly RCA digest by email, from the Automations templates (Business and Enterprise).
- A reliability report from Analytics, as a PDF.
Start free, or read Notion, Jira and reading an RCA.
Frequently asked questions
Does RubixKube write post-mortems automatically?
The RCA is written for every investigated incident. Turning it into a post-mortem page is one request: export Markdown, or ask Rubix to write it into Notion with your approval.
Can Rubix create Jira tickets?
Yes, through Atlassian Rovo. Writes follow your mode, so in Assist each ticket waits for your approval.
Does it work with Linear?
Linear issues labelled incident open incidents in RubixKube, and Rubix reads Linear for context.
Can I use my own post-mortem template?
Yes. Save it as a command in Customize > Commands, such as /postmortem, and Rubix fills it from the RCA.