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

Continue mobile work across queue boundaries #683

New Issue
Closed
opened 2026-08-12 21:50:51 +00:00 by timmy · 0 comments
timmy commented 2026-08-12 21:50:51 +00:00
Owner
Copy Link

Problem

Mobile queue flows stop at queue boundaries. Clearing the final unread Update closes the sheet and announces Inbox cleared., even when Attention, Today, Later, or Drafts still contain actionable work. The operator must reopen Queues and decide where to continue.

Slice

Add an accessible mobile queue-completion handoff. When Updates is exhausted, recommend the highest-priority currently actionable destination (Attention → Today → Later → Drafts → Find Work), show its live count, and launch it without mutating Gitea. Revalidate availability at launch and fall through when counts changed. Offer Choose another queue and Done for now.

Acceptance

  • Clearing the last Update presents a focused Updates cleared completion dialog instead of a dead end.
  • Primary action recommends the first available destination in priority order with count-aware copy.
  • Launch re-evaluates queue state, skips a now-empty destination, and uses existing queue launch behavior.
  • With no owned work, primary action opens Find Work.
  • Dialog is keyboard/screen-reader operable and mobile safe-area aware.
  • Existing within-queue next behavior remains unchanged.
  • Behavioral tests cover resolver priority, stale counts, no-work fallback, wiring, and accessibility.
## Problem Mobile queue flows stop at queue boundaries. Clearing the final unread Update closes the sheet and announces `Inbox cleared.`, even when Attention, Today, Later, or Drafts still contain actionable work. The operator must reopen Queues and decide where to continue. ## Slice Add an accessible mobile queue-completion handoff. When Updates is exhausted, recommend the highest-priority currently actionable destination (Attention → Today → Later → Drafts → Find Work), show its live count, and launch it without mutating Gitea. Revalidate availability at launch and fall through when counts changed. Offer Choose another queue and Done for now. ## Acceptance - Clearing the last Update presents a focused `Updates cleared` completion dialog instead of a dead end. - Primary action recommends the first available destination in priority order with count-aware copy. - Launch re-evaluates queue state, skips a now-empty destination, and uses existing queue launch behavior. - With no owned work, primary action opens Find Work. - Dialog is keyboard/screen-reader operable and mobile safe-area aware. - Existing within-queue next behavior remains unchanged. - Behavioral tests cover resolver priority, stale counts, no-work fallback, wiring, and accessibility.
timmy self-assigned this 2026-08-12 21:50:51 +00:00
timmy closed this issue 2026-08-12 21:59:43 +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#683
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?