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

Pin frequent work across signed-in mobile devices #1477

New Issue
Closed
opened 2026-08-27 18:23:03 +00:00 by timmy · 0 comments
timmy commented 2026-08-27 18:23:03 +00:00
Owner
Copy Link

User problem

Recent work retains only five items, so a release issue, pull request, or review that an operator revisits on mobile is displaced by incidental opens. There is no durable one-tap return path that survives device changes without changing ownership or queue state.

Vertical slice

Add a touch-safe Pin/Unpin action to Recent work. Pinned items appear in a Pinned work section above Recent work, survive the five-item recent limit, work offline-first, synchronize to the confirmed account, and open through the existing canonical detail route.

Evidence

  • frontend/mobile-recent-work.js bounds synchronized recent items to five and renders only an Open action.
  • src/recent_work_store.py already supplies encrypted account-scoped persistence and canonical route validation.
  • Historical issue-title review found only Recent work open/sync work (#1471/#1475); pin-related titles concern infrastructure, not saved user work.
  • No open issue or PR overlaps this behavior.

Acceptance

  • Pinning immediately places an item above Recent work and announces pending sync when offline.
  • Pins remain after six or more unrelated opens and synchronize to another session for the same confirmed login.
  • Unpin removes only the pin; a still-recent item remains in Recent work.
  • Pinned items use canonical in-app routes; data remains encrypted and account scoped.
  • Pin and Open controls are independently keyboard/touch accessible, at least 44px high, and do not overflow at 320px width.
  • Behavioral store, API, frontend, and rendered mobile tests pass.
## User problem Recent work retains only five items, so a release issue, pull request, or review that an operator revisits on mobile is displaced by incidental opens. There is no durable one-tap return path that survives device changes without changing ownership or queue state. ## Vertical slice Add a touch-safe Pin/Unpin action to Recent work. Pinned items appear in a Pinned work section above Recent work, survive the five-item recent limit, work offline-first, synchronize to the confirmed account, and open through the existing canonical detail route. ## Evidence - `frontend/mobile-recent-work.js` bounds synchronized recent items to five and renders only an Open action. - `src/recent_work_store.py` already supplies encrypted account-scoped persistence and canonical route validation. - Historical issue-title review found only Recent work open/sync work (#1471/#1475); pin-related titles concern infrastructure, not saved user work. - No open issue or PR overlaps this behavior. ## Acceptance - Pinning immediately places an item above Recent work and announces pending sync when offline. - Pins remain after six or more unrelated opens and synchronize to another session for the same confirmed login. - Unpin removes only the pin; a still-recent item remains in Recent work. - Pinned items use canonical in-app routes; data remains encrypted and account scoped. - Pin and Open controls are independently keyboard/touch accessible, at least 44px high, and do not overflow at 320px width. - Behavioral store, API, frontend, and rendered mobile tests pass.
timmy self-assigned this 2026-08-27 18:23:03 +00:00
timmy closed this issue 2026-08-27 18:46:57 +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#1477
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?