Quick answer: A saved view is a named, persistent filter in a bug tracker that displays a particular subset of issues according to criteria you define, such as status, owner, priority, or occurrence. Instead of building the same filter repeatedly, you save it once and open it anytime, keeping your focus on a relevant slice rather than the whole backlog.
As your bug list grows, looking at all of it at once becomes overwhelming and useless, you need to see specific slices: the bugs assigned to you, the highest-impact issues, the ones for this release. A saved view is the tool for that. It stores a filter so you can return to a focused, relevant subset with one click, rather than rebuilding the same query every time or drowning in the full list. Saved views are what make a large bug tracker actually workable day to day.
What a Saved View Is
A saved view is a filter you have defined and named for reuse. You specify criteria, status, assignee, priority, label, occurrence threshold, version, and save the resulting view. From then on, opening that view shows you exactly that slice of your bugs, kept up to date as issues change. It is essentially a stored question about your bugs ('show me all high-priority open issues assigned to me') that you can ask again instantly.
Common saved views include 'my open bugs' (what I personally need to work on), 'top issues by occurrence' (the highest-impact problems), 'needs triage' (new reports not yet reviewed), 'unassigned' (issues with no owner, at risk of being dropped), and 'this release' (bugs targeted for the current update). Each gives you a focused working list for a specific purpose.
Why Saved Views Matter
The core value is focus. A large bug backlog is overwhelming to face all at once, but you almost never need to, you need the relevant slice for whatever you are doing. Saved views keep the overwhelming full list out of sight and put a manageable, purpose-built subset in front of you. This is one of the most effective antidotes to bug-list overwhelm: you work from a short focused view, while the full backlog stays available but not in your face.
Saved views also make recurring workflows fast. Triage means opening 'needs triage'; your daily work means opening 'my open bugs'; release planning means opening 'this release.' Each routine becomes one click to the right list, rather than rebuilding the same filter each time. For teams, per-owner views let each person see their own queue without wading through everyone else's.
Saved Views in Your Workflow
Saved views turn a bug tracker from a flat database into a set of purpose-built workspaces. The discipline is to set up views matching your actual workflows, the questions you ask repeatedly, so that each part of your process has a ready-made list. Once configured, your tracker meets you where you are: triage view for triaging, impact view for prioritizing, personal view for working.
Bugnet's saved views let you store filtered, sorted views like 'top by occurrence', 'my open bugs', or 'needs triage' and jump straight to them. This is what keeps a tracker with a large backlog usable: you live in focused views matched to your tasks rather than scrolling the whole list, and during a busy period like a launch, a pinned 'top issues by occurrence' view keeps the short list that matters in front of you instead of the full firehose.
A saved view is a stored question about your bugs. Open 'top by occurrence' or 'my open bugs' in one click instead of drowning in the full list.