Jira Service Management - Create Issue

Jira Service Management - Create Issue creates one incident in Jira Service Management for all of the assets retrieved from the saved query supplied as a trigger (or from the entities selected in the asset table).

General Settings

• Use stored credentials from Jira Service Management (Desk) adapter - Select this option to use the Jira Service Management connected adapter credentials. When you select this option, the Select Adapter Connection drop-down is available, and you can and you can choose which adapter connection to use for this Enforcement Action.

Required Fields

These fields must be configured to run the Enforcement Set.

1. Request description - Specify a description for the request.
2. Request summary - Specify a summary for the created issue.
   NOTE

   You can replace text with parameters that can provide specific information to the Jira Service Management incident.
   The following parameters can be used:
   {{HOSTNAME}}, {{USERNAME}}, {{FIRST_NAME}}
3. Issue type - Indicate the issue type.
4. Service Management (Desk) key - Specify or select the desired project in Jira Service Management where the issue will be created.
5. Instance Name - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

Additional Fields

These fields are optional.

1. Host Name or IP Address - The hostname or IP address of the Jira Service Management server.

2. Jira Service Management API version - Specify the Jira Service Management API version.

3. User name and API Token - The credentials to connect to Jira Service Management.

4. Verify SSL - Select to verify the SSL certificate offered by the host supplied in Service Desk domain. For more details, see SSL Trust & CA Settings.

5. HTTPS Proxy - A proxy to use when connecting to the value supplied in Host Name or IP Address.

6. HTTPS Proxy User Name - The user name to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.

7. HTTPS Proxy Password - The password to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.

15. Use Cloud API - Select this option to explicitly specify that the enforcement should use the Cloud API instead of Jira Server API. When the user uses the cloud API the default host name or IP address should be https://api.atlassian.com. Even when left unselected, the action will attempt to use the cloud API if the domain specified is “api.atlassian.com”.
16. Assignee Name - Enter a user name to which to assign the incident.
17. Custom fields (JSON format) - Custom fields to add to this incident described in JSON format.
    Note:

    If a custom field is already configured by this Enforcement Action, the new custom value is ignored.
18. Add default incident description (optional) - Select whether to send the incident description to Jira Service Management.
    Message example:
    Alert - "test" for the following query has been triggered: Missing Sophos

_Alert Details_
_The alert was triggered because: The number of entities is above 0
The number of devices returned by the query:4
The previous number of devices was:4_

_You can view the query and its results here: https://demo-latest.axonius.com/devices?view=Missing Sophos_ 

18. Send CSV data (required, default: False)
    * If enabled, the created issue will include an attached CSV file with the query results.
    * If disabled, the created issue will not include an attached CSV file with the query results.

Permissions

To perform this action you need to create a user with action privileges.