The Jira Get Transitions action returns all possible transitions (transition steps) that a specific issue can make from its current workflow status. This allows the user to see which statuses the relevant issue can transition to.

Technical Specifications

Workflow Transition Retrieval: All available transitions for the selected issue are listed. The returned data type is JiraTransitionDto (Many).

Parameters:

• settings (Object – required): Jira connection settings (defined via Config Manager).
• issue_key (String – required): Jira issue key (e.g., DEV-123).

Data Source Compatibility:

• A fixed value (Fixed Value) can be entered.
• It can be obtained from dynamic sources (Form Input, Current, Action Result, Method Input).

Web & Mobile Support: Works on both web and mobile applications.

Jira Get Transitions Application Steps

1. Adding an Action in UI Design

• Open the issue details screen.
• Add a Button element (e.g., “View Transitions”) so the user can move the issue to a different status.
• Click the button → + ADD ACTION → Jira → Jira Get Transitions.

2. Define Parameters

• settings: Select your Jira API settings from Configuration Manager.
• issue_key: Bind the key of the dynamically selected issue (e.g., Current.Issue.Key).

3. Using the Returned Data

• The returned transition list can be displayed to the user in a Select Box.
• When the user selects a transition, the selected transition ID can then be passed to the Jira Transition Issue action.

Usage Scenario: Listing Issue Status Transitions

A user wants to see which statuses issue #DEV-45 can be moved to.

Steps:

1. Click the “Show Transitions” button.
2. The Jira Get Transitions action is triggered.
3. The returned results (e.g., In Progress, In Review, Done) are displayed to the user in a list.
4. After the user makes their selection, the Jira Transition Issue action moves the issue to the new status.

Jira Get Transitions Advanced Customizations

• Dynamic Issue Key: Automatically retrieve transitions for the issue opened by the user.
• Conditional UI: Activate only permitted buttons in the UI based on the returned transition list.
• Chained Usage: You can achieve full workflow control by using the “Get Transitions” + “Transition Issue” actions together.

Technical Risks and Controls

• issue_key must be entered correctly. Otherwise, transition information cannot be retrieved.
• settings must be configured correctly. It does not work without a Jira connection in the Configuration Manager.
• There may be permission restrictions. If the user does not have permission to transition on the relevant issue, some transitions may not be listed.