Findings sat in the backlog with no status change for two weeks, these are the ones losing money silently.
At a glance
The number of open Linear issues withvortex-iq-findinglabel whoseupdatedAthas not changed in 14+ days. On Linear this card carries unusual weight because Linear teams rarely accumulate stale work by accident; the cycle model and engineer-led culture push completion. A rising count is a stronger signal here than on Asana, ClickUp, or Monday: it means the cycle discipline is breaking down.
Calculation
Calculated automatically from your Linear data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US home-fitness brand on Shopify Plus with an 8-engineer team running Linear on weekly cycles. Snapshot taken on 02 May 26 at 11:30 EDT.- 6 stale issues on a Linear team is a meaningful signal. Engineering teams on Linear typically sit at 0-3 abandoned because the cycle model surfaces drift fast. Crossing warn means the cycle discipline broke at least once in the last fortnight.
- The ENG cluster has a clear root cause: an incident pulled the team off audit work. This is the single most common Linear abandoned-rate driver. Pair this card with Datadog incidents, if Datadog showed a sustained incident burst 2-3 weeks ago, this is the operational fallout.
- The Triage entry on parental leave is the single-point-of-failure marker. Triage means “no one has decided who owns this”; with the team lead away, no one is taking the decision. The right action is to reassign Triage ownership to a deputy for the leave duration.
- The INFRA vendor-pending cluster is debatable. Some teams prefer to mark vendor-blocked work as
canceled(closing the loop on Linear’s side, with a comment to re-create when the vendor returns). Others prefer to leave it open as a reminder. Either is defensible; what is not defensible is leaving it open and ignoring the abandoned signal. - The right action is a 15-minute cycle-retro audit. On a Linear team this is what stops staleness compounding. End-of-cycle review of any issue with
updatedAtolder than the cycle length: complete, cancel, or explicitly carry forward with an updated estimate. Linear’s keyboard shortcuts make this fast.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Linear’s own UI:linear.app then for each connected team open Issues. Apply filters:For multi-team visibility, the Workspace → Issues view (Enterprise plan) lets you apply the same filter across all teams. Why our number may legitimately differ from a saved Linear filter:Label is "vortex-iq-finding",State is not Completed and not Cancelled,Updated is more than 14 days ago. Save the view as Stale Findings withcmd+s. Linear’s filter for “Updated” is named-relative-time aware, so the filter automatically rolls forward as time passes.
Cross-connector reconciliation. Linear abandoned vs incident-management peers:
Known limitations / merchant FAQs
Linear shows my issue was edited yesterday but you say it’s abandoned. What’s wrong? Almost always the timezone or webhook delay. Linear’s UI shows “edited yesterday” in your account-profile timezone; our 14-day cutoff is UTC. For a boundary-day issue, the calendar day differs. Refresh in 30 seconds; the gap is very rare on Linear because webhooks are fast. What counts as movement? Any of: state change, assignee change, priority change, estimate change, label change, cycle assignment change, comment posted, description edit, title edit. Linear bumpsupdatedAt on each. What does NOT count: viewing the issue, watching/unwatching, time-tracking entries.
The 14-day window feels long for Linear. Can we tune it down?
Yes. Engineering teams running weekly cycles often tune to 7 days because the cycle length is the natural staleness boundary. Settings → Connectors → Linear → Abandonment threshold (days). Some teams set it to the cycle length plus a buffer (e.g. 2-week cycle → 16-day threshold).
A finding is in Triage and has been there 16 days. That feels intentional, why count it?
Because Triage is meant to be transient (under 24 hours typically). 16 days in Triage is the inverse signal: nobody is reviewing the Triage queue. The right action is to assign Triage ownership; the cleanest fix is Settings → Triage → Triage owner.
We use multiple Linear teams. The count looks alarming.
Open the per-team stack panel; on Linear the staleness usually concentrates on one team that just had a leave/incident/transition.
Resolution rate dropped, abandoned rising. What changed?
Standard playbook: (1) Datadog/New Relic incidents in the last 2-3 weeks. Engineering-led teams on Linear are the most incident-correlated of any PM tool we connect to. (2) Tickets by Assignee for sudden concentration changes. (3) Cycle Progress for whether findings are entering cycles at all.
The abandoned count appears suddenly higher overnight. Why?
The 14-day clock keeps ticking even when no one is editing. If 5 issues were last touched on the same day exactly 14 days ago, all 5 become abandoned at the same time the next day. Self-corrects within 24 hours of the team picking the queue back up.
Should I close abandoned issues or fix them?
Both, depending on triage. On Linear specifically the cleanest path is the end-of-cycle retro: any issue with updatedAt older than the cycle length gets a decision (complete, cancel, or carry forward with updated estimate). Most Linear teams find 30-50% of stale items should be cancelled, the cycle discipline does most of the work for them.
Is this the right card for my context, or should I focus on Findings Open?
On Linear specifically this card is the queue-health indicator; Findings Open is queue size. The platform usually self-corrects open count via cycles, so abandoned is the louder signal when something is genuinely off.
Why doesn’t Linear ship a built-in “abandoned” view?
Linear’s product philosophy holds that cycles are the staleness primitive: any issue not completed in its cycle is by definition stale. The 14-day overlay this card adds is finer-grained than Linear’s native cycle boundary, useful for teams that mix sprints with always-on work.