Jira Software - Create Ticket

Jira Software - Create Ticket automatically creates Jira Software issues from Axonius assets, 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.

• Project Key - The project key where the issue will be created (e.g., OPS, DEV).

• Issue Type - The type of issue to create (e.g., Bug, Task, Story, Epic).

• Request Summary - The title or summary of the issue. Supports Axonius template variables.

• Request Description - The issue description or body text. Plain text is automatically converted to ADF format on Jira Cloud.

• Use Assignee Name Instead of ID - Select this option to assign the issue by user display name or email. If not selected, use the user's account ID.

• Use Full URL - Select this option to include the full URL in issue links and webhooks.

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

• Assignee - User display name, email, or account ID to assign the issue. Search is performed via the Jira user search API.

• Labels - Comma-separated list of labels to add to the issue.

• Components - Comma-separated list of component names to associate with the issue.

• Custom Fields (JSON) - Additional fields as a JSON object. Example: {"priority": {"name": "High"}, "labels": ["Axonius"]}

• Webhook URL - Optional webhook URL to POST the created issue link to after successful creation.

• Webhook Content - Template for webhook body. Default: {"text": "Created issue link is: <<ISSUE_LINK>>"}

• Related Parent Ticket Key - Parent issue key for subtask creation (e.g., OPS-123).

• Fetch Created Issue to Axonius - Select this option to fetch the created ticket and insert it into the Axonius Tickets module. Default: enabled.

• Send CSV Data - Select this option to attach a CSV file with affected entities.

• Add Default Incident Description - Select this option to add default incident information to the description.

• Append CSV Data to Description - Select this option to append CSV data to the request description. Maximum description capacity: 30,000 characters.

Connection Settings

💡

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 (e.g., https://your-instance.atlassian.net or https://jira.on-prem.com).

• User Name - 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 - API token or Client Secret. For Cloud, generate at https://id.atlassian.com/manage-profile/security/api-tokens. For On-Prem, use an API token or personal access token.

• Jira API Version - 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.

---

APIs

Axonius uses the following endpoints of the Jira Cloud REST API v3 -

• POST /rest/api/3/issue (Cloud) or Jira Data Center and 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).
• GET /rest/api/3/project (Cloud) or GET /rest/api/2/project (On-Prem and Data Center).
• GET /rest/api/3/project/{projectKey}/statuses (Cloud) or GET /rest/api/2/project/{projectKey}/statuses (On-Prem and Data Center).

Required Ports

Axonius must be able to communicate via the following ports:

• TCP port 443 (HTTPS) - Standard for Jira Cloud and secure connections
• TCP port 8080 - Jira Data Center and On-Prem instances (varies by deployment)
• TCP port 80 - Jira Data Center and On-Prem instances over HTTP (if not using HTTPS)

Required Permissions

The following permissions and requirements are needed:

• Browse Projects - View projects where issues will be created.

• Create Issues - Create new issues in target projects.

• Assign Issues - Assign issues to other users (if using assignee field).

• Search Users - Search for users to assign issues (Jira Cloud only).

• API Token or Personal Access Token - Valid API token (Cloud) or personal access token (On-Prem).

Recommended Roles:

• Jira Cloud: Project Administrator or higher.

• Jira Data Center and On-Prem: Jira Administrator or Project Administrator.

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.