GET /rest/api/2/issue/{issueIdOrKey}/transitions

Returns either all transitions or a transition that can be performed by the user on an issue, based on the issue's status.

Note, if a request is made for a transition that does not exist or cannot be performed on the issue, given its status, the response will return any empty transitions list.

This operation can be accessed anonymously.

Permissions required: A list or transition is returned only when the user has:

However, if the user does not have the Transition issues project permission the response will not list any transitions.

Servers

Path parameters

Name Type Required Description
issueIdOrKey String Yes

The ID or key of the issue.

Query parameters

Name Type Required Description
transitionId String No

The ID of the transition.

includeUnavailableTransitions Boolean No

Whether details of transitions that fail a condition are included in the response

Default value: false

skipRemoteOnlyCondition Boolean No

Whether transitions with the condition Hide From User Condition are included in the response.

Default value: false

expand String No

Use expand to include additional information about transitions in the response. This parameter accepts transitions.fields, which returns information about the fields in the transition screen for each transition. Fields hidden from the screen are not returned. Use this information to populate the fields and update fields in Transition issue.

sortByOpsBarAndStatus Boolean No

Whether the transitions are sorted by ops-bar sequence value first then category order (Todo, In Progress, Done) or only by ops-bar sequence value.

Default value: false

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.