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
| 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 |
|---|---|
| Accept Update fields as JSON | Enable checkbox to accept the fields to be updated in JSON format. |
| 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. |
| 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. |
| Static Field Name | Clicking on this column field brings a dialog with the list of available fields to create an issue. |
| 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 tab
| Field Name | Description |
|---|---|
| ID | Output field to hold the ID of the issue created on successful plugin execution. The mandatory fields depend on the particular instance configurations. |
| 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. |