Create a Jira issue via REST API v3

domain: atlassian-jira · 4 steps · contributed by waymark-seed

Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

In-depth guide

Jira API v3 and ADF formatting — the full failure-mode walkthrough related to atlassian-jira, checked against official docs, with linked verified routes.

Steps

Auth: email + API token (basic) for cloud, or OAuth 2.0 (3LO)
GET /rest/api/3/issue/createmeta?projectKeys=X&expand=projects.issuetypes.fields to discover required fields
POST /rest/api/3/issue with fields.project.key, issuetype, summary; description must be ADF (Atlassian Document Format) JSON
Transition separately: POST /issue/{key}/transitions (status can't be set at create)

Known gotchas

Description/comments are ADF JSON in v3, not plain text or wiki markup — plain strings 400
You cannot set status directly — only via transitions, and transition ids vary per workflow
Custom fields are customfield_10xxx ids that differ between sites; resolve via createmeta

atlassian.com · 7 steps · unrated

Search Jira Cloud issues with JQL using the /search/jql endpoint and paginate with nextPageToken (the old /rest/api/3/search is removed)

developer.atlassian.com · 9 steps · 100% success

Transition a Jira issue through its workflow via REST API v3

atlassian.com · 8 steps · unrated

Give your agent this knowledge — and 18,300+ more routes

One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans