Jira - Create Issue
  • 19 May 2024
  • 6 Minutes to read
  • Dark
  • PDF

Jira - Create Issue

  • Dark
  • PDF

Article summary


This Enforcement Action has been deprecated from Axonius version 6.0.10. Use Jira Service Management - Create Ticket instead.

Jira - Create Issue 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). This is used for Jira ServiceDesk without Insight.
:::(Info) (NOTE)
To create a separate Jira issue for each entity, use the Create Jira Issue Per Asset action.

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

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

General Settings

  • Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
  • Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
  • Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
  • Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
  • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

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.

  • Project Key (required) - Specify or select the desired project in Jira where the issue will be created.
  • Issue type (required) - Specify or select the issue type for the created issue.
  • Summary (required) - Specify a summary for the created issue.
  • Description (required) - Specify a description for the created issue.
  • 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.

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

    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

  • 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
      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.
  • 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.
  • 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.
  • 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.
  • 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.
    • <<ISSUE_LINK>> - will include the Jira issue URL.

    Additional CSV Settings

    • Split by asset entities - 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. If you do not select this option, all values on a device are in the same cell on the CSV file.
    • Split by field values - 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.
    • Don't split complex objects into columns - 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.
    • Export CSV delimiter to use for multi-value fields (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.
    • Maximum rows (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. (note that this value is the maximum value supported by Excel, setting a higher value generates a file that can't be displayed fully or correctly in Excel)
    • Include associated devices (only for Vulnerabilities and Software) - For Software and Vulnerabilities queries. Toggle on this option to include the associated devices with the preferred hostname as a predefined field for each software or vulnerability. When you create a CSV file with associated devices (for Vulnerabilities or Software), if the exported query results are larger than the value set under Maximum rows (or the default value of 1048500), an appropriate notice is displayed at the end of the CSV file.
    • Include Associated fetch events (only for Fetch History) - For Adapter Fetch History queries, select this option to include details of the associated Fetch Events in the CSV file that is created.
    • Device fields - This option is available for Software and Vulnerabilities. Select the device fields to add. By default Preferred Host Name is selected. Click add to select more fields. At least one field must be selected. Once you select fields, you can drag and drop to rearrange in the order that you want them to appear in the CSV file. Click the bin icon to remove a device field.

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.

For more details about other Enforcement Actions available, see Action Library.

Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
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.