product-example 1 linked patterns checked
Jira Cloud What is a saved search
Documents saved work item searches as filters, including save-as flow, naming, ownership, privacy, sharing, starred filters, sidebar access, system filters, and rerunning a saved search.
Read with a purpose
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Saved search | Choose saved search when users need to store and rerun a named query or criteria set across sessions. | Saving stores query criteria, filters, sort, and scope as a reusable definition, not just the current result IDs. | Jira documents saved searches as named filters with ownership, privacy, sharing, starring, sidebar access, and rerun behavior. |
Comparisons supported by this source
- Saved search vs basic search vs filter panel vs recently viewed
Jira documents saved searches as named filters with ownership, privacy, sharing, starring, sidebar access, and rerun behavior.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: Atlassian Support. Last checked: .