Comment :: Add
Summary
Adds a comment to a JIRA issue using the asynchronous request queue. Retries are automatically handled.
Action Inputs
Linkage
linkage
Reference (Reference: Jira Record Linkage)
No
[optional] The JIRA Linkage record that ties an issue to a SN record.
Issue ID or Key
issue_id_or_key
String
No
[optional] The JIRA issue ID or Key of the issue to retrieve (This is only used if 'linkage' is not set)
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.
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
Comment String
comment_string
String
No
[optional] the comment string to insert into the JIRA Issue. This is required if Comment Body is not set.
Comment Body
comment_body
String
No
[optional] the JSON representation of the comment body as per the API. This gives you more precise control over the comment, if desired. This is required if Comment String is not set.
Expansion Options
expansion_options
String
No
A CSV string of expansion options for this operation. (eg. renderedBody)
Action Outputs
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
Response JSON
string
String
No
The JSON string returned from the API call
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.
This action returns 5 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.