What a saved view actually is
You spent a while tuning a filter in GitHub Projects and now the view shows exactly the slice of work you needed.
A small question follows: should this become a permanent tab, or was it a one-off look that you can discard?
Saving turns a filter into a saved view on the project instead of a private unsaved change — and a saved view is something you will have to keep meaningful.
This guide walks through when a filter earns a saved view, when a temporary filter is the better choice, and what actually happens to unsaved changes while you decide.
In GitHub Projects, each view appears as a separate tab in your project.
GitHub's documentation gives three typical examples.
One view shows all items not yet started, filtered on status.
Another shows workload per team, grouped by a custom team field.
A third sorts by a date field so the earliest ship dates come first.
A saved view is simply a named combination of layout, filters, grouping and sorting that lives on its own tab.
When you click “New view” to the right of your existing views, the new view is automatically saved, according to GitHub’s view management documentation.
So in practice, creating a view and saving it are the same action.
The real decision is not “save or not” at creation time.
It is whether a view you have been experimenting with should stay as a tab, be renamed into something your team recognizes, or be deleted.
What happens while your filter is unsaved
This is the part most people discover by accident.
When you change a view — sorting, reordering, filtering or grouping — a dot appears next to the view name to indicate unsaved changes.
GitHub documents two important facts about that state:
- If you do not want to keep the changes, you can simply ignore the indicator.
- No one else will see your changes until you save them.
That second point changes the decision entirely.
An unsaved filter is private.
You can slice the project by assignee, label or status, poke around, and close the tab without anyone noticing.
Saving turns the filter into a saved view on the project rather than a private unsaved change.
The question is whether this slice deserves that status.