steps

jiraGetComponentIssueCount This step queries a particular component’s issue-count. Input id - componentId. 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_component_issue_count 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. »

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. »

jiraGetProjectStatuses This step queries all the statuses of a particular project. Input idOrKey - project 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_project_statuses 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. »

jiraGetProjectVersions This step queries all the versions of a particular project. Input idOrKey - project 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_project_versions 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. »

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. »

jiraDeleteIssueLink This step deletes an issue link. Input id - issue link’s 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_delete_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. »

jiraGetIssueTransitions This step queries all transitions of a particular issue. 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_transitions 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. »