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

Reopen recent work from mobile Queues #1471

New Issue
Closed
opened 2026-08-27 15:24:54 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-27 15:24:54 +00:00
Member
Copy Link

Problem

On mobile, leaving an issue, pull request, review, filed item, or update means finding it again through a queue or search. The Queues sheet has no recent-item return path, even though detail routes are canonical and recover missing items.

Vertical slice

  • Remember the five most recently opened detail routes per signed-in Gitea login.
  • Show them in a Recent work section in the mobile Queues sheet.
  • Deduplicate revisits, keep the newest item first, and never expose one account's history to another account or an unauthenticated shell.
  • Reopen a recent route through the existing route resolver and close the Queues sheet.
  • Clear the account-scoped history through normal private-device sign-out cleanup.

Acceptance tests

  1. Opening issue, pull, review, filed, and update details records safe canonical route metadata; revisiting moves an item to the front and the list is bounded to five.
  2. Recent rows render with useful item labels and 44px-or-larger mobile targets and reopen through the existing route controller.
  3. Histories are scoped by normalized login; missing login shows and stores nothing.
  4. Malformed persisted data/routes are discarded without breaking Queues.
  5. Focused tests and the full suite pass; packaged mobile behavior is exercised at a phone viewport.

No matching behavior exists in historical issue/PR titles or recent commits as of origin/main 46e06c1; recent work has focused on queue priority, workspace demand loading, and deep-link recovery, not a recent-item switcher.

## Problem On mobile, leaving an issue, pull request, review, filed item, or update means finding it again through a queue or search. The Queues sheet has no recent-item return path, even though detail routes are canonical and recover missing items. ## Vertical slice - Remember the five most recently opened detail routes per signed-in Gitea login. - Show them in a Recent work section in the mobile Queues sheet. - Deduplicate revisits, keep the newest item first, and never expose one account's history to another account or an unauthenticated shell. - Reopen a recent route through the existing route resolver and close the Queues sheet. - Clear the account-scoped history through normal private-device sign-out cleanup. ## Acceptance tests 1. Opening issue, pull, review, filed, and update details records safe canonical route metadata; revisiting moves an item to the front and the list is bounded to five. 2. Recent rows render with useful item labels and 44px-or-larger mobile targets and reopen through the existing route controller. 3. Histories are scoped by normalized login; missing login shows and stores nothing. 4. Malformed persisted data/routes are discarded without breaking Queues. 5. Focused tests and the full suite pass; packaged mobile behavior is exercised at a phone viewport. No matching behavior exists in historical issue/PR titles or recent commits as of origin/main 46e06c1; recent work has focused on queue priority, workspace demand loading, and deep-link recovery, not a recent-item switcher.
timmy was assigned by rockachopa 2026-08-27 15:24:54 +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#1471
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?