A label is a tag defined by the workspace and attached to any number of tickets. Use labels for whatever cross-cutting grouping the kind does not express: a component, a customer programme, a release, a "needs-decision" marker. Labels are the only tagging concept in SAQ; there are no custom fields, components, or epics as separate objects (a parent ticket serves as an epic).
How it relates to other concepts
- Labels are workspace-wide. Every project shares the same list.
- A label has no effect on billing, states, or notifications. It is for finding and grouping.
- Ticket lists, boards, and the API filter by one or more labels.
Rules
- Owners and Admins manage labels under Settings → Labels: add by name, rename inline, remove.
- Names are 1–60 characters and unique in the workspace.
- Removing a label removes it from every ticket that carries it.
- Setting labels on a ticket follows the ticket edit rules: Owners and Admins, any workspace user on an Inbox ticket, and full project members. A regular client user's labels are ignored.
- A ticket can carry many labels; there is no limit on the number of labels in the workspace.
Example
Acme keeps the labels checkout, payments, and needs-decision. A weekly review filters the board on needs-decision across all projects; when a decision lands, the label is removed from the ticket.