Structure
Labels and templates keep work classified and consistent.
Labels
Labels are how work gets classified for filtering, views, and reporting, since Linear has no issue types.
| Scope | What it’s for |
|---|---|
| Workspace labels | Categories every team shares, like Bug or Security. Usable and reportable across all teams. |
| Team labels | Categories that only make sense inside one team. Sub-teams optionally inherit them from their parent. |
| Label groups | A set of mutually exclusive labels, like Type/Bug and Type/Feature. An issue takes at most one label from a group. |
Apply labels with L on any issue, and manage them in settings, where labels can be merged, archived, or moved between scopes as your taxonomy settles.
Templates
Templates pre-fill structure so recurring work arrives consistent and complete.
- Issue templates carry preset properties and descriptions for things like bug reports and incident write-ups, and a team can set one as its default so it applies automatically.
- Project templates start a new project with its milestones, properties, and documents in place, for repeatable kinds of work like launches.
- Document templates standardize the documents teams write repeatedly, like PRDs, decision logs, and retros.
Estimates
Estimation is off by default and enabled per team in Team settings → General → Estimates, where you pick a scale. An estimate field then appears on the team’s issues, along with effort options in view filters, display settings, and Insights.
Go deeper
- Labels. Scopes, groups, and label management.
- Issue templates. Standard and form templates, and defaults.