Skip to content
ToolPlankDEV
Text Tools
100% In-Browser Execution

Updated:

Jira to Markdown Converter

Paste Jira wiki markup and get Markdown as you type. This jira to markdown converter rewrites headings, nested lists, tables, code blocks, panels and links for GitHub, Notion or a README, and lists every macro it cannot carry over. Nothing is uploaded.

Options:

Jira wiki markup

Input
0 chars · 0 lines

Markdown

Ready
Processing in browser...
0 chars · 0 linesUpdates as you type

Macros and notes

Macros with no Markdown equivalent and every change made on the way appear here.

Processed on your device. Your text is not sent to our servers.

More free tools you may need next.

Quick Guide

How to use Jira to Markdown

Simple step-by-step instructions to get the exact output you need.

  1. 01

    Paste the Jira text

    Paste the description or comment into the left box, press Paste, or open a .txt file. If Jira shows a visual editor, switch it to the Text tab and copy from there. Example loads a ticket with a table, code and a warning panel.

  2. 02

    Read the Markdown and the macro list

    The Markdown appears on the right as you type. The panel under it lists macros that have no Markdown form, such as a table of contents, and counts every mention, emoticon and color that was changed.

  3. 03

    Choose panels, macros and bullets

    Write panels as GitHub alerts or plain block quotes, remove unknown macros or keep their text, and pick a dash or a star for bullets.

  4. 04

    Copy or download

    Press Copy to paste into a GitHub issue, a README, Notion or Obsidian, or press Download to save ticket.md.

How to convert Jira to Markdown

Jira text is stored as wiki markup: h2. Title for a heading, *text* for bold, {code} around code and ||Name|| for a table header. Markdown tools do not read that syntax. A jira to markdown converter reads the markup, builds a tree of headings, lists, tables and code, and writes the same tree as Markdown.

That makes it useful when you move tickets into GitHub issues, a README or a wiki, paste a description into a pull request or a chatbot prompt, or leave Jira Server. The conversion runs in your browser, and the text is not uploaded. The Privacy Policy has the details.

What each part becomes

  • Headings: h1. to h6. become one to six hash marks.
  • Text styles: *bold* becomes **bold**, _italic_ becomes *italic*, -strike- becomes ~~strike~~ and {{mono}} becomes a code span.
  • Links and images: a link with a pipe between text and address becomes a Markdown link, and an image between exclamation marks becomes an image with its alt text.
  • Lists: stars and hashes can be mixed and nested. A hash is a numbered item and a star is a bullet, at any depth.
  • Code: {code:java} becomes a fenced block with the language, and {noformat} becomes a fence with none.
  • Quotes and rules: {quote} and bq. become block quotes, and ---- becomes a rule.

A worked example

This Jira text has a heading, a nested list, a table and a Java block:

Text
h3. Steps

# Open the reset link
# Choose a password
#* at least 12 characters

||Browser||Fails||
|Chrome|(x)|

{code:java}
int ttl = 3600;
{code}

The converter writes this Markdown. The (x) emoticon becomes an emoji and the table gets the divider row that Markdown requires:

markdown
### Steps

1. Open the reset link
2. Choose a password
   - at least 12 characters

| Browser | Fails |
| --- | --- |
| Chrome | ❌ |

```java
int ttl = 3600;
```

Panels, info boxes and quotes

Jira has colored boxes: info, tip, note, warning and the general panel. Markdown has only the block quote, plus the alert syntax that GitHub shows as a colored box. With GitHub alerts, info becomes NOTE, tip becomes TIP, note becomes WARNING and warning becomes CAUTION. A panel title becomes a bold line inside the box.

Choose plain block quotes when the Markdown goes anywhere other than GitHub. Each box is then a quote that starts with a bold label such as Warning, so the meaning stays even where nothing is colored. Text inside a panel is converted like any other text, including lists and code.

Jira tables to Markdown

A row that starts with double pipes is the header. Markdown tables must have a header, so a table whose first row uses single pipes is still converted, with the first row as header, and the notes say so. Rows with fewer cells are padded so the table stays valid.

A link inside a cell keeps its pipe, because the splitter reads square brackets as one piece. A cell that spans several lines in Jira is not joined. If you have HTML tables instead, HTML Table to Markdown handles those.

Macros, mentions and colors

Markdown has no table of contents macro, no color, no underline and no user lookup, so those parts are handled openly. Unknown macros such as {toc} are removed or kept as text, as you choose, and each one is counted in the macro list. Color macros lose the color and keep the words. A mention of a user becomes @jsmith text.

Underlined text, superscript and subscript are written as plain text. An opening macro that is never closed swallows the rest of the text, and the notes report it.

Going the other way

To write Markdown and paste it into Jira, use Markdown to Jira, which also lists the Markdown that Jira cannot show. If you want plain words with no syntax at all, Markdown to Text strips the Markdown this tool produces, and Rich Text to Markdown converts text copied from a web page or editor.

Frequently Asked Questions

Technical Q&A for Jira to Markdown

Common questions about edge cases, character encoding, and privacy guarantees.

Paste the Jira text into the left box and the Markdown appears on the right. Press Copy to use it in GitHub, Notion or a README, or Download to save ticket.md.

Open the description or comment for editing and switch the editor to the Text tab, then copy. The visual editor hides the markup, so copying from it gives formatted text and not wiki markup.

A {code:java} block becomes a fenced block that starts with the language name. A {noformat} block becomes a fence with no language. The code inside is kept exactly as written.

They become GitHub alerts such as NOTE and CAUTION, or plain block quotes with a bold label if you choose that option. A panel title becomes a bold line.

Yes. A row with double pipes becomes the header, and the rows after it become table rows. A table without a header row uses its first row as the header, because Markdown requires one.

They are removed and listed, or kept as plain text if you choose that. Markdown has no table of contents, anchor or expand macro, so there is nothing to convert them to.

They are kept as text. A mention becomes @name and an issue key such as PROJ-12 stays as PROJ-12. The tool does not contact Jira, so it cannot create links to your site.

Yes, paste as much text as you like. Each comment is just more wiki markup, and the output is one Markdown document.

No. The conversion runs in your browser and nothing is sent to a server.