Jira Service Management - Create Issue per Asset

Jira Service Management - Create Issue per Asset (Jira Service Desk - Create Issue 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).

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.

1. Request description - Enter a description for the request.

2. 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}}

3. Issue type - Indicate the issue type.

4. Service Management (Desk) key - Specify the desired project in Service Desk 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.

   NOTE

   If Use stored credentials from the Service Management adapter is disabled, these fields are required.

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.

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

9. Assignee Name - Enter a user name to which to assign the incident.

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

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

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

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

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

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

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