Jump to content

RefractTrack Approvals and Review: Difference between revisions

From Pixel Refraction Studio
Created page with "== Approvals and Review == Every task carries a <code><nowiki>review_status</nowiki></code> of <code><nowiki>pending</nowiki></code>, <code><nowiki>approved</nowiki></code>, or <code><nowiki>wont_do</nowiki></code>, independent of its stage and archive state. This gives teams a lightweight sign-off workflow layered on top of the stage-based workflow — a task can, for example, sit in a "Done" stage while still awaiting review. === Approving, rejecting, and resetting =..."
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Approvals and Review ==
== Approvals and Review ==


Every task carries a <code><nowiki>review_status</nowiki></code> of <code><nowiki>pending</nowiki></code>, <code><nowiki>approved</nowiki></code>, or <code><nowiki>wont_do</nowiki></code>, independent of its stage and archive state. This gives teams a lightweight sign-off workflow layered on top of the stage-based workflow — a task can, for example, sit in a "Done" stage while still awaiting review.
On top of moving through columns, every task also carries its own sign-off status: '''pending''', '''approved''', or '''won't do'''. This gives teams a light second layer of quality control for example, a task can sit in a "Done" column while it's still waiting on a lead's review, so "moved to Done" and "actually signed off on" don't get mixed up.


=== Approving, rejecting, and resetting ===
=== Approving, rejecting, or resetting ===


Users with <code><nowiki>tasks:review</nowiki></code> can approve a task, reject/mark it <code><nowiki>wont_do</nowiki></code>, or reset its review status back to pending, from the task detail page.
From a task's detail page, anyone with review permission can approve it, mark it "won't do," or reset it back to pending if it needs another look.


=== Approvals in the nav ===
=== Always visible in the nav bar ===


The Approvals page/count is promoted to the main nav bar, giving reviewers a quick, always-visible view of what's waiting on them across the current project, rather than needing to hunt through the board or list view.
Rather than hunting through the board to find what's awaiting sign-off, an Approvals count sits right in the navigation bar, so reviewers always know at a glance how much is waiting on them.
 
=== Where reported tickets fit in ===
 
Anything submitted through the simplified [[RefractTrack_Tasks|reporter form]] — for teammates who shouldn't need full board access — lands in this same review queue automatically, rather than straight onto the board, so a lead can look it over before it becomes part of the team's active work.


=== Related pages ===
=== Related pages ===
Line 15: Line 19:
* [[RefractTrack_Tasks|Tasks]]
* [[RefractTrack_Tasks|Tasks]]
* [[RefractTrack_Permissions_and_Roles|Permissions and Roles]]
* [[RefractTrack_Permissions_and_Roles|Permissions and Roles]]
[[Category:RefractTrack]]

Latest revision as of 22:49, 11 September 2026

Approvals and Review

On top of moving through columns, every task also carries its own sign-off status: pending, approved, or won't do. This gives teams a light second layer of quality control — for example, a task can sit in a "Done" column while it's still waiting on a lead's review, so "moved to Done" and "actually signed off on" don't get mixed up.

Approving, rejecting, or resetting

From a task's detail page, anyone with review permission can approve it, mark it "won't do," or reset it back to pending if it needs another look.

Always visible in the nav bar

Rather than hunting through the board to find what's awaiting sign-off, an Approvals count sits right in the navigation bar, so reviewers always know at a glance how much is waiting on them.

Where reported tickets fit in

Anything submitted through the simplified reporter form — for teammates who shouldn't need full board access — lands in this same review queue automatically, rather than straight onto the board, so a lead can look it over before it becomes part of the team's active work.