Markdown to Jira

Convert Markdown to Jira Wiki Markup. Handles headings, code blocks, tables, links, lists, and inline formatting.

Markdown

Jira Wiki Markup

h1. Welcome to My Project

This is a *bold* statement and this is _italic_.

h2. Features

* Fast and reliable
* Easy to configure
* -Deprecated option- (removed)

h3. Code Example

{code:javascript}
const hello = "world";
console.log(`Hello ${hello}!`);
{code}

Inline code: {{npm install}}

h3. Links

[Visit our docs|https://docs.example.com]

h3. Table

|| Name || Role || Status ||
| Alice | Admin | Active |
| Bob | User | Inactive |

{quote}
Important: Always read the documentation first.
{quote}

----

# First step
# Second step
# Third step

Markdown to Jira Wiki Markup Converter

Jira uses its own wiki markup syntax that differs from standard Markdown. Key differences: headings use h1. syntax, bold uses *text*, inline code uses {{text}}, and links use [text|url]. Code blocks use the {code} macro with optional language syntax highlighting.

Built and maintained by Meet Shah · Last updated 27 July 2026

What this tool is used for

Posting a formatted issue description when your notes are written in Markdown.
Converting release notes for a Jira ticket or comment.
Adapting a bug report from a repository into an issue body.
Producing Jira markup from documentation you maintain elsewhere.
Getting a code block to render properly in a Jira comment.

Frequently Asked Questions

Why does Jira need its own markup?: Because Jira's wiki syntax predates Markdown's ubiquity and never adopted it. Headings are `h1.` rather than `#`, bold is `*text*` rather than `**text**`, and code blocks use `{code}` — so a Markdown paste renders as literal asterisks and hashes.
What is the trap with bold and italic?: They are swapped relative to Markdown. Jira uses a single asterisk for BOLD and an underscore for italic, where Markdown uses one asterisk for italic and two for bold. A naive conversion that maps `**` to `*` and leaves `*` alone turns every italic into bold.
How do code blocks convert?: A fenced block becomes `{code:language}` … `{code}`, and inline code becomes `{{monospace}}`. The language token is preserved where Jira recognises it, which is what gives the syntax highlighting — an unrecognised language falls back to plain monospace rather than failing.
What about tables?: Jira uses `||` for header cells and `|` for body cells, with no delimiter row at all — so the row of dashes that GitHub Flavored Markdown requires has to be removed rather than translated. Leaving it in produces a phantom first data row of dashes.
Does the new Jira editor still need this?: Less than it did — the cloud rich-text editor accepts a good deal of Markdown as you type. But the API, automation rules, and any field rendered from stored wiki markup still use the old syntax, which is where a conversion is still the reliable path.

Common errors and gotchas

Expecting Markdown code fences to work. Jira uses its own code macro with a different syntax.
Assuming heading syntax matches, when Jira uses h1. through h6. rather than hashes.
Losing table header formatting, which Jira marks with double pipes.
Overlooking that Jira's newer editor may not accept wiki markup at all.
Leaving nested list indentation as spaces, where Jira uses repeated markers.