Jira Service Management - Create Ticket per Asset

Jira Service Management - Create Ticket per Asset creates an incident in ServiceDesk for each entity retrieved from the saved query supplied as a trigger (or from the entities selected in the asset table).

Details for all devices are included in the ticket message as well as the CSV.

General Settings

• Use stored credentials from Jira Service Desk adapter - Select this option to use the first connected Jira Service Management adapter credentials. When you select this option, the Select Adapter Connection drop-down is available, 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.

• Request description - Enter a description for the request.

• Request summary - Enter a summary for the created issue.

  Note:

  You can replace text with parameters that can provide specific information to the Service Desk incident.
  The following parameters can be used:
  {{HOSTNAME}}, {{USERNAME}}, {{FIRST_NAME}}

• Issue type - Indicate the issue type.

• Service Management (Desk) key - Specify the desired project in Service Desk where the issue will be created.

• Compute Node - 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.

• Include missing adapters in description - Select to add to the description of the issue all the adapters that aren’t connected to the asset.

• Add asset fields to issue description - Select to add a list of fields from the asset entity to the description of the issue.

• Add asset description to issue description - Select to add the aggregated ‘description’ field from the asset to the issue description.

• Add asset host name to issue description - Select to add the aggregated hostname field value to the description of the issue.

• Add fields to issue description - Select field values to add to the description of the issue. You can select multiple additional fields. The values of the selected fields are added to the Request description.

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

• Map Axonius fields to adapter fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.

  Note:

  For details, see Axonius to External Field Mapping.

• Send CSV data - Select to include a CSV file with the query results in the issue created. For Vulnerabilities the first row shows the vulnerability information, and the next rows show the linked devices.

Permissions

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