Jira - Create Issue per Asset

Jira - Create Issue per Asset creates an an issue in your Jira server for each entity retrieved from the saved query supplied as a trigger (or from the entities selected in the asset table) .

This is for Asset Management with Insight.

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

General Settings

To use this action, you must enable the Use Jira setting and configure your Jira server. For more details, see Configuring Jira Settings.

Required Fields

These fields must be configured to run the Enforcement Set.

1. Project Key (required) - Specify or select the desired project in Jira where the issue will be created.

2. Issue type (required) - Specify or select the issue type for the created issue.

3. Summary (required) - Specify a summary for the created issue.

   NOTE

   You can replace text with params that can assist you in better informing in the Jira Issues.
   The following params can be used:
   {{HOSTNAME}}, {{USERNAME}}, {{FIRST_NAME}}, {{LABELS}}

4. Description (required) - Specify a description for the created issue.

   NOTE

   You can replace text with params that can assist you in better informing in the Jira Issues.
   The following params can be used:
   {{HOSTNAME}}, {{USERNAME}}, {{FIRST_NAME}}, {{LABELS}}

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. Add full device content (required, default: False) - Add all the data on the specific entity to the ticket

2. Add device description - use the "Description" of the device in Axonius as the description of the ticket.

3. Multiple optional fields for the created issue (optional, default: empty)

   • Assignee - A single user to assign the tickets to
   • Labels - Comma separated labels that will be added to the tickets
   • Components - Comma separated components that will be added to the tickets
     NOTE

     Since the valid values of the different parameters are customer specific, Axonius does not validate any of those parameters values. You must make sure inserted values are correct, otherwise, the request might fail.

4. Additional fields (optional, default: empty) - Specify additional fields to be added as part of the incident as key/value pairs in a JSON format. For example: {"field1": "value1", "field2": "value2"}.

   • If supplied, Axonius will add the specified fields and values to the created issue. If one of the specified fields is invalid, the request might fail.
   • If not supplied, Axonius will not any additional fields to the created issue.

5. Axonius to Jira field mapping - Use this setting to map Axonius fields to the CMDB fields. The input should be key/value pairs in a JSON format.

For example: {axonius_field1:jira_field1, axonius_field2:jira_field2}

Alternative Jira Parameters
By default the system uses the Jira settings that are configured on the Global Configuration page. Use the Alternative parameters to set a different Jira server to override the default Jira Settings.
Set the following parameters:

• Alternative Jira domain
• Alternative User name
• Alternative API Token
• Alternative Verify SSL
• Alternative Use assignee name instead of ID - Refer to Jira Settings for explanations of these parameters.