How do I paste a Markdown table into a Jira ticket?

Convert it first. The header row becomes ||Header||Header||, the separator row is removed, and body rows keep single pipes. Then paste the converted table into the description or comment.

Why does my pasted Markdown show literal ** and ## characters?

Jira fields treat pasted text as plain text plus wiki markup, not Markdown. The ** and ## have no meaning there, so they render literally until you convert them to *bold* and h2. syntax.

Can I paste Markdown into a Jira comment?

Yes, after converting it to wiki markup. Comments behave like descriptions: pasted Markdown stays plain, converted wiki markup renders.

What about creating issues through the API?

Send wiki markup in the v2 REST API description field. The v3 API expects Atlassian Document Format (ADF) JSON instead — raw Markdown fails in both.

Jira wiki markup guide

How to Paste Markdown Into Jira

Paste Markdown into Jira without broken formatting: convert to wiki markup first, then paste into the description or comment field. Covers tables, code blocks, and the API case.

Direct answer

Convert the Markdown to Jira wiki markup first, then paste the converted text into the Jira field. Pasting raw Markdown leaves literal ##, **, and pipe characters because Jira description and comment fields do not render Markdown on paste.

Open Markdown to Jira converter

When to use this

A ticket drafted in Markdown must go into a Jira description or comment.
A pasted table renders as a wall of pipes and dashes.
An AI assistant produced a Markdown ticket that you file into Jira by hand.

Steps

Copy the full Markdown draft, including tables and code fences.
Paste it into the converter and copy the Jira wiki markup output.
Open the Jira issue and paste the output into the description or comment field.
For tables, confirm the header row shows ||double pipes|| and the |---| separator row is gone.
Preview the field before you save: headings, bold, lists, code, and tables must render cleanly.

Example conversion

Markdown input

## Bug: export fails

**Steps**

1. Open the report
2. Click `Export CSV`

| Browser | Result |
| --- | --- |
| Chrome | fails |
| Firefox | works |

Jira wiki output

h2. Bug: export fails

*Steps*

# Open the report
# Click {{Export CSV}}

||Browser||Result||
|Chrome|fails|
|Firefox|works|

Common mistakes

Do not paste raw Markdown and hope the editor fixes it — Cloud converts some syntax as you type, not on paste.
Do not keep the Markdown |---| separator row; Jira renders it as a real row of dashes.
Do not paste triple-backtick fences; convert them to {code} or {noformat} blocks first.

FAQ

How do I paste a Markdown table into a Jira ticket?: Convert it first. The header row becomes ||Header||Header||, the separator row is removed, and body rows keep single pipes. Then paste the converted table into the description or comment.
Why does my pasted Markdown show literal ** and ## characters?: Jira fields treat pasted text as plain text plus wiki markup, not Markdown. The ** and ## have no meaning there, so they render literally until you convert them to *bold* and h2. syntax.
Can I paste Markdown into a Jira comment?: Yes, after converting it to wiki markup. Comments behave like descriptions: pasted Markdown stays plain, converted wiki markup renders.
What about creating issues through the API?: Send wiki markup in the v2 REST API description field. The v3 API expects Atlassian Document Format (ADF) JSON instead — raw Markdown fails in both.

Related Jira guides

Markdown Acceptance Criteria to Jira

Convert Markdown acceptance criteria into Jira wiki markup that stays readable in issue descriptions.

AI Coding Notes to Jira Ticket

Turn rough AI coding session notes into a Jira implementation ticket with scope, telemetry, and tests.

QA Repro Steps Jira Template

Format QA repro steps, environment details, evidence, and acceptance criteria as a Jira bug ticket.

Jira Markdown vs Wiki Markup

Why Markdown breaks in Jira description fields, how Jira's own wiki markup differs, and a side-by-side of the syntax that trips people up.

Jira Markdown Table: Convert a Markdown Table to Jira

A Jira markdown table uses ||double pipes|| for headers and no separator row. Convert Markdown pipe tables into Jira wiki markup tables that render in descriptions and comments.

Markdown Code Blocks to Jira

Turn Markdown fenced code blocks into Jira {code} macros with language highlighting, and use {noformat} for logs and stack traces.

How to Format Code Blocks in Jira

Wrap the code in a {code} macro, or use the code block button in the new editor. Markdown fences do not work in Jira. Covers language hints, {noformat}, and inline code.

Does Jira Support Markdown? What Works and What Does Not

Jira does not render pasted Markdown in description or comment fields. This guide shows which fields accept Markdown for Jira, which need wiki markup, and how to convert.

Jira to Markdown: Convert Wiki Markup Back to Markdown

Convert Jira to Markdown: turn wiki markup from descriptions and comments — h2. headings, {code} blocks, ||header|| tables — into clean Markdown for docs, README files, and AI tools.

Reading for ticket work

Automate the Jira busywork, write epics that survive a sprint, and keep the sentences short.

Book · Jira

Automate Everyday Tasks in Jira

A no-code guide for Jira admins and power users. It covers the rules that move, assign, and update issues, so you stop doing it by hand.

No-code automation rules
Written for admins and power users
Everyday Jira processes, not certification prep
Pairs with the Markdown to Jira tool

Check price on Amazon →Book

The Epic Guide to Agile

Covers the part most Scrum books skip: shipping on a schedule you can actually predict, and writing epics and stories that survive contact with a sprint.

Epics, stories, and estimation
Predictable release planning
Practical Scrum, not certification prep
Pairs with the Jira and epic tools

Check price on Amazon →Book · Writing

The Elements of Style (4th ed.)

The short book on plain sentences. Most of what makes a ticket or a spec readable is in the first forty pages.

Strunk and White, fourth edition
Rules of usage and composition
Under 120 pages
The shortest fix for bloated prose

Check price on Amazon →

Amazon affiliate links. We earn a commission on qualifying purchases at no extra cost to you.