Create Jira Service Desk Incident per Entity
  • 18 May 2022
  • 3 Minutes to read
  • Dark
    Light
  • PDF

Create Jira Service Desk Incident per Entity

  • Dark
    Light
  • PDF

The Create Jira Service Desk Incident per Entity action 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).

To configure the Create Service Desk Incident per Entity action, from the Action Library, click Create Incident, and then click Create Jira Service Desk Issue per Entity.

Connection Settings

  1. Use stored credentials from the Service Desk adapter (required, default: False) - Select this option to use the first connected Service Desk adapter credentials.
NOTE
To use this option, you must successfully configure an Atlassian Jira Service Desk adapter connection.
  1. Service Desk key (required) - Specify or select the desired project in Service Desk where the issue will be created.
    NOTE
    If Use stored credentials from the Service Desk adapter is disabled, this field is required.
  2. Request type (required) - Indicate the request type.
  3. Add full device content (required) - Adds all data on the specific entity to the incident.
  4. Add device description (required) - Adds a description of the device to the incident.
  5. Request summary (required) - Specify 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}}
  6. Request description (required) - Specify a description of the request.
  7. Additional description fields (optional) - Select additional fields from the list. You can select multiple additional fields. The values of the selected fields are added to the Request description.
  8. Assignee name (optional) - Assign the incident to the indicated user.
  9. Custom fields (JSON format) (optional) - 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.
  10. Host Name or IP Address (optional) - The hostname or IP address of the Jira Service Desk server.
  11. Version (optional, default: empty) - Specify the version type.
  12. User name and Password (optional) - To connect to Service Desk you will need to create a user with action privileges.
NOTE
If Use stored credentials from the Service Desk adapter is disabled, these fields are required.
  1. Verify SSL (required) - Verify the SSL certificate offered by the host supplied in Service Desk domain. For more details, see SSL Trust & CA Settings.
    • If enabled, the SSL certificate offered by the host will be verified against the CA database inside of Axonius. If it fails validation, the connection will fail with an error.
    • If disabled, the SSL certificate offered by the host will not be verified against the CA database inside of Axonius.
  2. HTTPS Proxy (optional) - A proxy to use when connecting to the value supplied in Host Name or IP Address.
    • When supplied, Axonius uses the proxy when connecting to the value supplied in Host Name or IP Address.
    • When not supplied, Axonius connects directly to the value supplied in Host Name or IP Address.
  3. HTTPS Proxy User Name (optional) - The user name to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.
    • When supplied, Axonius authenticates with this value when connecting to the value supplied in HTTPS Proxy.
    • When not supplied, Axonius does not perform authentication when connecting to the value supplied in HTTPS Proxy.
  4. HTTPS Proxy Password (optional) - The password to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.
    • When supplied, Axonius authenticates with this value when connecting to the value supplied in HTTPS Proxy.
    • When not supplied, Axonius does not perform authentication when connecting to the value supplied in HTTPS Proxy.

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.