Jira Integration¶

Argus creates Jira tickets for approved proposals. Each ticket contains the AI reasoning, key metrics, a copy-paste runbook, and a rightsizing recommendation (for resize/reduce_nodes actions).

Setup¶

1 — Policy directory¶

Tell Argus where your policy files live:

export ARGUS_POLICY_DIR=./config/policies   # default — already correct if you use the repo layout

Not set? Argus silently skips remediation and only posts the scan digest to Slack. Copy starter templates from config/policies.example/ to get going quickly.

2 — Jira API token¶

Generate an API token at id.atlassian.com/manage-profile/security/api-tokens and set these env vars:

export JIRA_BASE_URL=https://yourorg.atlassian.net
export JIRA_USER_EMAIL=you@yourorg.com
export JIRA_API_TOKEN=your-token-here

3 — Integrations config¶

Create config/integrations.yaml (gitignored — never commit this):

jira:
  project_key: COST          # Jira project where tickets are created
  issue_type: Task           # or Story, Bug, etc.
  default_assignee: null     # optional: Jira account ID
  labels:
    - argus
    - cloud-cost

Set the path via ARGUS_INTEGRATIONS_CONFIG if you store it elsewhere:

export ARGUS_INTEGRATIONS_CONFIG=/path/to/config/integrations.yaml

Ticket lifecycle¶

Create¶

On first apply --confirm for a finding, Argus:

1. Searches for an existing open ticket with label argus:<resource_id>:<policy_id>
2. If none found — creates a new ticket with full ADF description
3. If found — updates the description (if the snapshot fingerprint changed) and adds a diff-comment

This makes apply --confirm idempotent — re-running after a re-scan either does nothing (finding unchanged) or updates the existing ticket (finding changed), never creates duplicates.

Update on re-scan¶

If the same resource appears in a later scan with different metrics or cost:

• Argus detects the change via the snapshot fingerprint embedded in the ticket description
• It updates the description with new data
• It adds a comment: "Argus re-scan detected a change — description updated"

Close¶

Argus does not auto-close tickets. When a human resolves a ticket in Jira, Argus will stop matching it on future scans (JQL filter: statusCategory != Done).

Ticket structure (ADF)¶

Each ticket description has these sections:

Audit log¶

Every apply --confirm appends a line to local_reports/audit.jsonl:

{"ts":"2026-07-05T10:23:45+00:00","proposal_id":"uuid4","resource_id":"i-0abc","resource_type":"AWS::EC2::Instance","cloud":"aws","region":"us-east-1","policy_id":"aws-ec2-stop-idle-14d","action":"stop","estimated_monthly_cost_usd":28.40,"ai_priority":"high","jira_key":"COST-42","jira_url":"https://yourorg.atlassian.net/browse/COST-42"}

The file is append-only — multiple entries for the same proposal_id represent re-scans. Use argus policies stats to aggregate it.

Override the path with ARGUS_AUDIT_LOG:

export ARGUS_AUDIT_LOG=/var/log/argus/audit.jsonl

Labels¶

Every Argus ticket gets these labels automatically: