IssueTransitions
Displays all possible transitions for issues, including available status changes and transition rules.
Table Specific Information
You can search for IssueTransitions by using SQL and JQL (Jira Query Language).
Select
The add-in uses the Jira API to process some of the filters.
The add-in processes other filters within the add-in.
The available columns for IssueTransitions are IssueId, IssueKey, and JQL. For example:
SELECT * FROM IssueTransitions WHERE JQL = 'id=10022'
Columns
| Name | Type | References | SupportedOperators | Platform | Description |
| Id [KEY] | String | Common | The unique identifier of the transition that is available for the specified issue. Used to programmatically reference a transition. | ||
| IssueId [KEY] | Integer |
Issues.Id | =,<>,>,>=,<,<=,IN,NOT IN | Common | The internal identifier of the issue for which this transition is available. This links the transition to a specific issue. |
| IssueKey | String |
Issues.Key | =,<>,>,>=,<,<=,IN,NOT IN | Common | The human-readable key of the issue (such as 'PROJ-101') associated with the transition. Commonly used in the user interface and API. |
| IssueCreatedDate | Datetime | =,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN | Common | The date and time when the issue was originally created. Useful for understanding when the issue entered the system. | |
| IssueUpdatedDate | Datetime | =,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN | Common | The most recent timestamp when the issue was modified. Reflects the latest update before the transition was retrieved. | |
| HasScreen | String | Common | Indicates whether the transition includes a screen, such as one prompting for additional fields or comments when the transition is performed. | ||
| Name | String | Common | The name of the transition, as defined in the workflow (for example, 'Start Progress', 'Resolve Issue'). Represents the action being performed. | ||
| ToDescription | String | Common | A textual description of the status that the issue will move into after the transition is completed. | ||
| ToId | String | Common | The internal identifier of the destination status the issue will move to after this transition. | ||
| ToName | String | Common | The name of the destination status (such as 'In Progress', 'Done', or 'Closed') that results from this transition. | ||
| StatusCategoryId | Integer | Common | The unique identifier of the category to which the destination status belongs. Status categories help group statuses (for example, 'To Do', 'In Progress'). | ||
| StatusCategoryKey | String | Common | The programmatic key of the destination status category. This is a stable reference used in configurations and API logic. | ||
| StatusCategoryName | String | Common | The display name of the category of the destination status. This gives a general idea of where in the workflow the issue is headed. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| JQL | String | Jira Query Language (JQL) allows you to construct structured queries to retrieve transitions based on criteria such as issue key or current status. |