Create Jira Issue
  • 3 Minutes To Read
  • Print
  • Share
  • Dark
    Light

Create Jira Issue

  • Print
  • Share
  • Dark
    Light

The Create Jira Issue action takes the saved query supplied as a trigger (or devices that have been selected in the asset table) and creates an issue in your Jira server for all relevant entities.

NOTE

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

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

image.png

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.

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



For more details on other Enforcements available actions, see Action Library.
For more details on Enforcement Set configuration, see Enforcement Set configuration.

Was This Article Helpful?