Jira Service Management - Create Ticket

Jira Service Management - Create Ticket creates one incident in Jira Service Management for:

• Each asset returned by the selected query or assets selected on the relevant asset page.

Required Fields

These fields must be configured to run the Enforcement Set.

• Use stored credentials from Jira Service Management (Service Desk) adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
  • 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.
  Note:

  To use this option, you must successfully configure a Jira Service Management adapter connection.
• Request description - Specify a description for the request.
• Request summary - Specify a summary for the created issue.
• Issue type - Indicate the issue type.
• Service Management (Desk) key - Specify or select the desired project in Jira Service Management where the issue will be created.
• 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.

• 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”.

• Use full URL - Select this option if the URL references to a specific endpoint. For example: https://my-jira.com/jira.

• Assignee - Enter a user name or email address to which to assign the incident. It is recommended to use the user's email address.

• Use assignee name instead of ID - When Assignee has a value, Jira Service Management will search for the assignee by username or email address, depending on which is entered. When not selected, enter the user ID in the Assignee field.

• Labels - Comma separated labels that will be added to the tickets.

• Components - Comma separated components that will be added to the tickets.

• Custom fields (JSON format) - Custom fields to add to this incident described in the following JSON format: {"customfieldXYZ":{"value":"VALUE YOU WANT"}} or {"customfieldXYZ"{"id""ID YOU WANT"}}

  Note:

  If a custom field is already configured by this Enforcement Action, the new custom value is ignored.

• Send created issue link to webhook URL - Specify the webhook URL the created Jira Service Management issue link will be sent instead of Jira Service Management. Axonius will send the message specified in the Webhook content field to the specified webhook URL.

• Webhook content - Specify the webhook content in JSON format. This content will be sent to the specified webhook URL.

  NOTE

  • The default content is: {"text": "Created issue link is:<<ISSUE_LINK>>"}
  • <<ISSUE_LINK>> - will include the Jira Service Management issue URL.

• Related parent ticket key - Enter the key of the related parent ticket. The key usually includes the project key (string) and a sequential number, for example, "CT-1960".

• Add default incident description - 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

• Add a summary line of each Asset to the Description - When selected, adds a one line summary for each asset included in the ticket.

• Send CSV data - When selected, a CSV file with the query results is attached to the ticket.

Required Permissions

• Action privileges