# Work the crash tracker by user impact, one issue per ticket

The crash affecting the most users, taken one issue at a time rather than as an inbox.

Category: Bug backlog and defect hunting
Source: https://letsship.ai/use-cases/work-the-crash-tracker-by-user-impact
Published: 2026-08-25

## Goal

Fix the crash affecting the most users, with a test that reproduces it.

## Acceptance criteria

- The tracker issue is linked and its user count recorded
- A test reproduces the crash
- The fix handles the cause, not only the reported stack frame
- The issue is resolved in the tracker after the fix ships

## What lands as proof

The tracker issue, the reproducing test, and the affected-user count that justified picking this one.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Fix the crash in {area}

Description: Fix the crash affecting the most users, with a test that reproduces it.

Acceptance criteria:
- The tracker issue is linked and its user count recorded
- A test reproduces the crash
- The fix handles the cause, not only the reported stack frame
- The issue is resolved in the tracker after the fix ships

Before you create the issue, sort this repository's crash tracker by users affected and replace {area} with the top issue's location.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: fix the crash affecting the most users, with a test that reproduces it. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means stack trace linked, reproduction test, fix, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.