---
title: "Restore a saved view with all constraints"
description: "Verify that reopening a named saved search restores the complete query, filter combination, and ordering instead of only the view label."
canonical_url: "https://vostride.com/agent-library/search-filtering/saved-view-restoration.md"
md_url: "https://vostride.com/agent-library/search-filtering/saved-view-restoration.md"
content_kind: "recipe"
topic: "search-filtering"
---

# Restore a saved view with all constraints

Verify that reopening a named saved search restores the complete query, filter combination, and ordering instead of only the view label.

## Risk

Saved view implementations can persist a name while dropping an operator or sort direction. A meaningful check needs a result set where each stored setting changes either membership or order.

## Fixtures

- A test project contains three release issues with distinct priorities and statuses plus a non-release issue.
- The intended view uses query release, status Open, and priority descending, yielding Release gate before Release notes.
- The QA user owns a unique saved-view name and can delete it without affecting shared workspace views.

## Steps

1. Open issues, search release, select Open, and sort by priority descending; verify Release gate precedes Release notes.
2. Save the current state as QA release readiness and verify the saved view appears in the view menu.
3. Clear the query, status, and sort so the list visibly differs from the saved result.
4. Open QA release readiness and verify the query, status chip, and descending sort indicator are restored.
5. Verify the result contains exactly the two expected issue keys in the expected order, then reload and verify the same saved state.

## Expected results

- The saved definition contains three independent settings whose effects are visible in fixture membership and order.
- A reload preserves both the chosen view and the result semantics defined by the saved contract.
- The closed release issue and the unrelated issue remain excluded from the restored view.

## False-pass traps

- The saved-view title alone cannot prove its underlying definition was restored.
- Two equal priorities would make ascending and descending indistinguishable, so the fixture must avoid ties.

## Cleanup

- Delete the QA release readiness saved view and its issue fixtures.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Search and filtering QA recipes](/agent-library/search-filtering.md)
- [Software factory QA library](/agent-library.md)