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

Make the mobile Work action launch the highest-priority queue #755

New Issue
Closed
opened 2026-08-13 16:49:46 +00:00 by timmy · 0 comments
timmy commented 2026-08-13 16:49:46 +00:00
Owner
Copy Link

Problem

The persistent mobile Work dock action only understands Today and generic Find Work, even though the dashboard already exposes urgent Attention, resumable Updates triage, Agenda, Later, and Draft queues. Operators must open the queue switcher and decide where to continue, and the Work label can point at lower-priority Today work while Attention is waiting.

Slice

Make Work a deterministic one-tap continuation action: preserve an active Today session, then route to Attention, resumable/planned Today, Updates, Agenda, Later, Drafts, and finally Find Work. Keep the visible label and accessible name synchronized with the actual destination as queue state changes.

Acceptance

  • An active Today session always continues.
  • Otherwise Attention precedes Today; Today precedes Updates; Updates precede Agenda, Later, and Drafts.
  • Existing Updates triage is resumed through its normal launcher.
  • Empty queues fall back to Find Work.
  • The dock label and aria-label describe the same destination it opens.
  • Focus and 320px/44px mobile dock behavior remain intact.
  • Focused and full automated suites pass.

Evidence

frontend/mobile-work-entry.js only routes Today/Plan/Find. frontend/mobile-queue-launcher.js has cross-queue routing but its continuation list omits Updates, and frontend/dashboard.js wires Work only to the Today-centric entry. Historical issue-title and recent-commit review found queue-completion handoffs and individual resumable queue work, but no universal pre-completion Work action.

## Problem The persistent mobile **Work** dock action only understands Today and generic Find Work, even though the dashboard already exposes urgent Attention, resumable Updates triage, Agenda, Later, and Draft queues. Operators must open the queue switcher and decide where to continue, and the Work label can point at lower-priority Today work while Attention is waiting. ## Slice Make **Work** a deterministic one-tap continuation action: preserve an active Today session, then route to Attention, resumable/planned Today, Updates, Agenda, Later, Drafts, and finally Find Work. Keep the visible label and accessible name synchronized with the actual destination as queue state changes. ## Acceptance - An active Today session always continues. - Otherwise Attention precedes Today; Today precedes Updates; Updates precede Agenda, Later, and Drafts. - Existing Updates triage is resumed through its normal launcher. - Empty queues fall back to Find Work. - The dock label and aria-label describe the same destination it opens. - Focus and 320px/44px mobile dock behavior remain intact. - Focused and full automated suites pass. ## Evidence `frontend/mobile-work-entry.js` only routes Today/Plan/Find. `frontend/mobile-queue-launcher.js` has cross-queue routing but its continuation list omits Updates, and `frontend/dashboard.js` wires Work only to the Today-centric entry. Historical issue-title and recent-commit review found queue-completion handoffs and individual resumable queue work, but no universal pre-completion Work action.
timmy self-assigned this 2026-08-13 16:49:46 +00:00
timmy closed this issue 2026-08-13 17:02:13 +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#755
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?