## TL;DR

Jira rejects the issue create because the ADF (Atlassian Document Format) body is malformed. Build the ADF as nested nodes (doc, paragraph, text) and validate the structure before sending.

## Error

```text
400 on Jira issue create with an invalid ADF document
```

## Steps

1. Log the ADF payload being sent Expected: you see the malformed structure.
2. Rebuild it as proper ADF: doc node containing paragraph nodes containing text nodes Expected: the structure is valid.
3. Validate required fields (project, issuetype, summary) are present Expected: nothing else is missing.
4. Retry the create Expected: it succeeds.

## When to use

- 400 on Jira issue create with ADF
- The document structure is invalid

## When not to use

- The ADF is valid (then check the other fields)
- You can use plain text (then set the field as text, not ADF)

## Tool compatibility

- Jira ADF
- Ticketing integrations

## Variant phrasings

### jira invalid adf

Build proper ADF: doc, paragraph, text nodes.

### jira 400 issue create adf

Same: the document JSON is malformed.

## Why it happens

ADF looks like simple JSON but has a strict node schema. Agents hand-build it and miss a level.

## Edge cases

- The Jira API validates ADF strictly; test with the smallest valid doc first
- Wiki markup is not accepted where ADF is required

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ozyMSp2NKpRmlaJ5c_c8IQ