Skip to main content

Jira Integration

Streamline vulnerability remediation by automatically creating Jira issues from AIPTx findings.

Setup

1. Connect Jira

  1. Log in to the AIPTx Dashboard
  2. Navigate to SettingsIntegrationsJira
  3. Click Connect Jira
  4. Enter your Jira instance URL (e.g., yourcompany.atlassian.net)
  5. Authorize AIPTx to access your Jira workspace

2. Configure Project Mapping

Map AIPTx projects to Jira projects:

3. Set Up Field Mapping

Configure how AIPTx findings map to Jira fields:

Automatic Issue Creation

Configuration

Enable automatic issue creation for specific severity levels:

Issue Template

Customize the issue template:
$

Manual Issue Creation

From Dashboard

  1. Open a finding in the AIPTx dashboard
  2. Click Create Jira Issue
  3. Review and customize fields
  4. Click Create

From API

Response

Bidirectional Sync

Status Synchronization

AIPTx syncs status changes between platforms:

Configuration

Bulk Operations

Bulk Create Issues

Create Jira issues for multiple findings:

From Scan Results

Create issues for all findings from a scan:

Advanced Configuration

Priority Mapping

Map AIPTx severity to Jira priority:

Custom Fields

Map to Jira custom fields:

Labels and Components

Workflows

Security Triage Workflow

Example Jira workflow for security findings:

SLA Tracking

Configure SLA based on severity:

Reporting

JQL Queries

Example JQL queries for AIPTx findings:

Dashboards

Create Jira dashboards with:
  • Vulnerability Backlog - Open findings by severity
  • Remediation Progress - Findings fixed over time
  • SLA Compliance - Issues within/breaching SLA
  • Trend Analysis - New vs fixed findings

Troubleshooting

  1. Verify Jira connection in Settings → Integrations
  2. Check project permissions - AIPTx needs create issue permission
  3. Verify issue type exists in target project
  4. Check required fields are mapped
Enable deduplication in settings. AIPTx uses finding fingerprint to prevent duplicates.
  1. Verify webhook is configured in Jira
  2. Check bidirectional sync is enabled
  3. Verify status mapping configuration