For testers
Know what's ready to test, and make rework explicit.
A real QA cycle with recorded evidence — not a status column you have to guess the meaning of.
The queue
Ready for QA means ready — not “probably.”
A task only reaches Ready for QA after its understanding was approved and development considers it complete.
Evidence, preserved
Every cycle stays on the record — including the failed ones.
Environment, steps tested, and what you found — recorded per cycle. When a fix comes back, it starts a fresh cycle instead of overwriting what you already found.
Why this matters
Rework is a fact, not something to hide.
A task that needed three QA cycles before passing shows that plainly — for the task itself, and in first-pass QA rate reporting across the team. Nothing about QA history can be edited after the fact.