On this page
|Table of Contents|
This Snap provides the functionality to execute HTTP Post method to a JIRA REST API service endpoint to link JIRA issues.
For more information about the JIRA Issue Link API, refer to the official JIRA Rest API document for the Link Issue Resource.
The user must have the link issue permission in JIRA.
|Support and limitations:||Ultra pipelines: |
Works in UltraPipelines.Spark mode: Not supported in Spark mode
This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. The Snap supports the JIRA basic auth account. The JIRA sites may or may not allow anonymous access.
|The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.|
The JIRA REST API version number.
Default value: 2
You will likely want to use a Mapper Snap before the JIRA IssueLink Snap to see the target schema being requested and to map the appropriate fields or parameters.
The following image shows the schema of the JIRA IssueLink Snap inside the Mapper Snap:
The following sections describe common values that you might use when linking issues.
Use the JIRA Get issue link type API for your list of link types.
|Type||Inward issue note||Outward issue note|
|Blocks||is blocked by||blocks|
|Cloners||is cloned by||clones|
|Duplicate||is duplicated by||duplicates|
|Problem/Incident||is caused by||causes|
The value for the comment body must be a string.
If not specified, comments are visible to anyone with access to the issue. When specified, visibility type is usually set to role or group. The value is then set to the string containing the name of the preferred object.
- Use the get project roles API to return a list of JIRA roles.
- Use the find groups API to return a list of JIRA groups.