CFR from Jira / Linear

Ticket-as-failure. Less real-time than incidents but easier to triage and tag.

Oliver Wakefield-Smith

Founder, Digital Signet. Built siemcost / monitoringcost / itbudgetcalculator.

Updated 21 Jun 2026

Direct answer

Ticket-source CFR uses post-deploy bug tickets as the failure signal. JQL or Linear GraphQL queries pull tickets tagged as escape / regression, joined to the closest preceding deployJira REST Search2026 Linear GraphQL API2026. Slower than incident-source CFR but easier to triage.

Custom-field convention

One required field: escape: yes/no. One optional: root_cause: deploy/external/legacy. The CFR pipeline filters on escape=yes AND root_cause=deploy.

Ticket-source vs incident-source CFR

The two will diverge. Tickets lag incidents (filed days later) but capture user-reported regressions that never tripped an alert. Incidents capture only what alerted. The pragmatic choice: use incidents for the headline CFR, tickets for the post-mortem audit.