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

Batch-claim available work into Today from Find Work #671

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

User problem

Find Work only supports one issue at a time. On mobile, filling Today from unassigned work requires repeatedly claiming, leaving the sheet, reopening it, refreshing, and finding the next issue. Existing batch planning applies only to already-owned My Work.

Vertical slice

Add a selection session inside Find Work that persists across loaded pages, preflights Today capacity before any mutation, claims selected issues sequentially through the existing secure claim route, queues each confirmed assignment into Today, continues after assignment races, and reports truthful per-item outcomes while keeping the sheet open.

Acceptance

  • Select unique available issues across loaded pages with an accessible count and mobile-safe sticky controls.
  • Block the entire batch before claiming when selected work exceeds remaining Today capacity.
  • Claim and queue in selected order; queue only after confirmed assignment.
  • Continue after one claim conflict and summarize queued/unavailable outcomes.
  • Never retry successful rows or duplicate Today entries.
  • Preserve existing Assign, Queue Today, and Start now actions.
  • Focused behavioral tests and full suite pass.

Non-duplication evidence

Historical issues #175/#179/#181/#213 cover discovery and pagination; #411 and #415 cover single-item assign/start and queue; #633/#661/#669 cover planning already-owned work. No historical title or recent main commit implements multi-select claiming in Find Work.

## User problem Find Work only supports one issue at a time. On mobile, filling Today from unassigned work requires repeatedly claiming, leaving the sheet, reopening it, refreshing, and finding the next issue. Existing batch planning applies only to already-owned My Work. ## Vertical slice Add a selection session inside Find Work that persists across loaded pages, preflights Today capacity before any mutation, claims selected issues sequentially through the existing secure claim route, queues each confirmed assignment into Today, continues after assignment races, and reports truthful per-item outcomes while keeping the sheet open. ## Acceptance - Select unique available issues across loaded pages with an accessible count and mobile-safe sticky controls. - Block the entire batch before claiming when selected work exceeds remaining Today capacity. - Claim and queue in selected order; queue only after confirmed assignment. - Continue after one claim conflict and summarize queued/unavailable outcomes. - Never retry successful rows or duplicate Today entries. - Preserve existing Assign, Queue Today, and Start now actions. - Focused behavioral tests and full suite pass. ## Non-duplication evidence Historical issues #175/#179/#181/#213 cover discovery and pagination; #411 and #415 cover single-item assign/start and queue; #633/#661/#669 cover planning already-owned work. No historical title or recent main commit implements multi-select claiming in Find Work.
timmy self-assigned this 2026-08-12 18:50:10 +00:00
timmy closed this issue 2026-08-12 19:02:55 +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#671
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?