How to

Record a QA failure

Reopen work after QA rejection and start a corrective validation cycle.

What changes

reopen records accepted QA-failure evidence, clears stale validation and quality evidence, and recalculates the next action for correction and re-validation.

When this helps

QA reproduced the original problem or found a regression after validation.
A closed or validated Mission must return to delivery with the rejection reason preserved.
The next implementation session needs exact reproduction steps, a link, or screenshot context.

Run this command

terminal

$sumr mission reopen SUM-123 --reason "Checkout still fails on an empty cart" --note "Reproduce with a zero-item cart"# QA correction cycle

Flags you can use

--reason <text>

Record why QA rejected the work.

--note <text>

Add a reproduction pointer such as steps, a link, or a screenshot.

--allow-custom-key

Accept a work key that does not match a configured work-provider prefix. Use only for local or intentionally custom work.

--json

Return a structured JSON envelope for scripts, CI jobs, and AI assistants.

--help, -h

Show the command syntax, supported flags, and examples without changing files.

Keep in mind

Reopening preserves the QA rejection as accepted evidence and removes validation and quality evidence that no longer proves the corrected work.
Record fresh accepted validation and quality evidence before PR handoff. Replace implementation or review evidence too when the corrective change makes it stale.