Jira Service Management - Notify Issue

Jira Service Management - Notify Issue sends a notification about a Jira issue to specified recipients for:

• Assets returned by the selected query or assets selected on the relevant asset page.

Required Fields

These fields must be configured to run the Enforcement Action.

• Use stored credentials from the Jira Service Management (Service Desk) adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.

  • When you select this option, the Select Adapter Connection drop-down becomes available. Select the 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.

• Issue ID or Key - The ID or key of the Jira issue to send the notification about. It is recommended to use Dynamic Values to populate this field.

  • Example: 12345 or ABC-123

• Notification subject - Subject of the notification.

  • Example: Please take note of this issue

• Notification message body - Body of the notification message.

  • Example: This is a notification message.

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

Additional Fields

These fields are optional.

• Account IDs to Notify - List of Jira account IDs to notify.

• Email addresses to notify - List of email addresses to notify.

• Group names to notify - List of Jira group names to notify.

• Notify Assignee - Select to notify the assignee of the issue.

• Notify Reporter - Select to notify the reporter of the issue.

• Notify Watchers - Select to notify the watchers of the issue.

• Notify Voters - Select to notify the voters of the issue.

💡

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 of your Jira instance (for example, https://<your_atlassian_site_name>.atlassian.net/). The domain must include the https:// prefix and end with a trailing slash /.

• User Name - The email address associated with your Jira account.

• API Token - The API token for authentication. Generate an API token from your Atlassian Account Security settings.

• Jira Service Management API version - The API version to use (default: 1.0).

• 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 - The HTTPS proxy server address (for example, http://proxy.example.com:8080).

• HTTPS Proxy User Name and HTTPS Proxy Password - The credentials for the HTTPS proxy server, if required.

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

APIs

Axonius uses the Jira Cloud Platform REST API - POST /rest/api/latest/issue/{issueIdOrKey}/notify

Required Ports

Axonius must be able to communicate via the following ports:

• TCP port 80/443

Required Permissions

• Browse Projects permission - To access the Jira issue.
• Edit Issues permission - To send notifications about the issue.
• The user account must have access to the project containing the issue.
• Recipients specified by account ID, email, or group name must have valid Jira accounts or permissions to receive notifications.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.