Assignees, priority & labels
The three fields that tell you who owns a task, how urgent it is, and what bucket it belongs to.
Assignees
A task can have zero, one, or many assignees. The common case is one — a single owner accountable for the task. Use multiple assignees sparingly, usually for pairing or a temporary hand-off.
Zero assignees is a valid state. It means “this task exists but nobody has picked it up yet.” Board views surface unassigned tasks in the top column so the team can claim them.
Priority
Priority is a five-point scale: urgent, high, medium, low, none. It's always optional — a task with no priority is fine.
Treat urgent as a real bar: something that demands the team's attention today. Overusing urgent dilutes it. Most tasks are medium or none.
Labels (tags)
tags is a free-form string array. Use it for cross-cutting classification that doesn't fit status, priority, or project membership:
- Technical buckets —
frontend,infra,db - Process states —
blocked,needs-review,waiting-customer - Quarter or theme —
q2-mobile,polish
Tags auto-complete from existing values in the base. Keep the set small — if a tag is only ever on one task, it probably doesn't need to exist.
When to use which
A rough decision tree:
- Is it a workflow stage? → status
- Does it say how urgent the task is? → priority
- Does it say who owns it? → assignees
- Everything else → tags