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

Launch the next item directly from mobile work queues #645

New Issue
Closed
opened 2026-08-12 11:20:09 +00:00 by timmy · 0 comments
timmy commented 2026-08-12 11:20:09 +00:00
Owner
Copy Link

Evidence

The mobile Work queues sheet says “Choose what to work through next,” but frontend/mobile-task-dock.js closes it and frontend/dashboard.js::openMobileQueue only applies a filter, scrolls, and focuses My Work. Operators must then scan and tap a card even though issue, PR, update, Today, and Draft flows already support direct opening and sequential navigation. Historical issue review found the queue switcher (#627), Today entry (#611), Updates queue (#639), and Draft filing (#629), but no direct queue-to-item launch.

User impact

On phones, reduce starting work to Queues → queue, while preserving the selected queue, existing details, offline behavior, and sequential controls. Empty queues stay truthful and announce that no item is available.

Acceptance tests

  • Today delegates to existing continue/resume/start/plan behavior.
  • Attention, Updates, and Later select their filter and open the first eligible card directly.
  • Drafts selects its filter and invokes the first actionable draft control.
  • Empty queues keep the operator in context and announce a queue-specific empty state.
  • Queue sheet focus restoration and overlay dock hiding remain intact.
  • At phone widths, existing detail overlays and Previous/Next controls remain usable without horizontal overflow.
  • Focused and full automated suites pass.
## Evidence The mobile **Work queues** sheet says “Choose what to work through next,” but `frontend/mobile-task-dock.js` closes it and `frontend/dashboard.js::openMobileQueue` only applies a filter, scrolls, and focuses My Work. Operators must then scan and tap a card even though issue, PR, update, Today, and Draft flows already support direct opening and sequential navigation. Historical issue review found the queue switcher (#627), Today entry (#611), Updates queue (#639), and Draft filing (#629), but no direct queue-to-item launch. ## User impact On phones, reduce starting work to **Queues → queue**, while preserving the selected queue, existing details, offline behavior, and sequential controls. Empty queues stay truthful and announce that no item is available. ## Acceptance tests - Today delegates to existing continue/resume/start/plan behavior. - Attention, Updates, and Later select their filter and open the first eligible card directly. - Drafts selects its filter and invokes the first actionable draft control. - Empty queues keep the operator in context and announce a queue-specific empty state. - Queue sheet focus restoration and overlay dock hiding remain intact. - At phone widths, existing detail overlays and Previous/Next controls remain usable without horizontal overflow. - Focused and full automated suites pass.
timmy self-assigned this 2026-08-12 11:20:09 +00:00
timmy closed this issue 2026-08-12 11:28:52 +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#645
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?