Feature Specification: Saved Search Filters

Author: Marcus Adeyemi Status: Approved Date: 5 June 2026 Target release: v3.2 Related PRD: Search & Discovery PRD

---

1. Summary and problem

Power users of our project-tracking app re-apply the same combinations of filters many times a day — for example "open tasks assigned to me, due this week, high priority." Today they rebuild that combination by hand each session, which is slow and error-prone. Saved Search Filters lets a user name and store a filter combination once and re-apply it in a single click.

2. Goals and non-goals

Goals

• Let a user save the current set of applied filters under a name and re-apply it later in one action.
• Let a user manage their saved filters: rename, update, and delete them.

Non-goals

• Sharing saved filters with other users or across a team (planned separately).
• Saving sort order or column layout alongside the filter set.

3. User stories

• As a daily user, I want to save my current filter combination so that I can return to it instantly tomorrow.
• As a user with several workflows, I want a list of my saved filters so that I can switch between views quickly.
• As a user whose needs change, I want to rename or delete a saved filter so that my list stays relevant.

4. Functional requirements

1. The user can save the currently applied filters by choosing "Save current filters" and entering a name.
2. Saved filters appear in a "Saved filters" menu, listed in the order they were created.
3. Selecting a saved filter clears any active filters and applies the saved combination.
4. The user can rename and delete any of their own saved filters.
5. Filter names must be unique per user; a duplicate name is rejected with a clear message.
6. Saved filters persist across sessions and devices for the signed-in user.

5. Acceptance criteria

• Given filters are applied, when the user saves them with a valid new name, then the filter appears in the Saved filters menu.
• Given a saved filter exists, when the user selects it, then the list updates to show only matching items and the filter name shows in the active-filter bar.
• Given a saved filter exists, when the user renames it to an unused name, then the new name appears everywhere the old one did.
• Given a saved filter exists, when the user deletes it and confirms, then it is removed from the menu and cannot be re-applied.
• Given the user enters a name already used by one of their saved filters, when they try to save, then the save is blocked and a "name already in use" message is shown.

6. Edge cases

Edge case	Expected behaviour
User has no saved filters yet	Menu shows an empty state with a short "save your first filter" hint.
User tries to save with no filters applied	The save action is disabled, with a tooltip explaining at least one filter is required.
Saved filter name left blank	Save is blocked and the name field shows a "name required" message.
Applied filter references a value that no longer exists (e.g. a deleted label)	The filter applies the parts it can and flags the missing value so the user can update it.
Save fails due to a network error	The user keeps their current filters, sees a non-blocking error, and can retry.

7. Dependencies

• The existing filter engine, which already applies multiple filters to the list view.
• Per-user persistence so saved filters follow the account across sessions and devices.

8. Out of scope

• Sharing or publishing saved filters to a team — handled in a later feature.
• Saving sort order, grouping, or column layout — this feature stores filter values only.

---

Open questions

• Should there be a cap on the number of saved filters per user? Owner: Marcus. To resolve before build.