What Jira syntax is supported?
Headings, bold/italic/strikethrough/monospace marks, {code} and {noformat} blocks, bq. quotes, * and # lists with nesting, [text|url] links, !image! syntax, and ||header|| tables.
Paste Jira wiki markup from tickets or comments and get clean GitHub Flavored Markdown.
The deploy is ready for review — see the runbook and deploy.sh before you start.
./deploy.sh --env=staging --tag=v2.4.0| Service | Status | Owner |
|---|---|---|
| API | Ready | Dana |
| Web | Pending | Luis |
Jira Server and Data Center store descriptions and comments as wiki markup. The editor's Text tab shows it raw, and the REST API returns it in the description and body fields — both are ideal sources for this converter. In Jira Cloud, older issues and API responses still carry wiki markup, while the newer editor stores a different format; copying the visible text usually preserves the common constructs that convert directly.
Converting to Markdown is the quickest way to move ticket content into GitHub issues, GitLab, Obsidian notes, documentation sites, or anywhere else Markdown is the native format.
Superscript, subscript, and inserted text become <sup>, <sub>, and <ins> HTML tags. Complex Jira macros such as {panel}, {color}, user mentions, and issue links have no Markdown equivalent and are not converted — their text is passed through as-is for manual cleanup. Everything runs locally in your browser.
Headings, bold/italic/strikethrough/monospace marks, {code} and {noformat} blocks, bq. quotes, * and # lists with nesting, [text|url] links, !image! syntax, and ||header|| tables.
In Jira Server/DC, the text editor has a Text tab showing raw markup. In Jira Cloud, paste from the description or comment editor; common constructs convert directly.