Issue :: Create
Summary
Creates a JIRA Issue using the asynchronous request queue. Retries are automatically handled. A JIRA Record Linkage is created/updated after a successful response from JIRA.
Action Inputs
Connector
connector
Reference (Reference: Jira Connector)
No
[optional] The sys_id of the connector to use in the process. If this is blank, the default connector is used.
Issue Body
issue_body
String
No
[optional] Issue body JSON. This can be leveraged to submit data for custom fields or other items not available as inputs to the action. If the same field is used in the Issue Body as is used in the inputs to the action, the action input will overwrite the value supplied in the Issue Body. Action inputs for JIRA data will automatically be added to the Issue Body, if supplied.
Record SysId
record_sysid
String
No
The SYS_ID of the record in ServiceNow that will be associated to the JIRA Issue we are creating
Record Table
record_table
String
No
The table of the record in ServiceNow that the Record SysId belongs to
No Attachment Sync
no_attachment_sync
True/False
No
Do we avoid synchronizing any already existing attachments to the record upon creation.
Remote Web Links
remote_web_links
String
No
[optional] Add links to the Issue upon creation. Format is: [{"title":"The Label for my Link","url":"
Execute ASAP
execute_asap
True/False
No
[optional] Whether to run this as an asynchronous business rule when the record gets created or wait for the job to pick it up in relative order on the queue
Summary
summary
String
No
[optional] String to set on the 'Summary' field on the issue in JIRA
Description
description
String
No
[optional] String to set on the 'Description' field on the issue in JIRA
Project
project
Reference (Reference: Jira Project)
No
[optional] the Project record that directs what Project should be set to on the Issue in JIRA. This is required if it is not already specified in the "Issue Body"
Issue Type
issue_type
Reference (Reference: Jira Issue Type)
No
[optional] the Issue Type record that directs what issue type should be set to on the Issue in JIRA. This is required if it is not already specified in the "Issue Body"
Initial Comment
initial_comment
String
No
[optional] String to use for adding a comment to the issue in JIRA
Custom Field 1 Name
cf1_name
String
No
[optional] Set a particular custom field. This is the name of the field (eg. customfield_115002)
Custom Field 1 Type
cf1_type
Choice
No
[optional] The type of the custom field you are setting. This is only applied when "Custom Field 1 Name" has a value
Custom Field 1 Value
cf1_value
String
No
[optional] The value of the field set by "Custom Field 1 Name" field.
Action Outputs
Linkage
linkage
Reference (Reference: Jira Record Linkage)
No
The JIRA Linkage record that ties the issue to a SN record.
Request
request
Reference (Reference: Async Request Queue)
No
The original asynchronous request queue record used to make the request
Success
success
True/False
No
Whether the communication and response was as expected
Log
log
String
No
Scripted log statements of activities that took place during the operation of this activity
Retry Request
retry_request
Reference (Reference: Async Request Queue)
No
If there were Retries used in the process, the last retry record is returned
Issue JSON
issue_json
String
No
The resulting JSON representation of the JIRA Issue
Notes
This action belongs to the JIRA Request Queue category.
This action includes reference fields that link to other tables in ServiceNow:
references the table.
references the table.
references the table.
This action returns 6 output(s) that can be used in subsequent flow steps.
Example Usage
Example 1: Basic Usage
This example demonstrates how to use the action with typical inputs.
Input:
Output:
In this example, the action processes the provided inputs and returns the appropriate outputs. The actual values returned will depend on the specific functionality of this action and the input values provided.