Back to Docs
Integration

Jira Integration

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

Automatic Ticket 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

1

Enable Jira Integration

In Git AutoReview settings, enable Jira:

{
  "gitAutoreview.jira.enabled": true
}
2

Configure Jira Connection

Add your Jira instance details:

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


Jira Server/Data Center: 
{
  "gitAutoreview.jira.baseUrl": "https://jira.company.com",
  "gitAutoreview.jira.username": "your-username",
  "gitAutoreview.jira.password": "your-password-or-token"
}
3

Get Jira API Token

For Jira Cloud:
  • 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 Server:
    • Use your Jira password or create a Personal Access Token in your profile.
    4

    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 Server behind a firewall?

    Yes. Git AutoReview connects directly from your machine to your Jira instance. No external services are involved. Ensure your machine has network access to Jira.

    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 custom field IDs in settings.

    Bitbucket IntegrationSecurity & Privacy