[{"data":1,"prerenderedAt":70},["Reactive",2],{"blog-post-markdown-to-jira-wiki-markup-guide":3},{"slug":4,"title":5,"description":6,"excerpt":7,"date":8,"category":9,"author":10,"keywords":11,"readingMinutes":12,"html":13,"headings":14,"tools":55,"related":59},"markdown-to-jira-wiki-markup-guide","Markdown to Jira Wiki Markup: The Complete Conversion Guide","Converting Markdown to Jira wiki markup? This guide covers every syntax difference, explains how Jira Cloud vs Server handle formatting, and shows you how to automate the conversion.","If you write documentation in Markdown but need to post it to Jira, you've hit the wall: Jira has its own wiki markup language, and pasting Markdown directly doesn't work — or doesn't work…","2026-06-19","workflows","Matt Rathbone","markdown to jira, jira wiki markup, jira markdown conversion, atlassian wiki markup, jira formatting, jira text formatting, markdown jira syntax, jira cloud markdown",7,"\u003Cp>If you write documentation in Markdown but need to post it to Jira, you've hit the wall: Jira has its own wiki markup language, and pasting Markdown directly doesn't work — or doesn't work reliably. The results depend on which version of Jira you're using, which project type, and whether your admin has enabled anything.\u003C/p>\n\u003Cp>This guide maps out every syntax difference, explains what actually works in each Jira context, and shows you how to do the conversion reliably.\u003C/p>\n\u003Ch2 id=\"why-jira-doesnt-just-support-markdown\">Why Jira Doesn't Just Support Markdown\u003C/h2>\n\u003Cp>Jira's text formatting language (wiki markup) predates widespread Markdown adoption. It uses its own syntax that's close to — but not the same as — Markdown. In Cloud and Server, Atlassian has gradually added Markdown-like support, but it's incomplete and inconsistent across project types.\u003C/p>\n\u003Cp>The result: the same pasted content renders differently in:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Jira Data Center/Server\u003C/strong> — pure wiki markup, very little native Markdown support\u003C/li>\n\u003Cli>\u003Cstrong>Jira Cloud (classic projects)\u003C/strong> — hybrid editor, some Markdown autocomplete on the Visual side\u003C/li>\n\u003Cli>\u003Cstrong>Jira Cloud (next-gen / team-managed projects)\u003C/strong> — rich text editor, accepts some Markdown on paste, no wiki markup at all\u003C/li>\n\u003C/ul>\n\u003Cp>This distinction matters more than anything else in this guide.\u003C/p>\n\u003Ch2 id=\"which-jira-version-are-you-using\">Which Jira Version Are You Using?\u003C/h2>\n\u003Cp>Before converting anything, identify your environment:\u003C/p>\n\u003Cdiv class=\"table-responsive\">\u003Ctable class=\"table\">\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Jira type\u003C/th>\n\u003Cth>How to tell\u003C/th>\n\u003Cth>Markdown support\u003C/th>\n\u003Cth>Wiki markup\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Data Center / Server\u003C/td>\n\u003Ctd>Self-hosted, URL isn't atlassian.net\u003C/td>\n\u003Ctd>None\u003C/td>\n\u003Ctd>Full\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Cloud — classic project\u003C/td>\n\u003Ctd>atlassian.net domain, Text/Visual editor toggle\u003C/td>\n\u003Ctd>Partial (autocomplete)\u003C/td>\n\u003Ctd>Full\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Cloud — next-gen project\u003C/td>\n\u003Ctd>atlassian.net, no "Text" tab in editor\u003C/td>\n\u003Ctd>Paste-in only\u003C/td>\n\u003Ctd>None\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\u003C/div>\n\u003Cp>\u003Cstrong>For Data Center/Server and Cloud classic\u003C/strong>: Convert to wiki markup before pasting.\u003Cbr>\u003Cstrong>For Cloud next-gen\u003C/strong>: Paste Markdown directly into the rich text editor; basic formatting survives (bold, italic, lists), but tables and code blocks usually break.\u003C/p>\n\u003Ch2 id=\"the-complete-markdown--jira-wiki-markup-conversion-table\">The Complete Markdown → Jira Wiki Markup Conversion Table\u003C/h2>\n\u003Cdiv class=\"table-responsive\">\u003Ctable class=\"table\">\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Element\u003C/th>\n\u003Cth>Markdown\u003C/th>\n\u003Cth>Jira Wiki Markup\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Heading 1\u003C/td>\n\u003Ctd>\u003Ccode># Heading\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>h1. Heading\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Heading 2\u003C/td>\n\u003Ctd>\u003Ccode>## Heading\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>h2. Heading\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Heading 3\u003C/td>\n\u003Ctd>\u003Ccode>### Heading\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>h3. Heading\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Bold\u003C/td>\n\u003Ctd>\u003Ccode>**text**\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>*text*\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Italic\u003C/td>\n\u003Ctd>\u003Ccode>*text*\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>_text_\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Strikethrough\u003C/td>\n\u003Ctd>\u003Ccode>~~text~~\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>-text-\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Inline code\u003C/td>\n\u003Ctd>\u003Ccode>`code`\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>{{code}}\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Code block\u003C/td>\n\u003Ctd>\u003Ccode>```lang\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>{code:lang}...{code}\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Blockquote\u003C/td>\n\u003Ctd>\u003Ccode>> text\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>{quote}text{quote}\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Link\u003C/td>\n\u003Ctd>\u003Ccode>[text](url)\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>[text|url]\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Image\u003C/td>\n\u003Ctd>\u003Ccode>![alt](url)\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>!url!\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Unordered list\u003C/td>\n\u003Ctd>\u003Ccode>- item\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>* item\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Ordered list\u003C/td>\n\u003Ctd>\u003Ccode>1. item\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode># item\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Horizontal rule\u003C/td>\n\u003Ctd>\u003Ccode>---\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>----\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Table header\u003C/td>\n\u003Ctd>\u003Ccode>| head |\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>|| head ||\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Table cell\u003C/td>\n\u003Ctd>\u003Ccode>| cell |\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>| cell |\u003C/code>\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\u003C/div>\n\u003Cp>The differences look subtle but they trip people up constantly — especially \u003Ccode>*bold*\u003C/code> becoming \u003Ccode>_italic_\u003C/code> in Jira (the opposite of how Markdown works).\u003C/p>\n\u003Ch2 id=\"converting-code-blocks\">Converting Code Blocks\u003C/h2>\n\u003Cp>This is where things get interesting. Jira uses macro syntax for code blocks:\u003C/p>\n\u003Cp>\u003Cstrong>Markdown:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>```javascript\nconst greeting = 'Hello, world!';\nconsole.log(greeting);\n```\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Jira wiki markup:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>{code:javascript}\nconst greeting = 'Hello, world!';\nconsole.log(greeting);\n{code}\n\u003C/code>\u003C/pre>\u003Cp>The language name goes as a parameter to the \u003Ccode>{code}\u003C/code> macro. Supported languages include \u003Ccode>java\u003C/code>, \u003Ccode>javascript\u003C/code>, \u003Ccode>python\u003C/code>, \u003Ccode>sql\u003C/code>, \u003Ccode>xml\u003C/code>, \u003Ccode>html\u003C/code>, \u003Ccode>css\u003C/code>, \u003Ccode>bash\u003C/code>, \u003Ccode>ruby\u003C/code>, \u003Ccode>php\u003C/code>, and dozens more. If you omit the language, the block renders as plain preformatted text.\u003C/p>\n\u003Cp>For inline code, Markdown uses backticks while Jira uses \u003Ccode>{{double curly braces}}\u003C/code>:\u003C/p>\n\u003Cdiv class=\"table-responsive\">\u003Ctable class=\"table\">\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Markdown\u003C/th>\n\u003Cth>Jira\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Ccode>`variable`\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>{{variable}}\u003C/code>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>`npm install`\u003C/code>\u003C/td>\n\u003Ctd>\u003Ccode>{{npm install}}\u003C/code>\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\u003C/div>\n\u003Ch2 id=\"converting-tables\">Converting Tables\u003C/h2>\n\u003Cp>Tables are one of the clearest differences. Markdown uses a \u003Ccode>---\u003C/code> separator row to mark headers; Jira uses double pipes (\u003Ccode>||\u003C/code>) for header cells and single pipes (\u003Ccode>|\u003C/code>) for body cells.\u003C/p>\n\u003Cp>\u003Cstrong>Markdown:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">| Name | Role | Access |\n|------|------|--------|\n| Alice | Admin | Full |\n| Bob | Developer | Read/Write |\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Jira wiki markup:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>|| Name || Role || Access ||\n| Alice | Admin | Full |\n| Bob | Developer | Read/Write |\n\u003C/code>\u003C/pre>\u003Cp>There's no separator row in Jira. The header is inferred purely from whether the row uses \u003Ccode>||\u003C/code> or \u003Ccode>|\u003C/code>.\u003C/p>\n\u003Cp>What Jira wiki markup tables \u003Cstrong>don't\u003C/strong> support:\u003C/p>\n\u003Cul>\n\u003Cli>Column alignment (\u003Ccode>:---:\u003C/code> / \u003Ccode>---:\u003C/code> syntax is ignored)\u003C/li>\n\u003Cli>Multi-line cells\u003C/li>\n\u003Cli>Colspan or rowspan (requires the HTML macro)\u003C/li>\n\u003Cli>Cell background colours (without the HTML macro)\u003C/li>\n\u003C/ul>\n\u003Cp>If you need any of those, convert to HTML using our \u003Ca href=\"/tools/markdown-to-html\">Markdown to HTML tool\u003C/a> and paste using Jira's HTML macro.\u003C/p>\n\u003Ch2 id=\"converting-lists-and-nesting\">Converting Lists and Nesting\u003C/h2>\n\u003Cp>Both Markdown and Jira use \u003Ccode>*\u003C/code> and \u003Ccode>#\u003C/code> for lists, but Jira doesn't use indentation for nesting — it uses repeated characters:\u003C/p>\n\u003Cp>\u003Cstrong>Markdown (nested):\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">\u003Cspan class=\"hljs-bullet\">-\u003C/span> Item 1\n\u003Cspan class=\"hljs-bullet\">  -\u003C/span> Nested item\n\u003Cspan class=\"hljs-bullet\">  -\u003C/span> Another nested\n\u003Cspan class=\"hljs-bullet\">-\u003C/span> Item 2\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Jira wiki markup (nested):\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>* Item 1\n** Nested item\n** Another nested\n* Item 2\n\u003C/code>\u003C/pre>\u003Cp>Each additional level of nesting repeats the character. Two levels deep is \u003Ccode>**\u003C/code>, three is \u003Ccode>***\u003C/code>. Indentation in Markdown doesn't translate automatically — you need to count nesting depth and repeat accordingly.\u003C/p>\n\u003Cp>Mixed ordered/unordered nested lists work the same way:\u003C/p>\n\u003Cpre>\u003Ccode>* First level unordered\n*# Second level ordered under unordered\n*#* Third level unordered under ordered under unordered\n\u003C/code>\u003C/pre>\u003Ch2 id=\"converting-blockquotes\">Converting Blockquotes\u003C/h2>\n\u003Cp>Markdown blockquotes use \u003Ccode>>\u003C/code> prefixes. Jira uses a \u003Ccode>{quote}\u003C/code> macro:\u003C/p>\n\u003Cp>\u003Cstrong>Markdown:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode class=\"hljs language-markdown\">\u003Cspan class=\"hljs-quote\">> This is a quoted passage from the requirements document.\u003C/span>\n\u003Cspan class=\"hljs-quote\">> It can span multiple lines.\u003C/span>\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Jira:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>{quote}\nThis is a quoted passage from the requirements document.\nIt can span multiple lines.\n{quote}\n\u003C/code>\u003C/pre>\u003Cp>Nested blockquotes (\u003Ccode>> > text\u003C/code>) aren't directly supported in Jira wiki markup — you get one level.\u003C/p>\n\u003Ch2 id=\"jira-only-macros\">Jira-Only Macros\u003C/h2>\n\u003Cp>Wiki markup has macros that have no Markdown equivalent. Knowing these is useful when you're writing content that will only ever live in Jira:\u003C/p>\n\u003Cp>\u003Cstrong>Colour text:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>{color:red}This text is red.{color}\n{color:#0052CC}This text is Jira blue.{color}\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Info/note/warning/tip panels:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>{info}This is an informational note.{info}\n{warning}Caution: this action cannot be undone.{warning}\n{note}Note: configuration required.{note}\n{tip}Pro tip: use keyboard shortcuts.{tip}\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Panel with title and styling:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>{panel:title=Important|borderColor=#ddd|titleBGColor=#f0f0f0}\nPanel content here.\n{panel}\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>No-format block\u003C/strong> (preformatted text, no syntax highlighting):\u003C/p>\n\u003Cpre>\u003Ccode>{noformat}\nPlain text that should appear as-is.\nStack traces, log output, etc.\n{noformat}\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Jira issue link:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>{jira:KEY-123}\n\u003C/code>\u003C/pre>\u003Cp>These macros render as styled components in Jira but have no Markdown equivalent. If you're round-tripping content (Jira → Markdown → Jira), you'll lose these macros on the Markdown side.\u003C/p>\n\u003Ch2 id=\"what-doesnt-convert-cleanly\">What Doesn't Convert Cleanly\u003C/h2>\n\u003Cp>Some Markdown features have no wiki markup equivalent:\u003C/p>\n\u003Cdiv class=\"table-responsive\">\u003Ctable class=\"table\">\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Markdown feature\u003C/th>\n\u003Cth>In Jira\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Footnotes \u003Ccode>[^1]\u003C/code>\u003C/td>\n\u003Ctd>Not supported\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Definition lists\u003C/td>\n\u003Ctd>Not supported\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Task lists \u003Ccode>- [x]\u003C/code>\u003C/td>\n\u003Ctd>Use \u003Ccode>(/)\u003C/code> and \u003Ccode>(x)\u003C/code> emoji for checkmarks; not linked to issue checklists\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Custom heading IDs \u003Ccode>{#anchor}\u003C/code>\u003C/td>\n\u003Ctd>Not supported\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Strikethrough in tables\u003C/td>\n\u003Ctd>Works, but renders inconsistently\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>HTML elements\u003C/td>\n\u003Ctd>Use \u003Ccode>{html}\u003C/code> macro (Cloud only, off by default)\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Fenced code inside blockquotes\u003C/td>\n\u003Ctd>Loses code formatting\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\u003C/div>\n\u003Cp>For task lists specifically: Jira has a built-in checklist feature in Cloud, but it's separate from the text editor and not accessible via wiki markup.\u003C/p>\n\u003Ch2 id=\"using-our-markdown-to-jira-converter\">Using Our Markdown to Jira Converter\u003C/h2>\n\u003Cp>The fastest way to convert is with our \u003Ca href=\"/tools/markdown-to-jira\">Markdown to Jira tool\u003C/a>. Paste your Markdown on the left, get Jira wiki markup on the right in real time.\u003C/p>\n\u003Cp>The converter handles:\u003C/p>\n\u003Cul>\n\u003Cli>All heading levels (h1–h6)\u003C/li>\n\u003Cli>Bold, italic, strikethrough\u003C/li>\n\u003Cli>Inline code and fenced code blocks with language tags preserved\u003C/li>\n\u003Cli>Tables with header row conversion (\u003Ccode>||\u003C/code> vs \u003Ccode>|\u003C/code>)\u003C/li>\n\u003Cli>Ordered and unordered lists with nesting depth\u003C/li>\n\u003Cli>Blockquotes\u003C/li>\n\u003Cli>Links and images\u003C/li>\n\u003Cli>Horizontal rules\u003C/li>\n\u003C/ul>\n\u003Cp>It's particularly useful when you have long documentation pages to migrate, or you're regularly posting Markdown from a blog or docs tool into Jira issues.\u003C/p>\n\u003Ch2 id=\"which-editor-mode-to-use\">Which Editor Mode to Use\u003C/h2>\n\u003Cp>For \u003Cstrong>Data Center/Server\u003C/strong>: always use wiki markup. It's the native format. Click the \u003Ccode>Text\u003C/code> tab in the issue editor, paste wiki markup, done.\u003C/p>\n\u003Cp>For \u003Cstrong>Cloud classic projects\u003C/strong>: the \u003Ccode>Text\u003C/code> tab accepts wiki markup directly. The \u003Ccode>Visual\u003C/code> tab is WYSIWYG. If you're using the REST API to create or update issues, the \u003Ccode>description\u003C/code> field accepts wiki markup for classic projects.\u003C/p>\n\u003Cp>For \u003Cstrong>Cloud next-gen (team-managed) projects\u003C/strong>: there's no \u003Ccode>Text\u003C/code> tab. The editor is rich text only. For basic formatting, paste Markdown and let it auto-convert. For tables and code blocks, paste HTML using your browser's paste shortcut after converting with our \u003Ca href=\"/tools/markdown-to-html\">Markdown to HTML tool\u003C/a>.\u003C/p>\n\u003Cp>For \u003Cstrong>Jira Cloud API (creating issues programmatically)\u003C/strong>: Cloud's REST API v3 uses Atlassian Document Format (ADF), not wiki markup. You can't paste wiki markup into the \u003Ccode>description\u003C/code> field via the API on Cloud — you need to build an ADF document. Wiki markup is only supported in the Server/DC REST API. This is a significant pain point for teams automating Jira content creation.\u003C/p>\n\u003Ch2 id=\"jira-wiki-markup-reference-cheat-sheet\">Jira Wiki Markup Reference Cheat Sheet\u003C/h2>\n\u003Cp>Quick reference for the conversions you'll use most often:\u003C/p>\n\u003Cp>\u003Cstrong>Text formatting:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>*bold*           _italic_         -strikethrough-\n+underline+      ^superscript^    ~subscript~\n??citation??     {color:red}text{color}\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Structure:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>h1. Heading 1          h2. Heading 2          h3. Heading 3\n----                   (horizontal rule)\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Lists:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>* Bullet             # Numbered\n** Nested bullet     ## Nested numbered\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Links and media:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>[Link text|https://example.com]\n[Page title|PAGE TITLE]     (Confluence-style, not standard Jira)\n!image.png!                 !image.png|thumbnail!\n^file.pdf                   (attachment link)\n\u003C/code>\u003C/pre>\u003Cp>\u003Cstrong>Macros:\u003C/strong>\u003C/p>\n\u003Cpre>\u003Ccode>{code:java}code here{code}\n{{inline code}}\n{quote}quoted text{quote}\n{noformat}plain text{noformat}\n\u003C/code>\u003C/pre>\u003Ch2 id=\"related-posts-and-tools\">Related Posts and Tools\u003C/h2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"/tools/markdown-to-jira\">Markdown to Jira converter\u003C/a> — real-time conversion, no signup required\u003C/li>\n\u003Cli>\u003Ca href=\"/tools/markdown-to-confluence\">Markdown to Confluence\u003C/a> — Confluence uses similar wiki markup; see our \u003Ca href=\"/blog/markdown-in-confluence-what-works\">Confluence guide\u003C/a> for the differences\u003C/li>\n\u003Cli>\u003Ca href=\"/tools/markdown-to-html\">Markdown to HTML\u003C/a> — for Jira Cloud next-gen where wiki markup isn't available\u003C/li>\n\u003Cli>\u003Ca href=\"/blog/markdown-platform-compatibility-guide\">Markdown Across Platforms\u003C/a> — how Markdown behaves in each major platform\u003C/li>\n\u003Cli>\u003Ca href=\"/blog/markdown-for-technical-writers-docs-as-code\">Markdown for Technical Writers\u003C/a> — if you're managing docs alongside Jira tickets\u003C/li>\n\u003C/ul>\n",[15,19,22,25,28,31,34,37,40,43,46,49,52],{"id":16,"text":17,"level":18},"why-jira-doesnt-just-support-markdown","Why Jira Doesn't Just Support Markdown",2,{"id":20,"text":21,"level":18},"which-jira-version-are-you-using","Which Jira Version Are You Using?",{"id":23,"text":24,"level":18},"the-complete-markdown--jira-wiki-markup-conversion-table","The Complete Markdown → Jira Wiki Markup Conversion Table",{"id":26,"text":27,"level":18},"converting-code-blocks","Converting Code Blocks",{"id":29,"text":30,"level":18},"converting-tables","Converting Tables",{"id":32,"text":33,"level":18},"converting-lists-and-nesting","Converting Lists and Nesting",{"id":35,"text":36,"level":18},"converting-blockquotes","Converting Blockquotes",{"id":38,"text":39,"level":18},"jira-only-macros","Jira-Only Macros",{"id":41,"text":42,"level":18},"what-doesnt-convert-cleanly","What Doesn't Convert Cleanly",{"id":44,"text":45,"level":18},"using-our-markdown-to-jira-converter","Using Our Markdown to Jira Converter",{"id":47,"text":48,"level":18},"which-editor-mode-to-use","Which Editor Mode to Use",{"id":50,"text":51,"level":18},"jira-wiki-markup-reference-cheat-sheet","Jira Wiki Markup Reference Cheat Sheet",{"id":53,"text":54,"level":18},"related-posts-and-tools","Related Posts and Tools",[56,57,58],"markdown-to-html","markdown-to-jira","markdown-to-confluence",[60],{"slug":61,"title":62,"description":63,"excerpt":64,"date":65,"category":66,"author":67,"keywords":68,"readingMinutes":69},"mermaid-diagrams-in-slack-jira-confluence-word-email","Mermaid Diagrams in Slack, Jira, Confluence, Word, and Email: The Static Export Workaround","Mermaid renders live on GitHub, GitLab, and Obsidian — and nowhere else most teams actually work. Here's how to get a Mermaid diagram into Slack, Jira, Confluence, Word, and email as a static image instead.","Our complete guide to diagrams and flowcharts in Markdown covers Mermaid syntax in depth — flowcharts, sequence diagrams, ER diagrams, the works. What it doesn't dwell on is a problem that shows…","2026-09-18","Tutorial","Matthew Rathbone","mermaid diagrams slack, mermaid confluence, mermaid jira, mermaid word document, mermaid email, export mermaid to png, export mermaid to svg",6,1792184946857]