Retest Queue
The Retest Queue (/retest) surfaces every test case that needs to be re-executed — typically because a linked bug was fixed and the test must be verified again.
How a test case enters the queue
A test case is added to the retest queue when its retestRequired flag is set to true. This happens in two ways:
- Manually — A tester clicks Flag for retest on a test run result.
- Automatically — A linked Linear bug moves to the "Done" status. QA Hub sets the flag automatically via its background poller.
Working the queue
The queue shows:
| Column | Description |
|---|---|
| Code | Test case code (e.g., TC-047) |
| Title | Test case title |
| Bug ticket | The resolved bug that triggered the retest |
| Flagged at | When the retest flag was set |
| Status | Current test case status |
Clearing a test case from the queue
Once you have verified a fix:
- Run the test case in a new test run and mark it
PASSED. - The
retestRequiredflag is cleared automatically when aPASSEDresult is recorded.
Alternatively, manually unflag a test case from the queue list.
Integration with Bug Tracker
The Retest Queue and Bug Tracker work together:
Notifications
When a test case is automatically added to the retest queue, an in-app notification is sent to the QA Manager with a link to the affected test case.