These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Task & Kanban Board
- Features
- Reviews and approvals
Reviews and approvals
Review the current work before a protected move reaches its destination.
OverviewReview Inbox×
Task & Kanban Board · Reviews and approvals
New
Review Inbox
Approval conditions
| Request number | Task | Source column | Target column | Requested by | Requested at | |
|---|---|---|---|---|---|---|
| TR-75322 | Update sprint planning notes | Done | Done | Ibrahim Saleh | 24 Oct | |
| TR-21489 | Test invite acceptance flow | Needs review | Backlog | Mara Chen | 17 Oct | |
| TR-75785 | Fix mobile filter spacing | Approved | Needs review | Kenji Watanabe | 15 Oct | |
| TR-33775 | Fix mobile filter spacing | Ready to release | Blocked | Kenji Watanabe | 22 Oct | |
| TR-17012 | Test invite acceptance flow | Done | Backlog | Mara Chen | 28 Oct |
6 of 6 records
Update sprint planning notesTransition requests · TR-75322
PendingSource columnDone
Target columnDone
Requested byIbrahim Saleh
Requested at24 Oct
What you can do
Move work
Member requests a permitted move from the current column using the expected task revision. Resolve the active workflow revision, allowed source path, blockers and effective destination WIP limit. Reserve the destination and update current column plus derived Status atomically. Set started at on the first Doing entry of the current cycle, append task events and retain the order change. A drag, keyboard action or bulk request uses the same checks.
Request review
When a destination column requires approval, create a transition requests record for the current task revision and intended destination. The request waits in the Review Inbox without moving the task. Reviewer inspects the current work and required evidence. Decision by must differ from requested by and last worked by; holding two roles does not make self-review independent. A changed task or workflow expires the affected request and needs a fresh review.
Complete the handoff
The move service consumes an Approved transition requests decision once, rechecking current revision, blockers, mandatory checklist policy and destination capacity. Mark Applied only when the move commits. Entering Done stamps completed at and appends one Completed task events row for Task plus cycle number. An approved request with no free slot remains approved but unapplied until it can be safely retried; approval alone is not completion.
Reopen or archive
Board Owner can reopen completed work through an allowed current workflow move with a recorded reason. Preserve the original completion event, increment cycle number and start a new work cycle without rewriting earlier timings. Recheck WIP and applicable approval policy for the destination. Archiving removes a task from active lists but preserves its relationships and event history; it cannot be used to remove evidence from an open review.
Keep approval distinct from the move itself
A reviewer may approve a handoff just as another task fills the last destination slot. The approved request stays visible, but the task does not move until capacity is available and current checks pass. Applied records the successful move, not a click on Approve.
The decision identifies the exact task revision, workflow revision and destination. If protected work changes, the affected request expires. Holding Member and Reviewer roles cannot make a person independent of the work they prepared.
A rejected request keeps its reason while the task stays in place. The contributor can revise the work and request another decision. Repeated approval or move commands return the original outcome. When the destination is Done, the completed event belongs to the current cycle; reopening starts another cycle without erasing the earlier decision or claiming it covered the new work.
What your team sees
- Review Inbox. Open the current records for this module within your assigned role and permitted scope.
What it keeps track of
Data model- Transition requests
- Independent review of a specific task revision and destination; the request is not a completed move.
- Tasks
- Canonical work item. One column owns the workflow position; filters and lanes never duplicate the task.
- Columns
- Ordered workflow columns; task status derives from the current column category.
- Task checklist items
- Concrete steps required to complete a task; completion carries the acting identity and time.
- Task events
- Append-only task changes and completed cycle evidence.
Who uses it
Permissions- Member
- Requests a protected move. an independent Reviewer or authorized Board Owner decides.
Set up Task & Kanban Board your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.