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.

External Documentation

To learn more, visit the Jira documentation.

​
Basic Parameters

ParameterDescription
Issue ID Or KeyThe ID or key of the issue.
Transition ID FilterIf specified, only returns the given transition ID.

​
Advanced Parameters

ParameterDescription
ExpandUse 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.
Include Unavailable TransitionsWhether details of transitions that fail a condition are included in the response.
Skip Remote Only ConditionWhether transitions with the condition Hide From User Condition are included in the response.
Sort By Ops Bar And StatusWhether the transitions are sorted by ops-bar sequence value first then category order (Todo, In Progress, Done) or only by ops-bar sequence value.

​
Example Output

{
	"expand": "<string>",
	"transitions": [
		{
			"id": "<string>",
			"name": "<string>",
			"to": {
				"self": "<string>",
				"description": "<string>",
				"iconUrl": "<string>",
				"name": "<string>",
				"id": "<string>",
				"statusCategory": {
					"self": "<string>",
					"id": 2,
					"key": "<string>",
					"colorName": "<string>",
					"name": "<string>"
				}
			},
			"hasScreen": false,
			"isGlobal": true,
			"isInitial": false,
			"isAvailable": true,
			"isConditional": false,
			"isLooped": false
		},
		{
			"id": "<string>",
			"name": "<string>",
			"to": {
				"self": "<string>",
				"description": "<string>",
				"iconUrl": "<string>",
				"name": "<string>",
				"id": "<string>",
				"statusCategory": {
					"self": "<string>",
					"id": 6,
					"key": "<string>",
					"colorName": "<string>",
					"name": "<string>"
				}
			},
			"hasScreen": false,
			"isGlobal": true,
			"isInitial": false,
			"isAvailable": true,
			"isConditional": false,
			"isLooped": false
		}
	]
}

​
Workflow Library Example

Get Transitions with Jira and Send Results Via Email

Preview this Workflow on desktop

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.

External Documentation

To learn more, visit the Jira documentation.

​
Basic Parameters

ParameterDescription
Issue ID Or KeyThe ID or key of the issue.
Transition ID FilterIf specified, only returns the given transition ID.

​
Advanced Parameters

ParameterDescription
ExpandUse 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.
Include Unavailable TransitionsWhether details of transitions that fail a condition are included in the response.
Skip Remote Only ConditionWhether transitions with the condition Hide From User Condition are included in the response.
Sort By Ops Bar And StatusWhether the transitions are sorted by ops-bar sequence value first then category order (Todo, In Progress, Done) or only by ops-bar sequence value.

​
Example Output

{
	"expand": "<string>",
	"transitions": [
		{
			"id": "<string>",
			"name": "<string>",
			"to": {
				"self": "<string>",
				"description": "<string>",
				"iconUrl": "<string>",
				"name": "<string>",
				"id": "<string>",
				"statusCategory": {
					"self": "<string>",
					"id": 2,
					"key": "<string>",
					"colorName": "<string>",
					"name": "<string>"
				}
			},
			"hasScreen": false,
			"isGlobal": true,
			"isInitial": false,
			"isAvailable": true,
			"isConditional": false,
			"isLooped": false
		},
		{
			"id": "<string>",
			"name": "<string>",
			"to": {
				"self": "<string>",
				"description": "<string>",
				"iconUrl": "<string>",
				"name": "<string>",
				"id": "<string>",
				"statusCategory": {
					"self": "<string>",
					"id": 6,
					"key": "<string>",
					"colorName": "<string>",
					"name": "<string>"
				}
			},
			"hasScreen": false,
			"isGlobal": true,
			"isInitial": false,
			"isAvailable": true,
			"isConditional": false,
			"isLooped": false
		}
	]
}

​
Workflow Library Example

Get Transitions with Jira and Send Results Via Email

Preview this Workflow on desktop