About this block

Saved Searches Manager is the settings side of saved searches, distinct from the apply time pills or tabs: a panel where each row lists a search by name, its mono query string (status:open label:bug assignee:me), a visibility badge for Private or Team, the owner avatar, and when it was last used. Star, edit, and delete actions sit at the end of every row. The header carries a saved count badge and a New saved search button, and a footer line explains that team searches are shared across the workspace while private ones stay with you and the default runs when you open the issues page.

Searches are one array with a uniform shape, so every row renders the same query, visibility, and owner without optional key guards. The star toggles the default with aria-pressed so only one search leads, and the visibility badge swaps a lock icon for a users icon by field.

When to use

Reach for this block on the manage saved searches screen, wired to your searches API so renames, deletes, and default changes persist for the owner or for the whole workspace. Keep it separate from the switcher users tap to apply a search; this surface is where they curate the list itself.

A natural flow around it on an Application Pro page:

Before

• App shell
• Saved views tabs

After

• Data table
• Dialogs

What you can display

One strong use is the saved issue searches manager. Other saved query lists:

• Report definitions. Named metric queries with an owner and a last run time.
• Segment library. Customer segments marked private or shared across the team.
• Alert rules. Saved log queries behind a notification, each with a visibility badge.

Tip: show the raw query under every name; a saved search with no visible definition becomes a mystery box the moment its author moves on.