Triage, fix and verify a bug

Confirm a reported bug, mark it fixed and record the retest.

In short

A bug card goes from reported, to confirmed, to fixed, to verified. Each step is a button on the card, under "Needs attention", and is written to its History with your name. A verification can rest on a test run that passed after the fix.

Before you start

Who: confirming, fixing and verifying a bug need "Create and manage boards". Anyone who can open the board reads the bug and its History.
Plan: every plan.
First: the card needs a card type with Bug behavior (see /help/boards/card-types), or it is made from a request or run (see /help/boards/connections-and-hiring-boards).

Steps

Reported: the bug is created with triage state Pending and the details of the request or run it was reported from.
Triage: open the card and, under "Needs attention", choose "Confirm bug". Not a bug? Choose "Reject", add why if you like, then "Reject bug" - or "Keep it" to go back.
Fix: on a confirmed bug, choose "Mark fixed / ready for QA". It moves to a Testing column if the board has one, and records who fixed it.
Verify: choose "I verified the fix" or "Retest failed". Pick the Verification evidence - a linked test run that ran after the fix and passed - or "Manual verification (no linked test run)", and fill in Build / commit and Environment.

Result: a pass moves the bug to Done and records who verified it. A failure sends it back to In Progress, clears the fix and adds one to the retest count.

Good to know

A bug is a card whose card type has Bug behavior. Besides the usual fields it has a severity (Low, Medium, High or Critical) and the endpoint, method and status code it was seen on. It also has the expected and actual result, reproduction steps, and a triage state. A story adds a business description and acceptance criteria.
Confirming, rejecting, fixing and verifying need the manage permission on the board.
A rejected bug keeps triage state Rejected, and your reason is written to its History.
Linked evidence is a snapshot, and linking a passing test never closes a bug by itself.
On a bug with no steps yet, "Draft steps" asks AI to draft them from what the card says, for you to edit and save. What the failing service answered is never sent to AI.
The "Ready to verify" filter shows fixed bugs waiting for their retest.
What happens next: each step is written to the card's History with your name. A failed retest sends the bug back to In Progress and adds one to the retest count.
To undo: a verified result cannot be rewritten. Mark the bug resolved again and record a new verification.

If something goes wrong

"Only a confirmed bug can be marked resolved.": confirm the bug first.
"The evidence is unavailable or predates this fix. Link a new test run before verifying."
"The selected test evidence does not show a passing result.": run the test again until it passes, or record "Retest failed".
"Record the build and environment for this verification."
"A verified result cannot be rewritten. Mark the bug resolved again before recording a new verification."
"The verifier needs permission to manage this board and verify fixes."
"This action only applies to a Bug card." and "Verification is available for bugs.": the card's type does not have Bug behavior.
"This bug has not been marked resolved yet.": press "Mark fixed / ready for QA" first.
"Choose linked test evidence with a recorded outcome and execution time.": pick a run that has finished with a result.
"The duplicate-of card must be on the same board."