> For the complete documentation index, see [llms.txt](https://docs.yansalabs.com/jira-integration-framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yansalabs.com/jira-integration-framework/technical-docs/spoke-actions/issue-do-transition.md).

# Issue :: Do Transition

## Summary

Performs a specific transition in the workflow on a JIRA Issue

## Action Inputs

| Label                    | Name                       | Type                                  | Mandatory | Description                                                                                                                                                                         |
| ------------------------ | -------------------------- | ------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Connector                | connector                  | Reference (Reference: Jira Connector) | No        | \[optional] The sys\_id of the connector to use in the process. If this is blank, the default connector is used.                                                                    |
| Issue ID or Key          | issue\_id\_or\_key         | String                                | No        | The JIRA issue ID or Key of the issue                                                                                                                                               |
| Transition ID            | transition\_id             | String                                | No        | The JIRA ID on the transition we want to trigger on the workflow for the incident                                                                                                   |
| Optional Transition Data | optional\_transition\_data | String                                | No        | \[optional] a full transition object to do anything with the transition that is supported by JIRA REST Api                                                                          |
| Execute ASAP             | execute\_asap              | True/False                            | No        | Whether to run this as an asynchronous business rule when the record gets created or wait for the job to pick it up in relative order on the queue (typically this should be false) |

## Action Outputs

| Label         | Name           | Type                                       | Mandatory | Description                                                                                 |
| ------------- | -------------- | ------------------------------------------ | --------- | ------------------------------------------------------------------------------------------- |
| Request       | request        | Reference (Reference: Async Request Queue) | No        | The original asynchronous request queue record used to make the request                     |
| Success       | success        | True/False                                 | No        | Whether the communication and response was as expected                                      |
| Log           | log            | String                                     | No        | Scripted log statements of activities that took place during the operation of this activity |
| Retry Request | retry\_request | Reference (Reference: Async Request Queue) | No        | If there were Retries used in the process, the last retry record is returned                |

## Notes

* This action belongs to the **JIRA Request Queue** category.
* This action includes reference fields that link to other tables in ServiceNow:
  * references the table.
* This action returns 4 output(s) that can be used in subsequent flow steps.

## Example Usage

### Example 1: Basic Usage

This example demonstrates how to use the action with typical inputs.

**Input:**

**Output:**

In this example, the action processes the provided inputs and returns the appropriate outputs. The actual values returned will depend on the specific functionality of this action and the input values provided.