Converter Tools
Markdown to Jira Converter
Convert Markdown to Jira wiki markup and back in your browser. Headings, bold, italic, links, tables, code blocks, and lists, with a syntax cheat sheet.
Rewrite CommonMark or GitHub-Flavored Markdown into Jira wiki markup that pastes correctly into a Jira description, comment, or epic body.
Headings become h1. through h6., **bold** becomes *bold*, [label](url) becomes [label|url], GFM tables become ||header|| rows, and fenced code blocks become {code:lang} blocks.
Syntax mapping
Every construct, side by side.
| Construct | Markdown | Jira |
|---|---|---|
| Bold | **bold** | *bold* |
| Italic | *italic* or _italic_ | _italic_ |
| Strike | ~~strike~~ | -strike- |
| Inline code | `code` | {{code}} |
| Code block | ```lang ... ``` | {code:lang} ... {code} |
| Heading H1 | # Heading | h1. Heading |
| Heading H6 | ###### Heading | h6. Heading |
| Link | [label](url) | [label|url] |
| Bare URL | https://x.test | [https://x.test] |
| Image |  | !url|alt=alt! |
| Quote (line) | > line | bq. line |
| Quote (multi) | > line 1\n> line 2 | {quote} ... {quote} |
| Bullet | - item | * item |
| Nested bullet | - nested | ** nested |
| Numbered | 1. item | # item |
| HR | --- | ---- |
| Table header | | a | b | | ||a||b|| |
| Table row | | c | d | | |c|d| |
Jira quirks worth knowing
Things to remember when you paste into Jira Cloud or Data Center.
- Jira bold uses a single asterisk (*bold*), not two. Pasting double asterisks leaves the stars visible.
- Strikethrough uses a single hyphen (-strike-) and only renders when both sides land on word boundaries. The converter skips strikethrough when the text starts or ends with a dash.
- Inline code uses double curly braces ({{code}}). The contents are never reformatted.
- Fenced code blocks become {code:lang} when a language hint is present and {code} otherwise. The Atlassian {noformat} block is read as a plain code block in the reverse direction.
- Tables emit ||header|| rows and |cell| rows. The Markdown alignment row is dropped because Jira tables have no alignment syntax.
- Bullets use * for level one and ** for level two (up to four levels). Numbered lists use # per level.
- User mentions like [~username] are preserved when converting in either direction so cc-style references survive the round trip.
How to use
- Pick the direction: Markdown to Jira to paste a Jira description, or Jira to Markdown to pull a description back out for a README or doc.
- Paste your text into the left panel, or click one of the sample buttons to load a typical bug report, release notes, or spec layout.
- Read the converted output on the right and use the syntax cheat sheet card below for any rule you want to double-check.
- Click Copy to copy the result to your clipboard, then paste it into the Jira description or comment box, or your Markdown editor.
- Use Swap output into input to chain a round trip and confirm the conversion is lossless for your content.
About this tool
Markdown to Jira Converter rewrites CommonMark and GitHub-Flavored Markdown into Jira wiki markup, the dialect Jira Cloud and Jira Data Center accept inside issue descriptions, comments, and epic bodies. It also converts in the reverse direction so you can pull a Jira description out of a ticket, edit it as Markdown in your README or Linear issue, and put it back. Every construct is mapped: ATX and setext headings become h1. through h6., bold (**text** or __text__) becomes Jira's single-asterisk bold (*text*), italic becomes _text_, strikethrough becomes -text- (skipped when the inner text starts or ends with a dash so phrases like off-the-shelf are not damaged), inline code becomes {{code}}, fenced code blocks become {code:lang} or {code} blocks with the language hint preserved, links become [label|url], bare URLs become [url], images become !url|alt=alt!, GFM tables become ||header|| header rows and |cell| data rows, blockquotes use the short bq. form for a single line and {quote}...{quote} for multi-line, horizontal rules become ----, ordered lists use # per level, and unordered lists use * per level with task list checkboxes mapped to (/) for done and (x) for open. Reference-style Markdown links are resolved inline, since Jira has no reference syntax. The reverse direction is the inverse of the same table, including {noformat} blocks read back as code fences and Jira user mentions like [~username] preserved as @username so cc-style references survive the round trip. A built-in side-by-side syntax cheat sheet keeps every rule visible while you edit. Three samples cover the most common ticket shapes: a bug report with steps to reproduce and a code block, release notes with a pricing table, and a spec or task with checkbox acceptance criteria. The conversion is deterministic and runs entirely in your browser using a hand-written line-by-line parser with a token-protection pass so emphasis cannot double-process the contents of links or code. Useful when copying notes from GitHub, Notion, Linear, Obsidian, or VS Code into a Jira ticket, or pulling a Jira description out for a doc, README, or follow-up incident report. Nothing is uploaded, so private ticket content stays on your device.
Free to use. Works in your browser. No signup, no login.
Related tools
You may also like
Markdown to Slack Converter
Two-way converter between Markdown and Slack's mrkdwn message format.
Open tool
ConverterMarkdown to HTML Converter
Convert Markdown to clean HTML with a live preview and copy button.
Open tool
TextMarkdown to Plain Text
Remove Markdown formatting and get clean readable plain text.
Open tool
ConverterHTML to Markdown Converter
Convert HTML to GFM Markdown with tables, code, and reference links.
Open tool
TextMarkdown Editor
Live markdown editor with toolbar, preview, table of contents, and .md or .html download.
Open tool
TextMarkdown TOC Generator
Build a GitHub-style Markdown table of contents from any document.
Open tool