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

Select all matching work for mobile batch planning #669

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

Product gap

Mobile operators can search and filter a queue, and can batch-plan selected cards, but must still tap every 44px checkbox individually. The search and batch-planning flows are not connected.

Evidence on origin/main (0fbe047): frontend/dashboard.js computes the active filtered/search result set as visible, while frontend/work-selection.js only supports one-at-a-time select/toggle. Historical issue-title review through #668 found no select-all-matches behavior; #661 added manual batch selection and #667 added active-queue search.

Vertical slice

While work-selection mode is active, let the operator select all currently matching eligible cards in visible queue order, clear the selection without exiting selection mode, and see an explicit 50-item-cap result. Existing Add to Today / Later today / Tomorrow actions then operate on that set.

Acceptance

  • Select all matches is scoped to the active queue, milestone, and search query.
  • Identities are deduplicated and preserve visible order.
  • At most 50 items are selected; cap status is explicit and existing selection is preserved.
  • Clear selection keeps selection mode active.
  • Controls are accessible 44px mobile targets with no narrow-screen overflow.
  • Focused behavioral tests and full suite pass.
## Product gap Mobile operators can search and filter a queue, and can batch-plan selected cards, but must still tap every 44px checkbox individually. The search and batch-planning flows are not connected. Evidence on `origin/main` (`0fbe047`): `frontend/dashboard.js` computes the active filtered/search result set as `visible`, while `frontend/work-selection.js` only supports one-at-a-time `select`/`toggle`. Historical issue-title review through #668 found no select-all-matches behavior; #661 added manual batch selection and #667 added active-queue search. ## Vertical slice While work-selection mode is active, let the operator select all currently matching eligible cards in visible queue order, clear the selection without exiting selection mode, and see an explicit 50-item-cap result. Existing Add to Today / Later today / Tomorrow actions then operate on that set. ## Acceptance - Select all matches is scoped to the active queue, milestone, and search query. - Identities are deduplicated and preserve visible order. - At most 50 items are selected; cap status is explicit and existing selection is preserved. - Clear selection keeps selection mode active. - Controls are accessible 44px mobile targets with no narrow-screen overflow. - Focused behavioral tests and full suite pass.
timmy self-assigned this 2026-08-12 18:20:37 +00:00
timmy closed this issue 2026-08-12 18:25:42 +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#669
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?