# Triage a bug with reproducible evidence

Illustrative planning brief; no automatic product import.

Illustrative report: a user says an export failed, but the selected date range and exact failure state are missing.

## Decision

Collect a bounded reproduction and expected behavior before choosing a correction task.

## Owned work

- Capture observed behavior
  - Owner role: Triager
  - Acceptance evidence: The report states what happened without inferring its cause.
- Recover the reproduction
  - Owner role: Engineer
  - Acceptance evidence: A safe synthetic example identifies inputs and the visible failure condition.
- Choose the next action
  - Owner role: Technical lead
  - Acceptance evidence: The team chooses investigate, clarify or fix based on the evidence.

## Workflow

1. Record expected and observed behavior separately.
2. Reproduce with safe synthetic inputs where feasible.
3. Link the investigation outcome to a bounded next task.

## Judgment

A screenshot alone may omit the decisive input. Do not put customer data or credentials into the reproduction brief.


## Illustrative delivery brief

Observed: export failed according to the current report.
Missing: selected range and visible error state.
Hypothesis: investigate after reproduction.
Next action: collect a safe example before committing a fix.


## Workflow questions

### Should a plausible cause be called the bug?

Label it a hypothesis until code or reproduction evidence supports it.

### What if the failure cannot be reproduced?

Record the evidence gap and ask the smallest question that could change the next decision.

## Product connection

Prepare the observed failure and reproduction boundary before drafting the corresponding investigation task in TeamBoostAI.

Confirm account availability before adopting this manual outline.