Triage Guide
This doc covers how we classify, prioritize, and route incoming issues in Linear.
Issue typesâ
There are two types of issues:
- Feature: a major new capability, either customer facing or internal
- Task: regular work that doesn't qualify as a feature
Priorities and SLAsâ
| Priority | SLA | Notes |
|---|---|---|
| Urgent | Immediate | Takes precedence over other work |
| High | 1 to 2 weeks | |
| Medium | 4 to 6 weeks | |
| Low | Best effort |
Triage outcomesâ
How to route an issue once you've classified it:
-
Urgent
- Assign to Michael
- Status: Triage
- Priority: Urgent
-
High
- If it falls under your squad, assign to a dev on your squad
- If it falls under the other squad, assign to that squad and add the corresponding Squad label
- If you're unsure which squad owns it, assign to Pickup tasks:
- Status: Todo
- Priority: High
- Label: Pickup
-
Medium or Low: add to pickup tasks. No immediate assignment needed.
-
Feature request / product design required / priority unclear
- Assign to Michael
- Status: Triage
- Label: Product required
Useful viewsâ
- General triage: the main triage queue
- Squad A: Upcoming tasks: features and tasks waiting for assignment
- Squad B: Upcoming tasks: features and tasks waiting for assignment
- Triage for Michael: items routed to Michael
- Triage for Product: items requiring product input
- Stale issues: tasks with no progress for over a month