Which Markdown features are converted?

Headings, bold, italic, inline code, fenced code blocks, ordered and unordered lists (with nesting), links, blockquotes, strikethrough and horizontal rules are all mapped to their Jira wiki markup equivalents.

How are code blocks handled?

Fenced code blocks become Jira {code} blocks, and a language hint like ```js becomes {code:js} so syntax highlighting works in Jira.

Is anything uploaded?

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

How are bold and italic converted?

Markdown bold (**text** or __text__) becomes Jira *text*, and Markdown italic (*text* or _text_) becomes Jira _text_. Because both languages overload the asterisk, the converter processes links and code first, then bold, then single-star italic, to avoid clashes.

How are links converted to Jira?

A Markdown link [text](url) becomes the Jira form [text|url], with the pipe separating the label from the target. Bare or angle-bracket autolinks are left as-is since Jira renders raw URLs as clickable links.

Does it handle nested lists?

Yes. Indentation depth is converted to repeated markers: an unordered item nested two spaces becomes ** in Jira, three levels becomes ***, and ordered lists use # repeated the same way (#, ##, ###).

What about blockquotes and horizontal rules?

A Markdown blockquote (> text) becomes a Jira bq. line, and a horizontal rule (---, ***, or ___) becomes ---- (four dashes), which is the Jira wiki-markup divider.

Markdown to Jira — Gera Tools

Jira’s classic editor uses its own wiki markup, not Markdown — so pasting a README or pull-request description straight into a ticket leaves you with broken # headings and literal **stars**. This converter rewrites GitHub-style Markdown into the matching Jira syntax so it renders correctly in ticket descriptions and comments. Paste on the left, copy clean Jira markup from the right.

How it works

The text is processed line by line. Fenced code blocks (```) are detected first and their contents passed through untouched, becoming {code} (or {code:js} when a language is given). Outside code, each line is matched against block rules — headings, blockquotes, lists, horizontal rules — and the remaining inline syntax is rewritten in a fixed order (links, then code spans, then bold, then italic, then strikethrough) so the shared * and _ characters don’t collide.

Markdown	Jira wiki markup
`# Heading`	`h1.` (## → h2, etc.)
`bold`	`bold`
`italic`	`_italic_`
`code`	`{{code}}`
```js block	`{code:js}` … `{code}`
`[text](url)`	`[text\|url]`
`> quote`	`bq. quote`
`- item` (nested)	`` / `` / `**`
`---`	`----`

Example

The Markdown See the **release** notes at [docs](https://example.com) converts to See the *release* notes at [docs|https://example.com]. A ## Setup heading becomes h2. Setup, and a two-space-indented - step becomes ** step.

Everything happens in your browser — nothing is uploaded.