Migrate Statuspage to use Atlassian accounts
Learn everything you need to know to migrate you and your team to Atlassian accounts.
Once you've resolved an incident, it's always good to write a postmortem (especially for major outages). Postmortems are your opportunity to tell your customers what went wrong and what you're doing to avoid the incident in the future. Whether or not you should write a postmortem really depends on a combination of how important your product is to your customers and how severe the incident was.
To write a successful postmortem, you should do three things:
Apologize
Show understanding of what happened
Explain your remediation plan
Postmortems can only be created once you resolve an incident.
Click the Incidents tab on the incidents page.
Select Write postmortem on the Incidents page next to a resolved incident.
Type up your postmortem report in the text field. While writing your content, drafts are automatically saved so that you can review content before posting.
Click Publish when you're satisfied with your draft.
Postmortems are created using our editor, which has some support for Github Flavored Markdown (GFM) style syntax. GFM is an extended version of basic markdown syntax.
Here's what a published postmortem looks like:
We have set a default size and margin that we believe works really well and results in an easy-to-read postmortem.
As always, you can override the styles that affect your postmortems by using the Custom CSS feature.
Was this helpful?