Jira Software - Create Ticket Per Asset

Jira Software - Create Ticket Per Asset creates a Jira Software issue for each asset, 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 Software 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 an Atlassian (Formerly Atlassian Jira Software) adapter connection.

• Request Description - The body text for each issue. Plain text is automatically converted to Atlassian Document Format (ADF) on Jira Cloud.

• Request Summary - The title or summary for each issue. Supports Axonius template variables.

• Issue Type - The type of issue to create. For example, Bug, Task, Story, or Epic.

• Project Key - The project key for the Jira project where each issue is created. For example, OPS or DEV.

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

💡

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.

• Domain - The full URL of the Jira instance. For example, https://your-instance.atlassian.net (Cloud) or https://jira.on-prem.com (On-Prem).

• User Name - The Jira user account name or Client ID for OAuth authentication. The credentials for a user account that has the Required Permissions to perform this Enforcement Action.

• API Token - The API token or Client Secret. For Cloud, generate a token at https://id.atlassian.com/manage-profile/security/api-tokens. For On-Prem, use a personal access token.

• Jira API Version - The version of the Jira REST API to use:

  • v3 - Jira Cloud and Data Center (recommended)
  • v2 - Jira Data Center and On-Prem

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

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

• Assignee - The user display name, email address, or account ID to assign to each issue. Axonius resolves the value using the Jira user search API.

• Use Assignee Name Instead of ID - Enable this option to assign issues by user display name or email address. When disabled, the value in Assignee is treated as an account ID.

• Labels - A comma-separated list of labels to add to each issue.

• Components - A comma-separated list of component names to associate with each issue.

• Include Missing Adapters in Description - Enable this option to include adapters with no data in the issue description.

• Use Full URL - Enable this option to include the full URL in issue links.

• Add Asset Fields to Issue Description - Enable this option to append a list of asset fields to the issue description.

• Add Asset Description to Issue Description - Enable this option to append the aggregated asset description field value to the issue description.

• Add Asset Host Name to Issue Description - Enable this option to append the aggregated hostname field value to the issue description.

• Send CSV Data - Enable this option to attach a CSV file of the affected asset's data to the issue.

• Add Fields to Issue Description - Select asset fields (IP address, domain, hostname) to append to the issue description.

• Map Axonius Fields to Fields in the Description - A JSON mapping of Axonius field paths to description field labels. Use this to add custom Axonius field values to the issue description.

• Custom Fields (JSON Format) - Additional Jira fields as a JSON object to include in each issue. For example: {"priority": {"name": "High"}, "labels": ["Axonius"]}.

• Axonius to Jira Field Mapping - A JSON mapping of Axonius fields to Jira fields. Supports multi-field priority resolution.

• Related Parent Ticket Key - The parent issue key for subtask creation. For example, OPS-123. The parent and child issues must belong to the same project.

• Fetch Created Issue to Axonius - Enable this option to fetch each created issue and insert it into the Axonius Tickets module. Enabled by default.

• Append CSV Data to Request Description - Enable this option to append CSV data to each issue description. The maximum description capacity is 30,000 characters.

APIs

Axonius uses the following Jira REST API endpoints:

• Jira Cloud REST API v3 - POST /rest/api/3/issue (Cloud) or Jira Server REST API v2 - POST /rest/api/2/issue (On-Prem and Data Center)
• GET /rest/api/3/user/search (Cloud) or GET /rest/api/2/user/search (On-Prem and Data Center) — searches for users to resolve assignees.
• GET /rest/api/3/project (Cloud) or GET /rest/api/2/project (On-Prem and Data Center) — retrieves project information for validation.
• GET /rest/api/3/project/{projectKey}/statuses (Cloud) or GET /rest/api/2/project/{projectKey}/statuses (On-Prem and Data Center) — retrieves issue types per project.

Required Ports

Axonius must be able to communicate via the following ports:

• TCP port 443 (HTTPS) — Jira Cloud and Data Center with HTTPS
• TCP port 8080 — Jira Data Center and On-Prem (default; varies by deployment)
• TCP port 80 — Jira Data Center and On-Prem over HTTP (when HTTPS is not in use)

Required Permissions

The following permissions and requirements are needed:

• Browse Projects - View projects where issues are created.
• Create Issues - Create new issues in the target project.
• Assign Issues - Assign issues to other users (required when the Assignee field is configured).
• Search Users - Search for users to resolve assignees (Jira Cloud only).
• A valid API token (Cloud) or personal access token (On-Prem and Data Center).

Recommended roles:

• Jira Cloud: Project Member with Create Issues permission or higher.
• Jira Data Center and On-Prem: Jira user with Create Issues project permission.

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.

---