Create Issue
Description
“Jira Create Issue” plugin step creates an issue in an on-premise or on-cloud version of a JIRA instance.
Limitation:
The following fields are unsupported: Time Tracking, Original Estimate, and Remaining Estimate.
Note: Supported format for Date type fields, such as Due Date is ‘YYYY-MM-DD’.
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 create issue. This field is mandatory. |
| Password | ||
| 4 | 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 Key | Password can be entered as Text (for static value or environment variable) and Combo (drop down containing values from previous steps). This field is mandatory. If checkbox above is enabled Password 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. Provide an API Key in case of on cloud instance. 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 | Accept Update fields as JSON | Enable checkbox to accept the fields to be updated in JSON format. |
| 2 | Update fields JSON | Select the field in the stream containing the JSON text. Sample JSON is shown below. {“Summary”:”sumaryfromAE”,”Project”:”SP”,”Priority”:”Medium”,”description”:”Dec from AE”,”Issue Type”:”Bug”} The JSON field can be any field in the stream or can be created using any step such as Generate Rows, Modified Java Script, Set field value to a constant etc. |
| Tabular Fields | ||
| 3 | Variable Field Name | This is an optional field. Choose a field in input stream from drop down list or provide a user or system defined variable. |
| 4 | Static Field Name | Clicking on this column field brings a dialog with the list of available fields to create an issue. |
| 5 | Field Value | Specify a Field value to hold the value of field name selected in Field Name column above. All the mandatory fields for creating an issue for a particular instance must be selected and the field values should be provided else the workflows throw error mentioning the mandatory field that is missing. |
| Output Fields | ||
| 1 | ID | Output field to hold the ID of the issue created on successful plugin execution. The mandatory fields depend on the particular instance configurations. |
| 2 | Key | Output field to hold the key of the issue created on successful plugin execution Errors can be captured in the step error handling (right-click step and select error handling) to make the error message visible on AutomationEdge Requests. |