Which Jira syntax is converted?

Headings (h1.-h6.), bold, italic, monospace, {code} and {noformat} blocks, ordered and unordered lists with nesting, links, blockquotes, strikethrough and horizontal rules are all mapped to Markdown.

How are Jira links converted?

A labelled link [text|url] becomes [text](url), and a bare [url] becomes an autolink , both valid Markdown.

How is nested list indentation handled?

Jira marks list depth by repeating the bullet character — ** is a second-level bullet and

Does it keep code blocks unformatted?

Yes. Anything between {code} or {noformat} fences is passed through verbatim and wrapped in triple-backtick fences, so inline markup inside a code block is never rewritten.

Why does italic stay the same?

Jira uses _underscores_ for italic and so does Markdown, so italic text needs no change. Only bold (*text* to **text**) and strikethrough (-text- to ~~text~~) are rewritten.

Can I convert Markdown back to Jira?

Yes — use the companion Markdown to Jira tool for the reverse direction. The two are designed to round-trip the common headings, emphasis, lists, links and code blocks.

No. The conversion runs entirely in your browser — nothing leaves your device.

Jira to Markdown — Gera Tools

Convert Jira wiki markup to Markdown

Pulled a description out of a Jira ticket and need it in a README, pull request or docs file? Jira’s wiki markup doesn’t render anywhere else. This tool maps it back to standard Markdown line by line, so you can paste a ticket body into GitHub, GitLab, Notion or any Markdown editor and have it render correctly.

How it works

The converter processes your text one line at a time and applies block-level rules first, then inline rules:

Jira	Markdown
`h1.` … `h6.`	`#` … `######`
`bold`	`bold`
`_italic_`	`_italic_` (unchanged)
`{{monospace}}`	`code`
`-struck-`	`~~struck~~`
`[text\|url]`	`[text](url)`
`[url]`	`<url>`
`* item` / `** item`	`- item` (indented per depth)
`# item` / `## item`	`1. item` (indented per depth)
`bq. quote`	`> quote`
`{code}` / `{noformat}`	``` fenced block
`----`	`---`

List depth is read from how many bullet characters repeat (** is level two), and each level adds two spaces of indentation. Lines inside a {code} or {noformat} block are copied verbatim and never touched.

Example

Pasting this Jira markup:

h1. Release notes

Some *bold* and _italic_ text with `{{inline code}}`.

* First item
* Second item

[Gera Tools|https://tools.gera.services]

produces:

# Release notes

Some **bold** and _italic_ text with `inline code`.

- First item
- Second item

[Gera Tools](https://tools.gera.services)

Everything runs in your browser — nothing is uploaded.