Review Scope, Impact, Checklist & Test Cases
Route: Open Quality Assurance
Assignee: QA Lead | Project Manager 🧪
After the QA Engineer finishes generating the Test Cases and submits them for review, the QA Lead/PM performs the approval via the Floating Action Buttons at the bottom of the workspace. The status flow is identical to the BRD and Implementation Plan.
Ticket status lifecycle
CREATED → DRAFTING → WAITING_REVIEW → REVIEWING → APPROVED
↓
REJECTED → (Request Review again)
Any status → ON_HOLD → (Track Back to DRAFTING)
Actions per status
DRAFTING — Send for review
The QA Engineer finishes the Test Cases and clicks "Request Review" → the ticket moves to WAITING_REVIEW.
| Button | Action |
|---|---|
| Request Review | Send the QA artifacts for reviewer evaluation |
| Move to On Hold | Pause the ticket |
WAITING_REVIEW — Pick up the review
The QA Lead/PM finds a ticket with the WAITING_REVIEW badge and clicks "Start Review" to begin the evaluation.
| Button | Action |
|---|---|
| Start Review | Begin the review — status moves to REVIEWING |
| Cancel Review | Cancel the review request — returns to DRAFTING |
| Move to On Hold | Pause |
REVIEWING — Read and decide
The reviewer goes through the four tabs in order: Scope & Impact → Checklist → Test Cases. Inline edits can be made directly during review (the Scope/Impact/Checklist tables support Edit → Save). Once finished, click "Approve" or "Reject".
| Button | Action |
|---|---|
| Approve | Approve all QA artifacts — status moves to APPROVED |
| Reject | Reject — status moves to REJECTED; the QA Engineer must revise |
| Move to On Hold | Pause |
REJECTED — Revise and resubmit
The QA Engineer revises the artifacts per the feedback, then clicks "Request Review" to resubmit.
| Button | Action |
|---|---|
| Request Review | Resubmit after revision |
| Move to On Hold | Pause |
APPROVED — Approved
The QA ticket is approved. The team moves on to the Test Execution module to run the test cases.
| Button | Action |
|---|---|
| Change | (Coming Soon) — Reopen for editing |
ON_HOLD — Paused
| Button | Action |
|---|---|
| Track Back | Move the ticket back to DRAFTING |
An approved QA ticket (APPROVED) is the prerequisite for the team to start running actual tests in the Test Execution module — recording Pass/Fail results for each test case.
If the reviewer requests changes to Scope after the Checklist has been generated, the QA Engineer must regenerate the Checklist and then the Test Cases in order. AIPD does not auto-sync when Scope changes, to avoid losing hand-edited data.