Skip to content

Statuses

QA Sync tracks several independent lifecycles. This page lists each one with its values and transitions.

Applies to apps, modules, submodules and tasks. See Task lifecycle.

Stage Value Progress
Draft draft 0 %
Backlog backlog 10 %
Planned planned 20 %
In Progress in_progress 45 %
In Review in_review 60 %
Staging staging 75 %
Ready to Ship ready_to_ship 90 %
Production production 100 %
Deprecated deprecated excluded

Default transitions

From To
Draft Backlog
Backlog Draft, Planned
Planned Backlog, In Progress
In Progress Planned, In Review
In Review In Progress, Staging
Staging In Progress, Ready to Ship
Ready to Ship Staging, Production
Production Deprecated
Deprecated —

Who and how

  • Developers: Backlog → Planned → In Progress → In Review → Staging; In Review → In Progress; Staging → In Progress.
  • Admins: any stage except Production; Ready to Ship requires a passed QA result.
  • QA: Passed moves Staging → Ready to Ship; Failed moves the task to In Progress.
  • Promotion (Admins): Ready to Ship → Production.

Legacy task status (derived): Not Started (Draft, Backlog, Planned) · In Progress (In Progress, In Review) · Submitted (Staging, Ready to Ship) · Closed (Production, Deprecated). The value Needs Retest also exists for older records.

Separate from the workflow stage, modules have a catalogue status of Draft, Active or Archived, and submodules Active or Inactive.

Applies to QA runs, and as latest QA status to tasks and their parents. See QA execution and evidence.

Status Value Meaning
Pending pending Run created, waiting for a tester.
In Testing in_testing A tester started the run.
Passed passed Behaved as expected. Final.
Failed failed Didn’t behave as expected. Final.
Blocked blocked Couldn’t be tested. Final.
Needs Retest needs_retest A failed or blocked run whose task returned to Staging.

Transitions: Pending → In Testing → Passed, Failed or Blocked. Failed or Blocked → Needs Retest when the task re-enters Staging (a new Pending run is created).

QA severity: Critical, High, Medium, Low.

See Feedback and suggestions.

From To
New Triaged
Triaged In Progress
In Progress Fixed
Fixed Needs Retest
Needs Retest In Progress, Closed
Closed —
Won’t Fix —

Issue severity: Low, Medium, High, Critical.

See Task requests.

Status Meaning Open?
Draft Saved, not submitted. Yes
Pending Submitted, waiting for review. Yes
Reviewed Seen by an admin, not finalised. Yes
Published Converted into a new task, or merged into an existing one. No
Rejected Closed without becoming a task. No

Review actions: Mark as Reviewed → Reviewed · Publish as New Task → Published · Merge with Existing → Published · Reject Suggestion → Rejected.

See Approvals and releases.

Status Meaning
Pending Waiting for a decision.
Approved Signed off.
Rejected Turned down, with a reason.
Skipped No longer required by any rule. Returns to Pending if a rule requires it again.

Approval types: Developer Approved, QA Approved, Product Manager Approved, Admin Approved, Client Approved, Security Approved, Compliance Approved.

Status When
Not Ready Not in Ready to Ship or Production.
At Risk In Ready to Ship or Production, but with missing approvals, incomplete dependencies, failed QA, blocked or overdue items.
Ready Nothing missing.
Approved for Release Nothing missing, and a required Admin Approved approval is approved.

Ready and Approved for Release can be promoted without an override.

Status Meaning
Active Waiting on an unfinished item.
Blocked Waiting on something that is itself blocked.
Completed The item it waits on reached Ready to Ship, Production or Deprecated.
Ignored Deliberately set aside.
Status Effect
Active Can use their workspace.
Inactive Can sign in, but sees Access Pending.

Revoked members are Inactive and listed under archived users.

Critical, High, Medium, Low.