Ticket Type + Jira Collector

✓ Guardrail ↓ Collector Stable Devex Build And Ci

Enforce Ticket Type using data collected by Jira Collector. Automatically check devex build and ci standards on every PR.

Guardrail: Ensures the ticket is an acceptable issue type.

Data Source: Extract Jira ticket references from pull request titles, validate them against the Jira REST API, and detect ticket reuse across PRs.

Get Started View on GitHub

How Jira Collector Powers This Guardrail

The Jira Collector gathers metadata from your vcs systems. This data flows into Lunar's Component JSON, where the Ticket Type guardrail evaluates it against your standards.

When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement with actionable feedback.

↓ Jira Collector Gathers Data Collector

Extracts metadata from code, configs, and tool outputs

{ } Component JSON

Data centralized in structured format for evaluation

✓ Ticket Type Checks Guardrail

Pass/fail result with actionable feedback in PRs

Quick Start Configuration

Add both the collector and policy to your lunar-config.yml to enable this guardrail.

📄 lunar-config.yml

# Step 1: Enable the Jira Collector
collectors:
  - uses: github://earthly/lunar-lib/collectors/jira@v1.0.0
    # with: ...

# Step 2: Enable the Ticket Guardrails
policies:
  - uses: github://earthly/lunar-lib/policies/ticket@v1.0.0
    include: [ticket-type]
    # with: ...

What Jira Collector Collects

This collector gathers the following data that the Ticket Type guardrail evaluates.

Collector code

`ticket`

Extracts Jira ticket ID from PR title, fetches issue metadata from the Jira REST API, and writes normalized ticket data to .vcs.pr.ticket and native Jira data to .vcs.pr.ticket.native.jira.

Collector code

`ticket-history`

Queries the Lunar SQL database to count how many other PRs reference the same ticket. Writes .vcs.pr.ticket.reuse_count for policy evaluation. Detects ticket recycling abuse.

Example Data Flow

Here's an example of the data that Jira Collector writes to the Component JSON, which Ticket Type then evaluates.

{ } component.json From Jira Collector

{
  "vcs": {
    "pr": {
      "ticket": {
        "id": "ABC-123",
        "source": { "tool": "jira", "integration": "api" },
        "url": "https://acme.atlassian.net/browse/ABC-123",
        "valid": true,
        "status": "In Progress",
        "type": "Story",
        "summary": "Implement payment validation",
        "assignee": "jane@acme.com",
        "reuse_count": 0,
        "native": {
          "jira": { "...full Jira API response..." }
        }
      }
    }
  }
}

Configuration Options

Jira Collector Inputs

Input	Required	Default	Description
`ticket_prefix`	Required	—	Character(s) before the ticket ID in PR titles (empty = match anywhere)
`ticket_suffix`	Required	—	Character(s) after the ticket ID in PR titles (empty = match anywhere)
`ticket_pattern`	Optional	`[A-Za-z][A-Za-z0-9]+-[0-9]+`	Regex pattern for ticket ID (without prefix/suffix)
`jira_base_url`	Required	—	Jira instance base URL (e.g. https://acme.atlassian.net)
`jira_user`	Required	—	Jira user email for API authentication

Ticket Guardrails Inputs

Input	Required	Default	Description
`allowed_sources`	Required	—	Comma-separated list of allowed ticket sources (e.g. "jira,linear"). Empty = any.
`allowed_statuses`	Required	—	Comma-separated list of allowed ticket statuses (empty = any)
`disallowed_statuses`	Required	—	Comma-separated list of disallowed ticket statuses (empty = none)
`allowed_types`	Required	—	Comma-separated list of allowed issue types (empty = any)
`max_ticket_reuse`	Optional	`3`	Maximum number of other PRs allowed to reference the same ticket

Learn More

Guardrail · Ticket Guardrails Ticket Type View all compatible integrations

→

Collector Jira Collector View full documentation

→

Ready to Automate Your Standards?

See how Lunar can turn your engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 100+ built-in guardrails.

Works with any process

Infrastructure conventions

Post-mortem action items

Security & compliance policies

Testing & quality requirements

Automate Now

Turn any process doc into guardrails

Book a Demo