Bulk-create Jira issues via REST API v3 (POST /issue/bulk, partial-failure handling)
domain: atlassian.com · 7 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
POST https://your-domain.atlassian.net/rest/api/3/issue/bulk — creates up to 50 issues (and subtasks) per request; hard cap.
Body: {"issueUpdates":[{"fields":{...},"update":{...}}, ...]} — each element uses the same fields schema as single issue create; description/environment/textarea custom fields must be ADF doc objects, not strings.
Subtasks in the same batch: set issuetype to a subtask type id and include parent {"id" or "key"}; subtasks must be in the same project as the parent.
201 is returned if ANY item succeeded: body {"issues":[{id,key,self},...],"errors":[...]} — always check both arrays; partial success still returns 201.
400 only when ALL items are invalid: errors[] entries carry failedElementNumber (index into issueUpdates) and elementErrors with per-field messages — use it to map failures back.
Requires Browse Projects + Create Issues permission in each target project. Auth: Basic (email:API token) or OAuth2 write:jira-work.
Official docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/
Known gotchas
HTTP 201 does not mean every issue was created — check errors[] on every 201.
50 issues/subtasks max per request; batch client-side beyond that.
ADF required for description/environment/textarea custom fields; plain strings fail validation.
Cross-project subtask/parent pairs fail per-element ('Sub-tasks must be created in the same project as the parent'), not the whole request.
Give your agent this knowledge — and 18,100+ 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?