Ticket validation (Jira/Linear/GitHub Issues)

[haasonsaas]

Problem

Qodo, Bito, and CodeRabbit can read the linked Jira/Linear/GitHub issue and validate whether the PR actually satisfies the acceptance criteria. This is a compliance/process workflow feature with strong enterprise pull — it answers "did this PR actually do what the ticket asked for?"

DiffScope has no external context fetching beyond the repository itself.

Proposed Solution

1. Auto-detect linked tickets from:

   • PR description (Jira: PROJ-123, Linear: ENG-456, GitHub: #789)
   • Branch name conventions (feature/PROJ-123-add-widget)
   • Commit messages

2. Fetch ticket context via APIs:

   • Jira REST API (summary, description, acceptance criteria, labels)
   • Linear GraphQL API
   • GitHub Issues API

3. Inject ticket context into the review prompt as requirements

4. Add a validation pass that specifically checks:

   • Does the code change address the ticket's acceptance criteria?
   • Are there acceptance criteria that appear unaddressed?
   • Does the scope of changes match the ticket scope?

5. Output a ticket compliance section in the review:

   ## Ticket Compliance: PROJ-123
   ✅ "Add pagination to user list" — Pagination component added in UserList.tsx
   ⚠️ "Include loading states" — No loading indicator found
   ❌ "Write unit tests" — No test files changed
   

Configuration

integrations:
  jira:
    base_url: https://company.atlassian.net
    # API token from Vault
  linear:
    api_key_vault_path: secret/linear/api-key
  github_issues: true  # use existing GitHub token

Competitive Context

• Qodo Merge: /compliance command validates against Jira tickets
• CodeRabbit: Jira + Linear integration, validates acceptance criteria
• Bito: Reads linked Jira issues, flags mismatches

Priority

Tier 2 — Strong enterprise differentiator. Compliance teams love this.