Jira to Markdown Converter
Convert Jira to markdown and markdown to Jira wiki markup. Handles headings, bold, code blocks, tables and lists in both directions. Free tool.
## Summary Checkout fails with a **500 error** when the cart contains a *discounted* item and the coupon field is empty. ### Steps to reproduce 1. Add `SKU-1042` to the cart 1. Apply the ~~SPRING10~~ coupon, then remove it 1. Click **Pay now** ### Expected ✅ Order is created and the confirmation page loads. ### Actual ❌ The page shows "Something went wrong" and the log contains: ``` NullPointerException at CouponService.apply(CouponService.java:88) ``` | Environment | Version | | --- | --- | | Production | 2.3.7 | | Staging | 2.4.0-rc1 | > **Workaround** > > Refresh the cart page before paying. See [PAY-2210](https://example.atlassian.net/browse/PAY-2210).
What Is a Jira to Markdown Converter?
A Jira to markdown converter rewrites Jira wiki markup, the notation used in issue descriptions and comments, as standard markdown so the same text can be pasted into GitHub, a pull request, Slack, a README or a docs site. Jira markup writes headings as h2., bold as *bold*, code as {code}and tables as ||header|| rows, and none of that renders outside Atlassian products.
The converter also goes from markdown to Jira, which is what you need when a bug report drafted in a markdown editor has to become a ticket. Both directions run in your browser.
How to Convert Jira to Markdown
- Open the issue and copy the description or comment. On Server and Data Center, use the text tab of the editor to copy the raw wiki markup; on Cloud, copying the rendered text works too.
- Paste into the left pane. Wiki markup is parsed directly; rich text is detected as HTML and converted with the same rules.
- Check the markdown on the right. Tick Show rendered preview to see tables and code blocks as they will render.
- Copy the markdown or download it as a .md file.
Jira Wiki Markup Reference
| Jira wiki markup | Markdown |
|---|---|
h1. to h6. | # to ###### |
*bold*, _italic_, -strike-, +underline+ | **bold**, *italic*, ~~strike~~, <u> |
{{monospace}}, ^sup^, ~sub~ | `code`, <sup>, <sub> |
{code:js}, {noformat} | Fenced code blocks |
bq., {quote}, {panel:title=X} | Blockquotes, panel title in bold |
* bullet, ** nested, # numbered | Indented - and 1. lists |
||A||B|| then |1|2| | Pipe table |
[text|https://url], [https://url], [~user] | [text](url), <url>, @user |
!image.png|width=200! |  |
(/) (x) (!) (?) (i) | ✅ ❌ ⚠️ ❓ ℹ️ |
{color:red}text{color} | text (color dropped) |
---- | --- |
Markdown to Jira
Choose Markdown → Jira to produce jira wiki markup from markdown. Headings become h-lines, emphasis becomes single asterisks and underscores, fenced code becomes {code:lang}, tables become double-pipe headers, task lists get (/) and (x) markers and callouts become titled panels. Curly braces in ordinary text are escaped so Jira does not mistake them for macros. The output is plain text, so it pastes into any wiki-renderer field or an API payload as-is. The same jira markdown mapping powers the Confluence converter linked below.
Why Use a Jira to Markdown Converter
Issue text gets reused constantly: steps to reproduce end up in a pull request, a workaround gets posted to Slack, an incident description becomes a postmortem page. Each of those destinations speaks markdown, not Jira wiki markup. Running the text through a jira to markdown converter takes seconds and keeps the tables, code blocks and lists that make the report readable. Because the conversion happens locally in the browser, it is safe to use with internal ticket content.
Frequently Asked Questions
Does Jira support markdown?
Not directly. Jira Cloud's editor accepts a few markdown shortcuts as you type (## for a heading, ** for bold), but pasted markdown is treated as plain text. Jira Server, Data Center and the REST API use Jira wiki markup instead. This jira to markdown converter translates between the two notations so nothing has to be reformatted by hand.
How do I paste markdown into a Jira ticket?
Switch the direction to Markdown → Jira, paste your markdown and copy the wiki markup from the right pane. In Jira Server or Data Center paste it into the description field's text tab. In Jira Cloud you can paste it into fields that still use the wiki renderer, or send it through the REST API, which accepts wiki markup for description and comment bodies.
What happens to {code}, {noformat} and {quote} blocks?
{code:java} becomes a fenced code block tagged java, {noformat} becomes a fence without a language, and {quote} or bq. becomes a markdown blockquote. In the other direction fenced code becomes {code:lang} and plain fences become {noformat}, which is what Jira renders as a preformatted block.
Are Jira emoticons and colors converted?
Emoticons such as (/), (x), (!), (?) and (i) become the matching Unicode symbols so they survive as text. {color:red}…{color} spans have no markdown equivalent, so the color is dropped and the text is kept. Jira wiki markup for superscript and subscript becomes <sup> and <sub> tags, which most markdown renderers accept.
Does the tool connect to my Jira instance?
No. Everything runs in the browser. Paste the description or comment text, convert it, and paste the result back; nothing is uploaded and no Atlassian credentials are involved.