The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bulk Create Issue REST API - Does it support multiple transitions?

KC Wong
Contributor
May 22, 2026

The bulk create issue REST API: 
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-bulk-post

It includes a transition attribute in the payload. But I assume it must start from the initial status? Can it support multiple transitions? 

Or must I modify the workflow to add transitions to every status, hide them from users, in order to be able to create issue with any status? 

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

4 votes
Answer accepted
Carlos Garcia Navarro
Community Champion
May 23, 2026

Hi @KC Wong ,

Yes, the transition field on the Bulk Create Issue API only supports a single transition, and it must be a valid transition from the issue’s initial workflow state after creation. if you need issues to be created directly into arbitrary statuses, you would typically need to make those statuses reachable immediately after creation.

 

1 vote
Arkadiusz Wroblewski
Community Champion
May 23, 2026

Hello @KC Wong 🤠

The bulk create endpoint only handles a single transition during creation, it cannot chain multiple workflow steps at once. To move an issue through a sequence, you need to create it first and then call the transition endpoint separately for each subsequent step.

If you want to land issues directly into various target statuses right at creation, your workflow must explicitly allow those paths from the start via direct or global transitions. If these paths are strictly for an integration, you can use workflow conditions to hide them from your regular users. 

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events