How to use the markdown to jira converter
- Paste your Markdown text into the input area.
- The tool automatically converts headings, lists, emphasis, code blocks, links and tables into Jira wiki markup.
- Raw HTML is not interpreted and is copied as plain text.
- Copy the generated Jira markup from the output area and paste it directly into a Jira issue description, comment or Confluence page.
Supported Markdown Subset
This markdown to jira converter processes a practical subset of CommonMark that covers most documentation needs. The supported elements include:
- Headings: ATX style (
# H1through###### H6) - Emphasis: bold (
**text**or__text__) and italic (*text*or_text_) - Inline code: backticks (
`code`) - Fenced code blocks: triple backticks with optional language tag
- Links: standard syntax (
[text](url)) - Images: standard syntax (
) - Unordered lists: lines starting with
-,*or+ - Ordered lists: lines starting with digits followed by a period
- Blockquotes: lines starting with
> - Horizontal rules: three or more hyphens, asterisks or underscores
- Tables: pipe-delimited rows with a separator line
Elements outside this subset, such as footnotes or definition lists, are passed through as plain text.
How the Conversion Works
The conversion happens in two main phases. First, the input is split into blocks to handle multi-line structures like fenced code blocks, lists and tables. Fenced code blocks are extracted early so their contents are not processed as inline formatting. Then each block is classified and translated into the corresponding Jira wiki syntax.
For example, a Markdown heading ## My Title becomes h2. My Title. An unordered list item - Apple becomes * Apple, while an ordered item 1. First becomes # First. Inline replacements run last on paragraph text, converting **bold** to *bold* and *italic* to _italic_.
The Markdown is parsed with CommonMark rules first. Characters that would start Jira markup (curly braces, square brackets, pipes and emphasis characters that touch a word) are escaped with a backslash, and raw HTML is copied as plain text. This ensures that pasting untrusted content into Jira will not execute scripts or break the layout.
Markdown vs Jira Syntax Reference
Jira uses its own wiki markup language, which differs significantly from Markdown. Here is a quick reference table showing how common elements translate:
| Element | Markdown | Jira Wiki |
|---|---|---|
| Heading 1 | # Text | h1. Text |
| Bold | **Text** | *Text* |
| Italic | *Text* | _Text_ |
| Link | [Text](url) | [Text|url] |
| Image |  | !url! |
| Unordered list | - Item | * Item |
| Ordered list | 1. Item | # Item |
| Inline code | `code` | {{code}} |
| Code block | ```lang | {code:lang} |
| Blockquote | > text | {quote}text{quote} |
Understanding these differences makes it clear why a dedicated converter saves time when moving documentation between platforms.
Handling Tables and Code Blocks
Tables require special attention because Jira uses double pipes for header cells and single pipes for data cells. A Markdown table like this:
| Name | Role ||---|---|| Alice | Dev |
is converted to:
||Name||Role|||Alice|Dev|
The separator row (the one with dashes) is discarded during conversion since Jira infers headers from the double-pipe syntax.
Fenced code blocks preserve their internal whitespace exactly. If a language identifier is provided after the opening backticks, it is appended to the Jira {code} macro as {code:language}. Everything inside the fences is treated as literal text, meaning no inline formatting conversions are applied within code blocks.
Why Escape HTML?
Jira's text fields do not render arbitrary HTML for security reasons. If you paste raw HTML tags into a Jira ticket, they may be stripped out or displayed incorrectly. Escaping the characters that Jira itself treats as markup keeps text such as {code} or [link] from being interpreted by Jira.
This also prevents cross-site scripting issues if the Markdown source comes from an untrusted origin. Angle brackets and ampersands are not changed, because Jira wiki markup is not HTML.
Worked examples
| Example | Input | Result |
|---|---|---|
| Basic formatting | Markdown input: # Heading 1 / This is **bold** and *italic* text. / Here is `inline code`. | h1. Heading 1 / This is *bold* and _italic_ text. / Here is {{inline code}}. |
| Lists and blockquotes | Markdown input: - Apple / - Banana / - Sub-item / 1. First / 2. Second / > A wise quote | * Apple / * Banana / ** Sub-item / # First / # Second / {quote} / A wise quote / {quote} |
| Code block and table | Markdown input: ```javascript / const x = 42; / console.log(x); / ``` / | Name | Age | / |---|---| / | Alice | 30 | / | Bob | 25 | | {code:javascript} / const x = 42; / console.log(x); / {code} / ||Name||Age|| / |Alice|30| / |Bob|25| |
| Links and images | Markdown input: [Visit Example](https://example.com) /  | [Visit Example|https://example.com] / !image.png! |
FAQ
Does this tool support all Markdown features?
It supports a practical CommonMark subset including headings, bold, italic, inline code, fenced code blocks, links, images, ordered and unordered lists, blockquotes, horizontal rules and tables. Advanced extensions like footnotes or math blocks are not converted.
Will my HTML tags be preserved in Jira?
No. No. Raw HTML is not interpreted: tags are copied as plain text, and Jira shows them as typed. This keeps your Jira tickets secure and properly formatted.
Can I convert Jira markup back to Markdown here?
This tool only converts Markdown to Jira wiki syntax. For the reverse direction, you would need a separate Jira to Markdown parser.
Are nested lists supported?
Yes. Indented list items are converted using multiple asterisks or hashes. For example, two spaces before a bullet become ** in Jira, representing a second-level list item.
Is my text sent to a server?
No. The conversion logic runs entirely in your browser. Nothing is uploaded or transmitted over the network.
How are images handled?
Markdown image syntax like  is converted to Jira's image macro format: !url!. The alt text is omitted because standard Jira wiki markup does not use it in the same way.