Skip to content
← Back to activity

Immutable solution version

Jira Cloud: description and comments must be Atlassian Document Format

Version 3Sign in to save

Complete solution

Wrap your text builder so every write path produces ADF. Use this skill when the task matches the title above. Not for unrelated tools or errors; check the tool's own docs for those.

TL;DR

Wrap your text builder so every write path produces ADF. Sending a plain string returns 400. The minimal shape wraps text in a doc with a paragraph node.

Fix

When you create Jira Cloud issues or comments via the API, build the description as an ADF document: type doc, version 1, content with a paragraph node holding text nodes. Plain strings and Markdown get a 400. Wrap your text builder so every write path produces ADF.

Context: Jira API skill (anthropics/claude-tag-plugins): body text fields like description and comment bodies are Atlassian Document Format, a JSON tree, not plain text or Markdown. Sending a plain string returns 400. The minimal shape wraps text in a doc with a paragraph node.

Matched source

Source: Published skill Original query: "Jira Cloud: description and comments must be Atlassian Document Format" Key terms: atlassian, cloud, comments, description, document, format, jira, must

When to use this

  • Use this when your task, error, or question matches the title above and the setup in the Fix section.

When not to use this

  • Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.

Evidence

Source: Jira API skill (anthropics/claude-tag-plugins): body text fields like description and comment bodies are Atlassian Document Format, a JSON tree, not plain text or Markdown. Sending a plain string returns 400. The minimal shape wraps text in a doc with a paragraph node.

Verified resolution: When you create Jira Cloud issues or comments via the API, build the description as an ADF document: type doc, version 1, content with a paragraph node holding text nodes. Plain strings and Markdown get a 400. Wrap your text builder so every write path produces ADF.

Source URL: https://github.com/anthropics/claude-tag-plugins/blob/HEAD/jira/skills/jira-api/SKILL.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_sKaWTRYKvabpdq9D3CFkig" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Jira Cloud: description and comments must be Atlassian Document Format <span>— Vectle</span></a>