Review BRD
Route: Open BRD Generation
Assignee: Project Manager | Tech Lead 📋
After the BA finishes drafting the BRD and sends it for review, the ticket goes through a controlled status flow before it is approved. All review actions are performed through Floating Action Buttons — a floating button bar that appears at the bottom of the workspace when a ticket is selected.
Ticket status lifecycle
CREATED → DRAFTING → WAITING_REVIEW → REVIEWING → APPROVED
↓
REJECTED → (Request Review again)
Any status → ON_HOLD → (Track Back to DRAFTING)
The current status of a ticket is shown as a colored badge in the left-column list. The list filters itself by the selected status — switch status tabs to see tickets at each stage.
Actions per status
DRAFTING — Send for review
The BA finishes the BRD and clicks "Request Review" → the ticket moves to WAITING_REVIEW.
Buttons shown while the ticket is in DRAFTING:
| Button | Action |
|---|---|
| Request Review | Send the BRD for reviewer evaluation — status moves to WAITING_REVIEW |
| Move to On Hold | Pause the ticket — status moves to ON_HOLD |
WAITING_REVIEW — Pick up the review
The ticket is waiting for a reviewer. The reviewer finds a ticket with the WAITING_REVIEW badge in the list and clicks "Start Review" to begin the evaluation.
Buttons shown while the ticket is in WAITING_REVIEW:
| Button | Action |
|---|---|
| Start Review | Begin the review — status moves to REVIEWING |
| Cancel Review | Cancel the review request — status returns to DRAFTING (used by the BA when further edits are needed before review) |
| Move to On Hold | Pause the ticket |
REVIEWING — Read and decide
The reviewer reads the BRD content in the editor in read-only mode. After the evaluation, click "Approve" or "Reject".
Buttons shown while the ticket is in REVIEWING:
| Button | Action |
|---|---|
| Approve | Approve the BRD — status moves to APPROVED |
| Reject | Reject — status moves to REJECTED; the BA must revise |
| Move to On Hold | Pause if more time is needed |
REJECTED — Revise and resubmit
The BA is notified of the rejection, opens the ticket, edits the BRD content, and clicks "Request Review" to resubmit.
Buttons shown while the ticket is in REJECTED:
| Button | Action |
|---|---|
| Request Review | Resubmit the revised BRD for review |
| Move to On Hold | Pause |
APPROVED — BRD approved
A ticket in APPROVED status is at the end of the flow. The BRD is automatically added to the Knowledge Base.
Buttons shown while the ticket is in APPROVED:
| Button | Action |
|---|---|
| Change | (Coming Soon) — Reopen for editing |
ON_HOLD — Paused
The ticket is paused and not being worked on. Click "Track Back" to move it back to DRAFTING and continue.
| Button | Action |
|---|---|
| Track Back | Move the ticket back to DRAFTING |
An approved BRD (APPROVED) is automatically added to the project Knowledge Base. From that point on, the AI Agent uses this BRD as a source when generating the Implementation Plan and Test Cases for the same feature.
If the BA spots an issue after clicking "Request Review", they can click "Cancel Review" to retract it — the ticket returns to DRAFTING, the BA revises it, and submits again.