# Triage an unlabelled bug queue into reproducible and not

A queue nobody can prioritise, split by evidence into reproducible and not.

Category: Bug backlog and defect hunting
Source: https://letsship.ai/use-cases/triage-an-unlabelled-bug-queue
Published: 2026-08-25

## Goal

Attempt to reproduce each ticket in an untriaged queue and record the result on it.

## Acceptance criteria

- Every ticket carries a reproduction attempt and its outcome
- Reproducible ones get steps and an environment
- Non-reproducible ones state what was tried before being closed
- Duplicates are linked rather than closed silently

## What lands as proof

Every ticket annotated with evidence, so the next prioritisation meeting works from facts.

## 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: Triage the unlabelled bug queue

Description: Attempt to reproduce each ticket in an untriaged queue and record the result on it.

Acceptance criteria:
- Every ticket carries a reproduction attempt and its outcome
- Reproducible ones get steps and an environment
- Non-reproducible ones state what was tried before being closed
- Duplicates are linked rather than closed silently

Before you create the issue, count the untriaged bugs in this repository's tracker and put the number in the description so the scope is explicit.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: attempt to reproduce each ticket in an untriaged queue and record the result on 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 each ticket updated with a reproduction attempt and its result, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.