How to Create Custom Views in Linear for PMs and Eng Leads
Most people in Linear live in two places: My Issues and their team's active cycle. That is fine for an engineer working a single queue, but PMs and engineering leads need to slice work across teams, projects, labels, and priorities. Rebuilding the same filter every morning wastes time and leads to inconsistent answers when two people look at 'the same' list.
Custom views solve this. A view is a saved combination of filters and display settings that you can keep personal, share with a team, or pin to your sidebar. This guide covers how to build views that answer specific recurring questions, how to choose grouping and layout, and a starter set of views that most product teams end up needing.
Working in Linear? Turn your spec into dependency-ordered tickets.
Paste the feature or spec. Vantage pulls out the requirements and breaks them into tickets, ordered by what blocks what, ready to groom with your team.
How this works
- We save what you typed. No AI runs on this page.
- You create a free account.
- Vantage builds a PRD and dependency-ordered tickets from it inside your own workspace.
Why ask for an account? We’re a small team, and a full generation runs a multi-step AI pipeline that costs us real money. So we tie it to a free account instead of running it anonymously. You also get to keep the result and edit it.
Your text is only used to create your project, and it stays private to your account. If you don’t sign up, we delete it after 7 days. Privacy policy
Step-by-step guide
Start from the question, not the filter
Before you click anything, write down the question the view should answer. 'What P0 and P1 bugs are open across all teams?' or 'What is in review for the checkout project?' are good questions. 'All issues' is not. A view tied to a clear question stays useful; a view built around a vague idea gets abandoned within a week.
- List the three or four questions you answer most often in standups and planning
- Note which teams, projects, and labels each question touches
- Decide who else needs the same answer
Build the filter
Open an issue list such as All Issues or a team's issues and add filters. Linear supports filtering on status, assignee, priority, label, project, cycle, estimate, creator, due date, and more, and you can combine multiple conditions. Use 'is any of' and 'is not' conditions to keep the filter tight. For cross-team views, start from the workspace-level issue list rather than a single team.
- Open the issue list that covers the right scope (team or workspace)
- Add filters for status, priority, labels, or project as needed
- Exclude noise such as canceled or duplicate issues
- Check the result count to make sure it matches your expectation
Set display options: layout, grouping, and ordering
Open the display options to switch between list and board layouts, choose a grouping (status, assignee, project, priority, label, cycle), and set an ordering. Sub-grouping is useful for leads: group by team and sub-group by status to see where each team's work sits. Choose which properties appear on each row so the view stays readable instead of crowded.
Save the view and choose its visibility
Save the configured filter as a view and give it a name that states the question, such as 'Open P0/P1 bugs, all teams'. Decide whether it is personal or shared with a team or workspace. Shared views are the single source of truth for recurring meetings, so give them clear names and an owner who keeps them accurate.
- Save the filter as a new view
- Name it after the question it answers
- Set it as personal or share it with the relevant team or workspace
- Add it to your favorites so it appears in the sidebar
Create a starter set of PM views
A handful of views covers most PM needs. 'In review, my projects' shows what is close to shipping. 'Blocked' shows issues with a blocked relation or a blocked label. 'Recently completed' filtered to the last seven days powers weekly updates. 'Unestimated in upcoming cycle' catches planning gaps before cycle start. 'Customer-reported bugs' filtered by label keeps support escalations visible.
Use project views for launch tracking
Inside a project you can also filter and save views scoped to that project's issues. For a launch, create a view grouped by milestone or label so you can see remaining work per release step. This is more useful in launch reviews than the full project list, because it answers 'what still blocks launch?' directly.
Prune views every quarter
Views accumulate. Once a quarter, delete views no one has opened, merge near-duplicates, and rename anything ambiguous. A short, trusted list of shared views beats a long list nobody is sure about.
Common mistakes
Building views without excluding canceled work
If you forget to filter out canceled and duplicate statuses, counts look inflated and people lose trust in the view. Always check the status filter.
Too many shared views with similar names
Three shared views called 'Bugs', 'Bugs 2', and 'Bug triage' guarantee that different people look at different data. Name views after the question they answer and remove duplicates.
Overloading rows with properties
Showing every property on every row makes the view hard to scan. Display only the properties needed to answer the view's question.
Tips
Share the view link in your standup or planning doc so everyone starts from the same list.
Pair a list view for detail with a board view grouped by status for quick visual scanning of the same filter.
Use a dedicated 'blocked' label alongside issue relations so blocked work is easy to filter.
Favorite your top three views so they sit in the sidebar and you stop navigating through menus.
How Vantage helps
Views are only as good as the metadata on the issues behind them. Tickets generated in Vantage arrive in Linear with priority, requirement links, and dependency relations already set, so filters for blocked work or a specific requirement return accurate results from the first day. Bi-directional sync keeps that metadata aligned with the PRD as work moves.