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

Batch-schedule selected mobile Search issues into Later #813

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

User problem

Mobile Search preserves selections across result pages, but batch planning only sends selected issues to Today. Scheduling to Later requires opening and deferring each result individually, which makes backlog triage slow and fragile on a phone.

Vertical slice

Add a distinct batch Defer path for selected Search issues. The operator chooses one return time, confirms once, and the dashboard claims eligible issues then adds successful items to Later in selection order using the existing durable claim journal and Later sync.

Evidence

  • frontend/search-batch-plan.js exposes only the Today queue action for selected results.
  • frontend/search-defer.js handles one preview result at a time.
  • frontend/later-work.js already supports adding a group at one wake time.
  • frontend/batch-find-work.js already provides owner-scoped checkpointed claims.
  • Historical issue/PR titles and recent commits cover single-result Search defer (#799/#800), Search batch-to-Today (#809/#810), and Updates batch defer (#659/#660), but not selected Search results to one Later time.

Acceptance criteria

  • At mobile width, selected Search results expose separate Add to Today, Defer, and Cancel actions without losing cross-page selection.
  • Defer asks for one valid future local time before any assignment.
  • Confirmation claims eligible issues sequentially, skips already-owned issues, and adds successful issues to Later at the exact chosen instant in selection order.
  • Interrupted claims resume without duplicate assignment or Later entries; per-item failures remain truthful and retryable.
  • Existing single-result defer and batch-to-Today behavior remains unchanged.
  • Behavioral tests cover the new flow and the full suite passes.
## User problem Mobile Search preserves selections across result pages, but batch planning only sends selected issues to Today. Scheduling to Later requires opening and deferring each result individually, which makes backlog triage slow and fragile on a phone. ## Vertical slice Add a distinct batch **Defer** path for selected Search issues. The operator chooses one return time, confirms once, and the dashboard claims eligible issues then adds successful items to Later in selection order using the existing durable claim journal and Later sync. ## Evidence - `frontend/search-batch-plan.js` exposes only the Today queue action for selected results. - `frontend/search-defer.js` handles one preview result at a time. - `frontend/later-work.js` already supports adding a group at one wake time. - `frontend/batch-find-work.js` already provides owner-scoped checkpointed claims. - Historical issue/PR titles and recent commits cover single-result Search defer (#799/#800), Search batch-to-Today (#809/#810), and Updates batch defer (#659/#660), but not selected Search results to one Later time. ## Acceptance criteria - At mobile width, selected Search results expose separate Add to Today, Defer, and Cancel actions without losing cross-page selection. - Defer asks for one valid future local time before any assignment. - Confirmation claims eligible issues sequentially, skips already-owned issues, and adds successful issues to Later at the exact chosen instant in selection order. - Interrupted claims resume without duplicate assignment or Later entries; per-item failures remain truthful and retryable. - Existing single-result defer and batch-to-Today behavior remains unchanged. - Behavioral tests cover the new flow and the full suite passes.
timmy self-assigned this 2026-08-14 08:50:28 +00:00
timmy closed this issue 2026-08-14 09:08:15 +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#813
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?