Integration

Jira Integration

Automatically verify that your PR addresses the Jira ticket's acceptance criteria. AI checks each criterion against the code changes.

Automatic TicketIcon Detection

Extracts Jira ticket ID from PR title or branch name (e.g., PROJ-123)

Acceptance Criteria Fetch

Retrieves task description and acceptance criteria from Jira

AI Verification

AI analyzes if the PR changes address each acceptance criterion

Setup Guide

Enable Jira Integration

In Git AutoReview settings, enable Jira:

{
  "gitAutoreview.jira.enabled": true
}

Configure Jira Connection

Add your Jira instance details:

Jira CloudIcon:

{
  "gitAutoreview.jira.baseUrl": "https://your-company.atlassian.net",
  "gitAutoreview.jira.email": "your-email@company.com",
  "gitAutoreview.jira.apiToken": "your-api-token"
}

Jira ServerIcon/Data Center:

{
  "gitAutoreview.jira.baseUrl": "https://jira.company.com",
  "gitAutoreview.jira.username": "your-username",
  "gitAutoreview.jira.password": "your-password-or-token"
}

Get Jira API Token

For Jira CloudIcon:

Go to id.atlassian.com/manage-profile/security/api-tokens

Click "Create API token"

Name it "Git AutoReview"

Copy and paste in settings

For Jira ServerIcon:

Use your Jira password or create a Personal Access Token in your profile.

Configure Advanced Settings (Optional)

Fine-tune what Jira context the AI receives:

{
  "gitAutoreview.jira.fetchComments": true,
  "gitAutoreview.jira.fetchAttachments": false,
  "gitAutoreview.jira.fetchSubtasks": true,
  "gitAutoreview.jira.fetchLinkedIssues": false,
  "gitAutoreview.jira.maxComments": 20,
  "gitAutoreview.jira.acceptanceCriteriaField": "customfield_10001"
}

- fetchComments: Include ticket comments for additional context - fetchSubtasks: Include subtask details in the review context - acceptanceCriteriaField: Custom field ID if your AC is in a non-standard field

Review with AC Verification

When you review a PR:

Git AutoReview detects the Jira ticket (e.g., PROJ-123 from branch or title)

Fetches the ticket's acceptance criteria

AI analyzes if the PR addresses each criterion

Shows verification results in the review panel

Example output:

✅ AC1: User can login with email — Addressed in auth.ts ✅ AC2: Show error on invalid password — Addressed in LoginForm.tsx ⚠️ AC3: Remember me checkbox — Not found in changes

Why Use AC Verification?

For Developers

• Catch missing requirements before review
• Self-check PR completeness
• Reduce back-and-forth with reviewers

For Reviewers

• Quick overview of AC coverage
• Focus on code quality, not requirements
• Faster review cycles

Frequently Asked Questions

How does Git AutoReview find the Jira ticket?

It looks for patterns like PROJ-123 in the PR title first, then in the branch name. Common patterns: feature/PROJ-123-description, PROJ-123-feature-name, [PROJ-123] Feature description.

What if my PR doesn't have a Jira ticket?

Jira integration is optional. If no ticket is found, Git AutoReview performs a standard code review without AC verification. You can also manually specify a ticket ID.

Does this work with Jira ServerIcon behind a firewall?

Yes. The extension connects directly from your machine to your Jira instance. No external services involved — just make sure your machine can reach Jira on the network.

What Jira fields are used for acceptance criteria?

By default, Git AutoReview looks for acceptance criteria in the Description field and custom fields named 'Acceptance Criteria'. You can configure a custom field ID via the acceptanceCriteriaField setting.

What advanced Jira settings are available?

You can configure fetchComments (include ticket comments in AI context), fetchAttachments (reference attachment names), fetchSubtasks (include subtask context), fetchLinkedIssues (include linked issue context), maxComments (limit comments fetched, default 20), and acceptanceCriteriaField (custom field ID for AC).

Bitbucket Integration Security & Privacy