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

Respect Today time capacity when batch-planning mobile Search #811

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

Problem

Mobile Search batch planning enforces Today item slots but bypasses Today’s configured minute capacity. The shared batch processor already supports atomic time-budget preflight and estimate persistence, while frontend/search-batch-plan.js wires neither. Operators can therefore assign several issues before discovering that the plan cannot fit.

User flow

Select open issues in mobile Search → Assign & add to Today → when minute capacity is configured, review one estimate per selected issue → confirm only if the complete selection fits → persist estimates only after each issue is successfully queued.

Acceptance criteria

  • With configured minute capacity, selected Search issues require valid estimates before any preview, claim, or queue mutation.
  • An over-budget selection is rejected atomically and reports requested versus remaining time.
  • A fitting selection processes in selection order and persists estimates only for successfully queued issues.
  • Interrupted batches retain estimates, skip confirmed entries, and do not reclaim confirmed assignments.
  • Without configured minute capacity, the current batch flow remains unchanged.
  • Estimate-review controls are keyboard accessible, safe-area aware, and at least 44px on mobile.
  • Focused behavioral tests and the full suite pass.

Non-duplication evidence

Historical issue titles and recent commits were reviewed. #459 introduced Today capacity, #635 added inline estimates, #675 applied capacity to Find Work, and #809 added Search batching; none applies time-capacity preflight to Search batching. No current open issue or PR covers this behavior.

## Problem Mobile Search batch planning enforces Today item slots but bypasses Today’s configured minute capacity. The shared batch processor already supports atomic time-budget preflight and estimate persistence, while `frontend/search-batch-plan.js` wires neither. Operators can therefore assign several issues before discovering that the plan cannot fit. ## User flow Select open issues in mobile Search → Assign & add to Today → when minute capacity is configured, review one estimate per selected issue → confirm only if the complete selection fits → persist estimates only after each issue is successfully queued. ## Acceptance criteria - With configured minute capacity, selected Search issues require valid estimates before any preview, claim, or queue mutation. - An over-budget selection is rejected atomically and reports requested versus remaining time. - A fitting selection processes in selection order and persists estimates only for successfully queued issues. - Interrupted batches retain estimates, skip confirmed entries, and do not reclaim confirmed assignments. - Without configured minute capacity, the current batch flow remains unchanged. - Estimate-review controls are keyboard accessible, safe-area aware, and at least 44px on mobile. - Focused behavioral tests and the full suite pass. ## Non-duplication evidence Historical issue titles and recent commits were reviewed. #459 introduced Today capacity, #635 added inline estimates, #675 applied capacity to Find Work, and #809 added Search batching; none applies time-capacity preflight to Search batching. No current open issue or PR covers this behavior.
timmy self-assigned this 2026-08-14 08:19:57 +00:00
timmy closed this issue 2026-08-14 08:31:25 +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#811
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?