Jira Integration

Connect Jira to enable agents to search issues, create tickets, and automatically investigate incoming issues via webhooks.

Used by: Incident Response, Vulnerability Remediation (mitigation tickets), and custom agents.

Using Jira Service Management? It has its own integration. See Jira Service Management, which additionally reads service-desk requests with their request type, SLA state and queue. If you run both products on one Atlassian site, connect both. Autoheal routes each ticket to the right one.

Capabilities

Capability	Description
Search Issues	Query issues using JQL
Read Issues	Access full issue details and comments
Create Issues	Create new bugs, tasks, and stories
Add Comments	Post investigation results to issues
Transition Issues	Change issue status
Webhooks	Trigger investigations on new/updated issues

note

Write tools on this integration (create issues, add comments, assign and transition issues) are available only to agents granted write access to it. A governance policy on write operations pauses each write for a person to approve, and every call is recorded in the Audit Trail.

Supported Platforms

Autoheal supports both Jira Cloud and Jira Data Center/Server.

Platform	Authentication
Jira Cloud	Email + API Token
Jira Data Center	Personal Access Token (PAT)

Setup

Jira Cloud

1

Create an API Token

1. Go to Atlassian API Tokens
2. Click Create API token
3. Name it "Autoheal" and copy the token

2

Add Integration in Autoheal

1. Go to Integrations and click Add Integration
2. Select Jira and choose Cloud (Email + API Token)
3. Enter your Jira URL (e.g., https://your-domain.atlassian.net)
4. Enter your email and API token
5. Click Save

Jira Data Center

1

Create a Personal Access Token

1. In Jira, go to Profile (click your avatar) → Personal Access Tokens
2. Click Create token
3. Name it "Autoheal", set expiration, and copy the token

2

Add Integration in Autoheal

1. Go to Integrations and click Add Integration
2. Select Jira and choose Data Center (PAT)
3. Enter your Jira Server URL (e.g., https://jira.company.com)
4. Enter your Personal Access Token
5. Click Save

Configuring Webhooks

Enable webhooks to automatically trigger investigations when issues are created or updated.

1

Enable Webhooks in Autoheal

1. Go to Integrations → Jira → Settings
2. Toggle Enable Webhooks
3. Copy the Webhook URL shown
4. Optionally, set a Signing Secret for security

2

Add Webhook in Jira

For Jira Cloud:

1. Go to Settings → System → Webhooks
2. Click Create a webhook
3. Paste the Webhook URL from Autoheal
4. Select events: Issue created, Issue updated
5. Optionally, add JQL filter (e.g., project = SUPPORT)
6. Save the webhook

For Jira Data Center:

1. Go to Administration → System → Webhooks
2. Click Create a webhook
3. Follow the same steps as Cloud

3

Test the Webhook

Create a test issue in Jira and verify an investigation is created in Autoheal.

Webhook Events

Autoheal responds to the following Jira webhook events:

Event	Triggers
jira:issue_created	New investigation
jira:issue_updated	New investigation
comment_created	New investigation

When an investigation is skipped

Autoheal doesn't always start an investigation for an issue. When it decides not to, it posts a short comment on the issue so your team isn't left wondering whether anything happened. Three reasons a skip happens:

• A recent investigation already found the root cause for a matching alert. The comment links that earlier investigation. Always posted.
• Your workspace reached its investigation limit (daily or weekly). The comment names which limit. Always posted.
• A skip rule you configured matched the alert. Off by default. Because you wrote the rule to cut noise, the comment stays quiet unless you opt in.

To get a comment when one of your own skip rules skips an issue:

1. Go to Settings → Alert Response → Investigate Group.
2. Expand the skip rule.
3. Enable Notify the source ticket.

The toggle appears only when a Pylon, Jira, or ServiceNow integration is connected.

These comments are posted by the platform rather than by an agent tool call, so approval policies don't apply to them.

Example Queries

Search for open bugs in the SUPPORT project

Find all high priority issues assigned to me

Get details about PROJ-123

List all issues updated in the last 7 days

Permissions

The API token or PAT needs the following permissions:

• Browse Projects - View projects and issues
• Create Issues - Create new issues (optional)
• Add Comments - Post investigation results (optional)
• Transition Issues - Change issue status (optional)

For webhooks, ensure the Jira user has permissions to view the issues that trigger webhooks.