Each area carries one quiet hue worn as a 3px left edge on every card, so a mixed day reads at a glance as 'two pipeline, one invoicing'. Inside an area, tasks cluster under the snapshot label of the thing they are about, such as a job name. Groups collapse.
Also called: task categories · tasks by project · tasks by customer · task colour coding
- 1A task's category comes from an explicit choice by the junction, else the canonical module id from the shared context envelope, else id-guessing from project/estimate/opportunity/contact.
- 2The sub-group is context_label, a label captured at creation time and kept — not a join.
- 3Category chips above the list filter to one area; a client/job Select filters to one context label.
Migration 166 spells out both halves. On grouping: “A flat list stops being usable at about thirty items… Those are the same top-level places in the left nav, so the hub mirrors the mental map people already have rather than inventing a second taxonomy.” On the snapshot: resolving the sub-group at read time “means a lookup per task against four different tables, and it breaks entirely once the project is archived or the estimate link is replaced.” The colours are deliberately restrained — 'enough that a mixed day reads at a glance, never enough to tint the surface'.
- A flat list becomes unusable past thirty items
- Read-time joins break on archived projects
- No visual separation between areas of the business
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →