Skip to main content

Labels

Labels tag tasks across your category structure. A category answers "where does this task live?"; labels answer everything else — which client, whether it's billable, how urgent it is.

Labels are trees​

Labels can nest, and the top-level label defines a tree. Trees work well as "field and values":

Billing
├── Billable
└── Non-billable
Client
├── Fjordvik Bakery
└── Nordlys Consulting
Urgent

Assign labels in the task editor. In the label picker you can search the whole tree ("ins" finds Channel › Instagram), and create new labels on the fly — type Client > New Name to build a path as you go.

By default a task can carry one value per tree — assigning Billable replaces Non-billable. That's what makes a tree act like a field. Trees that should allow several values at once (tags, essentially) can opt out. See One value per tree and Allowing multiple values.

Colors​

Each label can have its own color. Sub-labels inherit their parent's color unless they set their own — the deepest color set wins. The label's chip shows the effective color everywhere.

Showing labels in List​

Label chips on List rows are opt-in per tree, so your rows only show what you care about. Toggle Show in List on a tree's top label (the eye icon in its Edit dialog). Rows then show the assigned label's name in its color, with the full path in the tooltip.

This only affects what the rows display — the filter always offers every label, whether shown or not.

Filtering​

The Filter button in List and Calendar filters by labels:

  • Within one tree, several selections mean any of these (OR).
  • Across trees, selections combine (AND) — Billable and Fjordvik Bakery.
  • Selecting a parent covers everything under it.

Filters live in the page address, so a filtered view can be bookmarked or shared with a workspace member.

Managing labels​

The Labels page lists every tree with usage counts across sub-labels. From there you can create, rename, recolor and delete labels, and open a label's own page to see every task that carries it. Deleting a label with sub-labels deletes the whole subtree — you'll be asked to confirm when the labels are in use.