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
`workstream`	—	Marks parent workstream issues — high-level delivery streams that contain child tasks
`focus-leadership`	business-focus	Work most relevant to strategic oversight, planning, or executive decision-making.
`focus-marketing`	business-focus	Work most relevant to the marketing team’s goals and priorities.
`focus-operational`	business-focus	Work most relevant to operational delivery, processes, or internal effectiveness.
`acquisition`	business-impact	Improves new patient acquistion or conversion.
`engineering`	business-impact	Internal engineering or platform investment.
`hybrid`	business-impact	Impacts both acquisition and ltv.
`ltv`	business-impact	Improves retention, reorder behaviour, or patient lifetime value.
`throughput`	business-impact	Improves operational efficiency, capacity, or delivery speed.
`marketing`	department	Issues raised by the marketing team.
`operations`	department	Issues raised by clinic and support teams.
`technical`	department	Issues raised by technical and engineering teams.
`enablement`	engineering-type	Improves developer productivity or unlocks future delivery.
`maintainability`	engineering-type	Improves code health, architecture, or long-term maintainability.
`observability`	engineering-type	Improves monitoring, analytics, alerting, or operational visibility.
`reliability`	engineering-type	Improves stability, resilience, or reduces production issues.
`scalability`	engineering-type	Improves system performance or ability to handle growth.
`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.
`operational`	type	Day-to-day operational work needed to support business and team functions.
`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
`focus-leadership`	business-focus	Work most relevant to strategic oversight, planning, or executive decision-making.
`focus-marketing`	business-focus	Work most relevant to the marketing team’s goals and priorities.
`focus-operational`	business-focus	Work most relevant to operational delivery, processes, or internal effectiveness.
`acquisition`	business-impact	Improves new patient acquistion or conversion.
`engineering`	business-impact	Internal engineering or platform investment.
`hybrid`	business-impact	Impacts both acquisition and ltv.
`ltv`	business-impact	Improves retention, reorder behaviour, or patient lifetime value.
`throughput`	business-impact	Improves operational efficiency, capacity, or delivery speed.
`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.
`enablement`	engineering-type	Improves developer productivity or unlocks future delivery.
`maintainability`	engineering-type	Improves code health, architecture, or long-term maintainability.
`observability`	engineering-type	Improves monitoring, analytics, alerting, or operational visibility.
`reliability`	engineering-type	Improves stability, resilience, or reduces production issues.
`scalability`	engineering-type	Improves system performance or ability to handle growth.

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.