stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Save and reopen synced mobile Search views #821

New Issue
Closed
opened 2026-08-14 10:34:05 +00:00 by timmy · 0 comments
timmy commented 2026-08-14 10:34:05 +00:00
Owner
Copy Link

Evidence

Mobile Search already supports query, type, status, and repository scopes, but frontend/commands.js keeps them only in memory/URL state. Operators must rebuild recurring searches on every session and device. No historical issue title/body or recent commit implements saved or pinned searches.

User flow

  1. Enter a scoped mobile Search and save it with a short name.
  2. Reopen the named search with one tap on any signed-in device.
  3. Rename or delete saved searches without affecting Gitea work.
  4. Ad-hoc Search remains usable when synchronization fails.

Acceptance criteria

  • Saved search records are bounded, validated, revisioned, account-scoped, and durable.
  • Save/list/rename/delete synchronize through authenticated no-store APIs and reject stale revisions instead of overwriting newer state.
  • Opening a saved search restores query, type, status, and repository and runs exactly one search.
  • Mobile controls are accessible and touch-sized; errors are truthful and retryable.
  • Behavioral store/API/controller/render tests and the full suite pass.
  • Closes via a tested PR and produces a new release after merge.
## Evidence Mobile Search already supports query, type, status, and repository scopes, but `frontend/commands.js` keeps them only in memory/URL state. Operators must rebuild recurring searches on every session and device. No historical issue title/body or recent commit implements saved or pinned searches. ## User flow 1. Enter a scoped mobile Search and save it with a short name. 2. Reopen the named search with one tap on any signed-in device. 3. Rename or delete saved searches without affecting Gitea work. 4. Ad-hoc Search remains usable when synchronization fails. ## Acceptance criteria - Saved search records are bounded, validated, revisioned, account-scoped, and durable. - Save/list/rename/delete synchronize through authenticated no-store APIs and reject stale revisions instead of overwriting newer state. - Opening a saved search restores query, type, status, and repository and runs exactly one search. - Mobile controls are accessible and touch-sized; errors are truthful and retryable. - Behavioral store/API/controller/render tests and the full suite pass. - Closes via a tested PR and produces a new release after merge.
timmy self-assigned this 2026-08-14 10:34:05 +00:00
timmy closed this issue 2026-08-14 10:49:03 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#821
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?