Which languages does the Jira code macro support?

Common values include java, bash, python, sql, xml, javascript, and json — written as {code:java}. Unsupported languages still render as a plain monospaced block.

When should I use {noformat} instead of {code}?

Use {noformat} for logs, stack traces, diffs, and terminal output — anything where syntax coloring is wrong or noisy. Use {code} for actual source code and commands.

How does inline code convert?

Markdown inline backticks like `config.yaml` become Jira {{config.yaml}} monospace text, which renders inline within the sentence.

Why did my code block swallow the rest of the ticket?

An unclosed {code} macro treats everything after it as code. Make sure every {code} has a matching closing {code} — converted output always pairs them.

Jira wiki markup guide

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.

Direct answer

Markdown code fences become Jira {code} macros: ```java converts to {code:java} ... {code}. For stack traces, logs, and terminal output where highlighting adds noise, use {noformat} ... {noformat} instead.

To copy a {code} block out of an existing ticket as a fenced block, use the Jira to Markdown converter.

Open Markdown to Jira converter

When to use this

Bug reports carry stack traces or console output that must stay readable.
Repro steps include shell commands or JSON payloads drafted in Markdown.
Pasted code in a ticket collapsed into one unformatted paragraph.

Steps

Tag Markdown fences with a language (```java, ```python, ```sql) where highlighting helps.
Convert the draft — fences become {code:language} macros, inline backticks become {{monospace}}.
Move pure log output into {noformat} blocks.
Paste into the description and preview: code should render in a bordered block.
Keep one command per line so on-call engineers can copy them safely.

Example conversion

Markdown input

Steps:

1. Run the failing job

```bash
python etl.py --date 2026-07-01
```

Stack trace:

```
KeyError: 'currency'
  File "etl.py", line 88
```

Jira wiki output

Steps:

# Run the failing job

{code:bash}
python etl.py --date 2026-07-01
{code}

Stack trace:

{noformat}
KeyError: 'currency'
  File "etl.py", line 88
{noformat}

Common mistakes

Do not paste triple-backtick fences into Jira — they render as literal characters around unformatted text.
Do not syntax-highlight stack traces; {noformat} keeps them intact without misleading coloring.
Do not put {code} blocks inside table cells — rendering is unreliable; link or attach instead.

FAQ

Which languages does the Jira code macro support?: Common values include java, bash, python, sql, xml, javascript, and json — written as {code:java}. Unsupported languages still render as a plain monospaced block.
When should I use {noformat} instead of {code}?: Use {noformat} for logs, stack traces, diffs, and terminal output — anything where syntax coloring is wrong or noisy. Use {code} for actual source code and commands.
How does inline code convert?: Markdown inline backticks like `config.yaml` become Jira {{config.yaml}} monospace text, which renders inline within the sentence.
Why did my code block swallow the rest of the ticket?: An unclosed {code} macro treats everything after it as code. Make sure every {code} has a matching closing {code} — converted output always pairs them.

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.

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.