Link Issues
Description
This step creates a link between two issues in Jira. You provide the source issue key, the target issue key, and the link type (such as "blocks," "is blocked by," or "relates to"). Use this step in workflows that connect related issues, track dependencies between tasks, or link incidents to their root cause.
Configurations
| Field Name | Description |
|---|---|
| Step Name | Name of the step. This name has to be unique in a single workflow. |
Connection
For the connection field details, click Connection Fields
Input tab
| Field Name | Description |
|---|---|
| Input Fields | |
| Issue Key | Specify the issue key of the JIRA for which comment is to be added. JIRA automatically assigns this key when the issue is created (for example, PROJ-123). The field accepts environment variable or previous step field, and the field is mandatory. Note: To prevent performance issues, such as OutOfMemoryException, JIRA limits the number of returned issues: • On-premise (Server/Data Center): Up to 1,000 issues • JIRA Cloud: Up to 100 issues |
| Get | Click Get to select an issue key. The system opens a pop-up that lists the JIRA projects accessible to the configured user. After you select a project, the next pop-up displays the available issues. Select the required issue key from the list. |
| 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. |
| Get | Clicking on this button brings up the available Issue Link Types. |
| Issue Key to be linked | The Key of the outward issue with which the link is to be created. |
| Get | Clicking on this button brings up the issue keys available as per the access permission of Username provided in Connection. |