issue

jiraGetRemoteIssueLink This step queries a particular remote link of an issue. Input idOrKey - issue id or key. linkId - remote link id. site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. Output Each step generates generic output, please refer to this link for more information. The api response of this jira_get_remote_issue_link step can be reused later in your script by doing response.data.required_field_name. You can see some example scenarios here All the available fields for a jira response can be found in JIRA API documentation depending on your JIRA version. »

jiraNewIssues This step creates new issues in bulk in the provided JIRA site. Input issues - issues to be created. site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. auditLog - Optional. default: true. Append a panel to the comment with the build url and build user name. Output Each step generates generic output, please refer to this link for more information. The api response of this jira_new_issues step can be reused later in your script by doing response. »

jiraDeleteAttachment This step deletes the attachment from an issue. Input id - Attachment Id. site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. Output Each step generates generic output, please refer to this link for more information. The api response of this step can be reused later in your script by doing response.data.required_field_name. You can see some example scenarios here All the available fields for a JIRA response can be found in JIRA API documentation depending on your JIRA version. »

jiraAssignIssue This step assigns a particular issue to a user. Input idOrKey - Issue id or key. userName - username of the person who should be added as a watcher. accountId - accountId of the person who should be added as a watcher. Only applicable for GDPR instances. site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. Output Each step generates generic output, please refer to this link for more information. »

jiraEditComment This step updates a particular comment on particular issue. Input idOrKey - Issue id or key. commentId - comment id. input - comment, supports jira wiki formatting. site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. Deprecated: comment - comment, supports jira wiki formatting. Output Each step generates generic output, please refer to this link for more information. The api response of this jira_edit_comment step can be reused later in your script by doing response. »

jiraGetIssue This step queries a particular issue from the provided JIRA site. Input idOrKey - Issue id or key. site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. Output Each step generates generic output, please refer to this link for more information. The api response of this jira_get_issue step can be reused later in your script by doing response.data.required_field_name. You can see some example scenarios here All the available fields for a jira response can be found in JIRA API documentation depending on your JIRA version. »

jiraGetRemoteIssueLinks This step queries all the remote links of a particular issue. Input idOrKey - issue id or key. globalId - global application id (Optional). site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. Output Each step generates generic output, please refer to this link for more information. The api response of this jira_get_remote_issuelinks step can be reused later in your script by doing response. »

jiraNewRemoteIssueLink This step creates a new remote link to a particular issue. Input idOrKey - issue id or key. remoteLink - remote link. site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. Output Each step generates generic output, please refer to this link for more information. The api response of this jira_new_remote_issuelinks step can be reused later in your script by doing response.data.required_field_name. You can see some example scenarios here All the available fields for a jira response can be found in JIRA API documentation depending on your JIRA version. »

jiraEditIssue Updates an existing issue based on given input, which should have some minimal information on that object. Input idOrKey - issue id or key. issue - issue to be updated. queryParams - Optional. Map of query parameters. site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. Output Each step generates generic output, please refer to this link for more information. The api response of this jira_edit_issue step can be reused later in your script by doing response. »

jiraLinkIssues This step links two issues in the provided JIRA site. Hint: Try getIssueLinkTypes to know the type. Input type - type of the link. (Ex: Relates, Blocks, Cloners, Duplicate) inwardKey - inward issue key. outwardKey - outward issue key. site - Optional, default: JIRA_SITE environment variable. failOnError - Optional. default: true. Output Each step generates generic output, please refer to this link for more information. The api response of this jira_link_issues step can be reused later in your script by doing response. »