Perform Transition
Description
JIRA perform transition plugin step performs a transition of an issue in a JIRA instance.
Configurations
| No. | Field Name | Description |
|---|---|---|
| 1 | Step Name | Name of the step. This name has to be unique in a single workflow. |
| Connection: | ||
| 1 | Base URL | For on-premise JIRA instance specify IP/Fully Qualified Domain Name/Hostname:Port of the JIRA Server (e.g. xxx.xxx.xxx.xxx:Port). Port can be optional as per network configuration. In case of Cloud instance specify the JIRA instance URL (e.g. https://xxxx.atlassian.net/). |
| 4 | Username | A username with appropriate permissions to authenticate to JIRA instance and perform a transition. This field is mandatory. |
| Password | ||
| 5 | Accept Value as variable/static | Leave checkbox unchecked to accept Password value from a field in the previous steps of the stream using a drop down list. Else enable checkbox for Password field to appear as Text box. |
| 6 | Password/API Key | Password can be entered as Text (for static value or environment variable) and Combo (drop down containing values from previous steps). This field is mandatory. If checkbox above is enabled Password field appears as Text box and accepts static or variable values. Else if checkbox above is disabled Password field appears as a drop down to select fields from previous steps. Provide an API Key in case of on cloud instance. Note: Following is the link to find the steps to generate token for on-cloud JIRA instance: https://confluence.atlassian.com/cloud/api-tokens-938839638.html |
| 7 | Test Connection | Verifies whether the connection is established or not. Note: For the purpose of verification fields coming from previous steps are not allowed since field values can only be accessed when workflow is in running state. Static values and environment variables are allowed. |
| Input Fields | ||
| 1 | Issue Key | Specify the Key of the issue on which transition is to be performed. Note: REST API can get maximum of 1000 and 100 issues for on-premise and on-cloud instances respectively. This is an intentional limitation on JIRA applications to avoid performance-related issues such as an OutOfMemoryException. |
| 2 | Button: Get | Click this button to get all Issue Keys available in the JIRA instance as per the access permission of Username provided in Connection. |
| 3 | Transition Name/ID | Specify the Name or ID of the transition to be performed. You may get the Name of the transition by clicking the Get button as described below. |
| 4 | Button: Get | Clicking on this button brings a dialog for all the Transitions Names possible for the provided issue. |
Note: Errors can be captured in the step error handling (right-click step and select error handling) to make the error message visible on AutomationEdge Requests.