Jira Service Management - Update Tickets

💡

Note

This Enforcement Action requires the Jira Service Management (JSM) Standard, Premium, or Enterprise license.

Jira Service Management - Update Tickets updates the relevant tickets for:

• Assets matching the Enforcement Set query or assets selected on the relevant asset page. For example, if the action is triggered on asset type=Users, the action updates tickets linked to each user.
  • When triggered on any asset type except Tickets (for example, Users, Devices), this action updates related ServiceNow tickets based on your selection in the Select Which Related Tickets To Update dropdown (see below).
  • When triggered on asset type=Tickets, this action runs on all tickets resulting from the selected query. The Select Which Related Tickets To Update dropdown is not applicable in this scenario.

Required Fields

These fields must be configured to run the Enforcement Set.

• Use stored credentials from Jira Service Management (Service Desk) adapter - Select this option to use the Jira Service Management connected adapter credentials.

  • When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.

📘

Note

To use this option, you must successfully configure a Jira Service Management (Service Desk) adapter connection.

• Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Ticket Main Settings

These fields are optional.

• Ticket Status - Select a value for ticket status.

• Ticket Assignee - Enter to whom the ticket is assigned.

• Ticket Comments - Enter comments related to the ticket.

Ticket Additional Settings

These fields are optional.

• Map Axonius fields to vendor fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way, you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.

  📘

  Note:

  For details, see Axonius to External Field Mapping.

Connection and Credentials

These fields are optional.

💡

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

• Host Name or IP Address -The hostname or IP address of the Jira Service Management server.

• Jira Service Management API version - The Jira Service Management API number.

• User Name and API Token - The credentials for a user account that has the permissions to read and write.

• Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

• HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

• HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

• HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

• Use Cloud API - Select this option to explicitly specify that the enforcement should use the Cloud API instead of Jira Server API. When the user is using the cloud API the default host name or IP address should be https://api.atlassian.com. Even when left unselected, the action will attempt to use the cloud API if the domain specified is “api.atlassian.com”.

• Gateway Name - Select the Gateway through which to connect to perform the action.

Additional Fields

• Additional fields (json format) - 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"}

Permissions

• Action privileges

---