> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira audit profile, Vortex IQ

> What the Vortex IQ Jira health audit checks: Jira: Backlog, Capacity & Finding Lifecycle

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/jira) · [Audit Profile](/nerve-centre/kpi-cards/jira/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/jira/sentiment)**

Surfaces the daily ops questions a merchant or web agency lives with in Jira: is the token still good, is our backlog drowning, are people overloaded, and (most importantly) are the findings we filed actually getting resolved or quietly dying in the queue?

## What this audit checks

### Authentication & access

* API token still valid (auth on /rest/api/3/myself)
* Default project exists and is writable
* Issue-types Bug + Task available in default project
* Atlassian rate-limit headroom > 30%

### Backlog health

* Open ticket count vs 30-day baseline (sudden growth = drowning signal)
* Blocked-tickets count + change WoW
* Oldest open ticket age (>90 days = backlog rot)
* Unassigned tickets > 5 (work that nobody owns)
* Backlog-by-priority skew (mostly Lows = no one is grooming)

### VortexIQ findings lifecycle (the stickiness test)

* Abandoned findings - VortexIQ-created, no status change >14d
* Finding resolution rate over rolling 90d (target >75%)
* Avg time-to-fix for resolved findings, by severity
* Findings closed Won't-Do without comment (silent dismissals)
* Regression rate - findings that reopened after Done

### Team capacity

* Assignees with >10 open tickets (overload signal)
* Assignees with zero closed tickets in 14d (parked work)
* Cycle time degradation > 25% week-over-week
* Sprint scope-creep (issues added after sprint start)

### Cross-connector signals

* Critical findings from sibling connectors (shopify/bigcommerce/adobe/cybersource) older than 7 days with no Jira ticket - coverage gap
* Jira tickets referencing decommissioned/archived integrations - stale work

## Severity thresholds

| Signal                             | Warn | Critical |
| ---------------------------------- | ---- | -------- |
| `vortexiq_findings_abandoned`      | 5    | 15       |
| `vortexiq_finding_resolution_rate` | 75   | 50       |
| `blocked_tickets`                  | 3    | 8        |
| `unassigned_tickets`               | 5    | 20       |
| `oldest_open_ticket_age_days`      | 60   | 90       |
| `cycle_time_change_pct`            | 25   | 50       |
| `rate_limit_headroom_pct`          | 30   | 10       |

## Data sources

* `GET {site_url}/rest/api/3/myself` - Token + account info
* `GET {site_url}/rest/api/3/project/{key}` - Default project access + writability check
* `GET {site_url}/rest/api/3/project/{key}/statuses` - Status name → status\_category mapping
* `GET {site_url}/rest/api/3/search?jql=...` - JQL-driven backlog reads (open count, blocked, abandoned, by-assignee, etc.)
* `GET {site_url}/rest/agile/1.0/board` - Discover boards for sprint-aware projects
* `GET {site_url}/rest/agile/1.0/board/{boardId}/sprint` - Active-sprint progress + velocity history