How do I make a header row in a Jira table?

Use double pipes around each header cell: ||Env||Version||Result||. Body rows use single pipes. Jira has no separator-row concept like Markdown.

Why does my table render fine in the Cloud editor but break via the API?

The Cloud editor may auto-format pasted content, but the v2 REST API renders raw wiki markup — the table must already be in ||header|| / |cell| form when submitted.

Can Jira tables span columns or align text?

Not in wiki markup. Column spans and alignment aren't supported syntax — keep tables simple, and restructure wide tables into two narrower ones if they overflow.

What happens to empty Markdown cells?

Keep a space between the pipes (| |) so the row keeps its shape — completely empty cells can make Jira merge or drop the cell.

Jira wiki markup guide

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.

Direct answer

A Markdown table becomes a Jira table by converting the header row to double pipes (||Header||Header||), dropping the |---| separator row, and keeping body rows as single-pipe cells. Jira marks header cells with the double pipes, so no separator line is needed.

Open Markdown to Jira converter

When to use this

A test matrix, environment list, or comparison table drafted in Markdown belongs in a Jira ticket.
Pasted Markdown tables are rendering as a wall of pipes and dashes.
QA repro grids or rollout plans need scannable tables inside descriptions or comments.

Steps

Give every Markdown row the same number of cells.
Convert — the header row becomes ||...|| and the separator row is removed.
Paste into the Jira description or comment field.
Preview: header cells render shaded; body rows follow.
If a row shows as text, look for an unescaped pipe inside a cell.

Example conversion

Markdown input

| Env | Version | Result |
|-----|---------|--------|
| staging | 2.14.1 | pass |
| prod | 2.14.0 | fail |

Jira wiki output

||Env||Version||Result||
|staging|2.14.1|pass|
|prod|2.14.0|fail|

Common mistakes

Do not keep the Markdown separator row — Jira renders |---|---| as a real row of dashes.
Do not leave a trailing pipe off the end of a row; Jira needs each row fully closed.
Do not put line breaks inside a cell; Jira wiki tables are one row per line.

FAQ

How do I make a header row in a Jira table?: Use double pipes around each header cell: ||Env||Version||Result||. Body rows use single pipes. Jira has no separator-row concept like Markdown.
Why does my table render fine in the Cloud editor but break via the API?: The Cloud editor may auto-format pasted content, but the v2 REST API renders raw wiki markup — the table must already be in ||header|| / |cell| form when submitted.
Can Jira tables span columns or align text?: Not in wiki markup. Column spans and alignment aren't supported syntax — keep tables simple, and restructure wide tables into two narrower ones if they overflow.
What happens to empty Markdown cells?: Keep a space between the pipes (| |) so the row keeps its shape — completely empty cells can make Jira merge or drop the cell.

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.

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.

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.

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.