Need AI Training/Help?CloudYeti.io/meet
MarkdownMe
Confluence wiki markup guide

Markdown Incident Review to Confluence

Convert a Markdown incident review into a Confluence page with timeline, impact, root cause, and follow-up actions.

Direct answer

To publish an incident review in Confluence, structure the Markdown around summary, impact, timeline, root cause, what went well, what went wrong, and follow-up actions, then convert tables, action lists, code identifiers, and warning notes into Confluence wiki markup.

Open Markdown to Confluence converter

When to use this

  • An incident retro starts as Markdown notes.
  • The final review needs to live in Confluence for support and engineering.
  • The review includes a timeline table, owners, action items, or alert names.

Steps

  1. Write a short summary and user impact first.
  2. Put events in a timeline table with time, event, and owner.
  3. Separate root cause from contributing factors.
  4. List follow-up actions with owners and due dates.
  5. Convert the Markdown to Confluence wiki markup and link the final page from the incident ticket.

Example conversion

Markdown input
## Incident review

### Summary

API errors increased after the 10:05 deploy.

### Timeline

| Time | Event | Owner |
| --- | --- | --- |
| 10:05 | Deploy completed | Engineering |
| 10:12 | `api_error_rate` alert fired | On-call |
| 10:20 | Rollback completed | On-call |

### Root cause

A required environment variable was missing from production.

### Follow-up actions

- Add deploy-time config validation
- Add runbook step for environment checks
Confluence wiki output
h2. Incident review

h3. Summary

API errors increased after the 10:05 deploy.

h3. Timeline

|| Time || Event || Owner ||
| 10:05 | Deploy completed | Engineering |
| 10:12 | {{api_error_rate}} alert fired | On-call |
| 10:20 | Rollback completed | On-call |

h3. Root cause

A required environment variable was missing from production.

h3. Follow-up actions

* Add deploy-time config validation
* Add runbook step for environment checks

Common mistakes

  • Do not mix timeline facts with root-cause interpretation.
  • Do not leave follow-up actions without owners.
  • Do not paste alert names as plain prose if inline code would make them easier to identify.

FAQ

What sections should a Confluence incident review include?
Use summary, impact, timeline, root cause, contributing factors, what went well, what went wrong, follow-up actions, owners, and links to alerts or tickets.
Should the incident timeline be a table?
Usually yes. A timeline table is easier to scan than a paragraph and converts cleanly into Confluence wiki table markup.
How should follow-up actions be formatted?
Use bullets or a table with action, owner, due date, and status. Confluence can then track the work more clearly.

Related Confluence guides

Markdown Runbook to Confluence

Convert a Markdown runbook into Confluence wiki markup with steps, warnings, code blocks, and rollback notes.

Confluence Technical Spec Template

Format a Markdown technical spec for Confluence with problem, decision, architecture, tradeoffs, and open questions.

Markdown Meeting Notes to Confluence

Turn Markdown meeting notes into a Confluence page with decisions, action items, blockers, and links.