Saved Triage Filters in Linear
Save a custom issue view with Triage explicitly included in its status filter. Default views can omit triage issues because they sit outside the normal team workflow.
Step-by-step guide
Check access and scope
Triage must be enabled for the team, and you need permission to create the intended shared or personal view.
Include Triage status
Open the team issue list and add a status filter including Triage.
Narrow the review scope
Add a focused ownership or label filter for the review question.
- Worked example: Name a view Mobile triage: needs reproduction. Filter for Triage plus the needs-reproduction label so the meeting focuses on evidence gaps rather than the whole backlog.
Save the custom view
Save the filtered list as a custom view and name it by its purpose. A filtered team list can be saved using Option/Alt V or its Save view control; a new issue view can also be created from Views.
Choose review fields
Choose useful displayed fields such as priority, age and assignee.
Process matching issues
Review matching issues and accept, snooze, decline or mark duplicates deliberately.
Verify the result
Create a harmless matching issue and confirm it appears; remove the label and confirm it leaves the view.
Common mistakes
Avoid the main failure mode
A saved list is not an automatic routing rule. It displays matching records; it does not assign or accept them.
Check the handoff edge case
Naming a view simply Triage does not explain its scope. Include the owning team or evidence gap so reviewers understand exclusions.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.