Saved search state and management decisions
Review what a saved search name says about its current criteria
Review the boundary between a saved definition and a temporary edit using controlled create, update, and reopen evidence.
- ✓The name implies the edit was saved
- ✓Update has an unclear target
- ✓Rename and criteria changes overlap
Make the stored-versus-working distinction reviewable
Saved state made explicit
Show when current criteria differ from the definition a customer expects to reopen.
Management actions separated
Keep renaming and updating criteria from becoming one ambiguous finding.
Reopened evidence
Check the stored definition after a deliberate update instead of relying on a confirmation label.
Review the difference between saved and changed
A coordinator opens a saved search called Sample renewals, adds another status filter, and later returns believing that change was stored. The management list shows the same name without explaining that the edit was temporary. Review how your application distinguishes a saved definition from a modified working search. This concerns your app's saved-search feature, not a search storage service provided by Retick.
Capture the definition before and after editing
Use synthetic names and harmless seeded records. Record creating a saved search, changing its current criteria, leaving the page, and reopening it from management. Note build, viewport, starting criteria, and whether the product requires an explicit update action. Keep personal search names and private query details outside the recording. Use supported browser capture or upload authorized media that shows the sequence rather than only the management list.
Name the uncertain persistence state
A concrete issue is Modified saved search lacks an unsaved-state indicator. Inspect AI candidate findings in Retick and edit any draft that treats a temporary change as confirmed data loss. Annotate the unchanged saved name beside the modified criteria. Keep renaming, updating a definition, and deleting a saved entry as separate decisions. Reject a proposed automatic-save behavior unless the product owner has explicitly chosen that model.
Example acceptance criteria
When working criteria differ from the saved definition, the interface should communicate that difference using the agreed indicator. The update action should clearly identify which saved search it affects. Reopening after an explicit update should restore the approved synthetic criteria, while leaving without saving should follow the documented product rule. Verify both branches directly and confirm that a rename does not unexpectedly replace the underlying definition.
Recheck management operations in context
Use a review cycle to retain create, modified, and reopened states. Follow up with duplicate display names, a long name, cancelling a deletion, and opening the saved search from its usual entry point. Export reviewed files or selected individual-media findings to Trello. Retick does not persist these searches for your app or validate their query behavior. Storage correctness, sharing rules, and permissions require separate application testing; the review establishes whether visible state communicates the intended management model.
Review what reopening a saved search should restore
Capture a temporary edit and an explicit update as different branches.