Triage an unlabelled bug queue into reproducible and not
A queue nobody can prioritise, split by evidence into reproducible and not.
The ticket
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.
Why teams defer it
- Triage produces no shipped code, so it loses to anything that does.
- It needs somebody with enough product knowledge to judge each report, which is usually the busiest person.
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.