Bulk request for status transition ID

[Dmitry Kuharev]

Hello, could you please explain the nuances of how Get available transitions requests work?

There are two issues:
QWE-1 has the status “To do”
QWE-2 has the status “In progress”
Both issues can be changed to “Pending” status.

The situation is as follows: if I perform a request to

GET /rest/api/3/bulk/issues/transition?issueIdsOrKeys=QWE-1

in the response I get 2 different transition options.

Also, if I make a request only for QWE-2 -

GET /rest/api/3/bulk/issues/transition?issueIdsOrKeys=QWE-2

I also get 2 transition options.

But if I make a GET request for two issues at once,

GET /rest/api/3/bulk/issues/transition?issueIdsOrKeys=QWE-1,QWE-2

then I don't get any transition options.

Am I correct in understanding that I am only given general transition options that are valid for all issues in the request?

It would be nice to get all available transitions for both QWE-1 and QWE-2 in one request, as it comes only for one.

And also the situation with the POST request Bulk transition issue statuses, I take the same two issues (QWE-1 and QWE-2). I try to change their status to the same, for example, “Pending.”
I create the request body with the transitionId I need:

{
  "bulkTransitionInputs": [
    {
      "selectedIssueIdsOrKeys": [
        "QWE-1"
      ],
      "transitionId": "91"
    },
    {
      "selectedIssueIdsOrKeys": [
        "QWE-2"
      ],
      "transitionId": "111"
    }
   ],
   "sendBulkNotification": false
}

But I get an error:

“message”: “Every transition input must correspond to a distinct workflow.”

[Hari Krishna · Accepted solution]

Hi @Dmitry Kuharev ,

Yes, your understanding is correct.

For GET /bulk/issues/transition, Jira returns only those transitions that are valid for all issues in the request.
Since QWE-1 and QWE-2 are in different current statuses, the transitions available from those statuses are different, even if they eventually lead to the same target status (“Pending”). Because there is no single common transition, the bulk GET request returns no options.

There is currently no API support to fetch all transitions per issue in a single bulk request. You must call the transitions API per issue to get their available transitions.

Regarding the POST bulk transition error:

Even if two issues move to the same target status, Jira treats transitions as workflow-specific actions, not status-based actions.
In your case:

Transition 91 and 111 belong to the same workflow

Bulk transition API requires each bulkTransitionInput to map to a different workflow

Since both issues are in the same workflow, Jira rejects the request

This means:

You cannot bulk-transition issues in the same workflow using different transition IDs in one request

Bulk transition only works when:

All issues use the same transition ID, or

Each input refers to a different workflow