Create Jira Issue
  • 20 Sep 2022
  • 5 Minutes to read
  • Dark
    Light
  • PDF

Create Jira Issue

  • Dark
    Light
  • PDF

Create Jira Issue Incident creates an issue in your Jira server for all the entities retrieved from the saved query supplied as a trigger (or from the entities selected in the asset table).

NOTE

To create a separate Jira issue for each entity, use the Create Jira Issue Per Entity action.

To configure Create Jira Issue, from the Action Library, click Create Incident, and then click Create Jira Issue.

Connection Settings

Click to view Connection Settings

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

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 key
  • Alternative Verify SSL
  • Alternative Use assignee name instead of ID - Refer to Jira Settings for explanations of these parameters.
  • Instance name - Select the Axonius node to connect to, to run this action.

Action Settings

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

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

    NOTE

    This field is relevant only for Create Jira Issue per Entity action and is not part of the Create Jira Issue action settings.

  6. Add default incident description (required, default: False) - Select whether to add the incident description to the created Jira issue.

    • If enabled, Axonius will include the default incident description Jira issue.

    • If disabled, Axonius will not include the default incident description Jira issue.

      NOTE

      This field is relevant only for Create Jira Issue action and is not part of the Create Jira Issue Per Entity action settings.

    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

  7. 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.
  8. 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.
  9. 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.
    NOTE

    This field is relevant only for Create Jira Issue action and is not part of the Create Jira Issue Per Entity action settings.

  10. Send created issue link to webhook URL (optional, default: empty) - Specify the webhook URL the created Jira issue link will be sent.

    • If supplied, Axonius will send the message specified in the Webhook content field to the specified webhook URL.
    • If not supplied, Axonius will only create the Jira issue.
    NOTE

    This field is relevant only for Create Jira Issue action and is not part of the Create Jira Issue Per Entity action settings.

  11. Webhook content (optional, default: {"text": "Created issue link is:<<ISSUE_LINK>>"}) - Specify the webhook content in a JSON format.

    • If supplied, Axonius will send the specified content to the specified webhook URL.
    • If not supplied, Axonius will only create the Jira issue.
    NOTE
    • <<ISSUE_LINK>> - will include the Jira issue URL.
    • This field is relevant only for Create Jira Issue action and is not part of the Create Jira Issue Per Entity action settings.

Additional CSV Settings

  1. Split by asset entities (required, default: false) - Select to create a CSV file where each asset on a device is shown as a separate row. This separates each asset as the 'expand' option in the application. It separates each asset by its entity. For example, you will be able to know which values were fetched from each adapter connection.
    a. If supplied, each value on a device or user is shown as a separate row.
    b. If not supplied all values on a device are in the same cell on the CSV file.
  2. Split by field values (optional, default empty) - Choose field value - For complex fields and lists you can create a CSV file where the values of complex fields and lists are represented as separate rows in the file. From the drop-down box select the value that you want to display in the file, 'Tags' for instance. Only fields that have been discovered are available. For example, if you export by Installed Software, you will be able to see each installed Software name and its version.
  3. Don't split complex objects into columns (optional, default: false) - When selected, complex objects appear in a single column in JSON format. By default, each field in a complex object is split into a separate column in the CSV file.
  4. Export CSV delimiter to use for multi-value fields (optional, default: Export CSV delimiter to use for multi-value fields field under the System Settings section in the GUI Settings) - Specify a delimiter to separate between values within the same field of an exported CSV file, otherwise the delimiter defined in Export CSV delimiter to use for multi-value fields is used.
  5. Maximum rows (optional, default: 1048500) - Specify the maximum number of rows to be included in the CSV file. When you set a value here the generated CSV file will include the top x rows, based on the specified values. Otherwise, the generated CSV file will include the default maximum rows, set as 1048500.


To learn more about configuring Enforcement Sets, see Configuring Enforcement Sets.


First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.