Link Issues
Description
Jira Link Issues Plugin step creates a link between two issues in an instance of JIRA software.
Configurations
| No. | Field Name | Description |
|---|---|---|
| 1 | Step Name | Name of the step. This name has to be unique in a single workflow. |
| Connection | ||
| 2 | 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/). |
| 3 | Username | A username with appropriate permissions to authenticate to JIRA instance and get issue. This field is mandatory. |
| 4 | Password | |
| 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. | |
| 5 | Password/API | Provide password of the username to authenticate in case of on premise instance and API Key in case of on cloud instance Password/API is entered using a widget. The widget handles both Text (static value or environment variable) and Combo (drop down containing values from previous steps). This field is mandatory. If checkbox above is enabled Password/API 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. 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 |
| 6 | 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 | The Key of the inward issue for which link is to be created. The issue key can be chosen from a pop-up obtained by clicking the Get button next to it as described below. Note: REST API returns maximum of 1000 and 100 issues for on-premise and on-cloud instance respectively. This is an intentional limitation on JIRA applications to avoid performance-related issues such as an OutOfMemoryException. |
| 2 | Get | Clicking on this button brings up the issue keys available as per the access permission of Username provided in Connection. |
| 3 | Issue Link Type | Type of the link to be created between the two issues. Following are the issue link types, - is duplicated by - duplicates - clones - relates to - blocks - is cloned by - is blocked by The issue link type can be chosen from a pop-up obtained by clicking the Get button next to it as described below. |
| 4 | Get | Clicking on this button brings up the available Issue Link Types. |
| 5 | Issue Key to be linked | The Key of the outward issue with which the link is to be created. |
| 6 | Get | Clicking on this button brings up the issue keys available as per the access permission of Username provided in Connection. |