Practice Reference
Workspace Labels
This page documents the current Linear labels used across the workspace so teams can classify work consistently during validation, planning, and delivery.
Workspace labels are available across the organization. Team-specific labels are only shown where we intentionally call them out.
Workspace Issue Labels
These labels are available at workspace level and can be used across teams.
| Label | Group | Description |
|---|---|---|
prod | env | Affects production, or requires changes, validation, or coordination in production. |
staging | env | Affects staging, or requires changes, validation, or coordination in staging. |
design | flag | Design input, review, or a design decision is required before the issue can move forward. |
requirements | flag | Product input, clarification, or a requirements decision is required before the issue can move forward. |
requirements-tech | flag | Technical input, review, or an implementation decision is required before the issue can move forward. |
mobile | platform | Affects the mobile app experience or mobile-specific functionality. |
web | platform | Affects the web app experience, browser-based functionality, or web-specific implementation. |
bug | type | A defect, regression, or unintended behaviour that needs to be fixed. |
chore | type | Routine maintenance, cleanup, or operational work that does not directly add user-facing functionality. |
feature | type | New or improved user-facing functionality being added to the product. |
investigation | type | Investigation, discovery, or root-cause analysis before deciding on implementation work. |
report | type | A reported problem, observation, or incident that needs review or follow-up. |
suggestion | type | A proposed idea, improvement, or enhancement that has not yet been committed as planned work. |
Workspace Project Labels
These labels are used on Linear projects and drive roadmap reporting such as commitment and confidence.
| Label | Group | Description |
|---|---|---|
committed | commitment | Uses the Linear target date directly for reporting. |
target | commitment | Treats the Linear target date as optimistic in reporting, with the confidence buffer added to calculate the pessimistic date. |
high | confidence | Adds a 20% buffer to the optimistic target date to calculate the pessimistic date in reporting. |
low | confidence | Adds a 60% buffer to the optimistic target date to calculate the pessimistic date in reporting. |
medium | confidence | Adds a 40% buffer to the optimistic target date to calculate the pessimistic date in reporting. |
Technical Team Label
project-request is a team-specific issue label owned by the Technical team, so
it does not appear in the workspace-wide issue label list above.
| Label | Group | Description |
|---|---|---|
project-request | category | Request issues that may be converted into one or more projects, while the original issue remains the discovery request. |