Task Statuses and Workflows

Task Statuses and Workflows

Task Statuses and Workflows

A task’s status says where it stands in your process. In AB Projects the status set is fully yours — per project, configurable, and colour-coded — so AB adapts to how your team already works.

Statuses are per-project and configurable

  • When a project is created it’s seeded with a starter set of statuses based on the project type (a template) — not a single fixed list. If a project already has statuses, the starter set is left alone.
  • Admins manage statuses in the project’s task options: add or rename statuses, set each one’s colours (badge text/background), and set the display order so they read in the right sequence.
  • Every project can have a different set — different teams/departments, different stages.

Auto-progress & the “complete” status

  • Each status can carry an auto-progress %. Moving a task to that status automatically sets its progress — e.g. In Progress → 10%, Testing → 60% — so progress stays consistent without manual bookkeeping.
  • One status is designated as the “marks task complete” status (typically 100%). Moving a task there completes it; you don’t track “done” separately from status.

Changing a task’s status

  • Open the task and use the status panel (click the status badge, or the ··· menu).
  • You’ll be asked for a short reason for the change.
  • The change — who, when, why — is written to the task’s change history and posted to the linked Teams channel, so a status move always carries its context.
  • There are no enforced transitions — any status can move to any other. AB doesn’t impose a state machine; your status set is the workflow.

Seeing work by status

  • The Board view groups tasks into columns by status — the fastest way to see flow and bottlenecks.
  • Statuses render as coloured badges (with localized names) across the list, board, and task detail.
  • AI assistants set status by the project’s own status IDs, so automation respects your configured set.

Best practices

  • Keep the set small and meaningful — only statuses the team will actually use.
  • Use auto-progress intentionally so the percentage reflects reality as work moves.
  • Use Board view to review flow regularly and prune statuses that cause confusion.

With per-project, colour-coded statuses and auto-progress, AB Projects fits your process — not the other way around — while every status change stays accountable and visible to the team.

Published on 2025-07-07
Last updated on 2026-05-18
Version 6