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

Batch-plan Search results into Week Ahead #1196

New Issue
Closed
opened 2026-08-20 21:52:41 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-20 21:52:41 +00:00
Member
Copy Link

Product gap

Search supports selecting several issues and batch-planning them into Today, Later, or a release, while the newly shipped Week Ahead action only handles the single open preview. On a phone, planning several discovered issues requires reopening every result and repeating the full flow.

Vertical slice

Add Plan Week Ahead to the Search batch action bar. The review flow must let the operator assign each selected open issue to one of the next seven local dates with an estimate, show live daily load/capacity, reject invalid or duplicate placement before assignment, explicitly confirm overload, then claim eligible unassigned work and stage one canonical Week Ahead update. Preserve Search state on cancel/back and report partial claim/sync outcomes truthfully.

Acceptance

  • Selected eligible results can be dated and estimated in one mobile review flow, then appear exactly once in Week Ahead.
  • Missing estimates, invalid dates, day item-limit overflow, and duplicate placement block confirmation before claims.
  • Capacity overload shows exact planned/capacity minutes and requires explicit confirmation.
  • Cancel/back preserves query, filters, selection, and scroll and mutates nothing.
  • Partial claim or sync failure remains recoverable and never reports all items planned.
  • Controls remain keyboard accessible, at least 44px, and have no horizontal overflow at 320x568 and 390x844.
  • Behavioral unit/UI tests and a packaged mobile browser journey cover the flow.

Non-duplication evidence

All 599 historical issue titles and recent commits were checked. #1194/#1195 implements only single-preview Search → Week Ahead. Historical batch Search issues cover Today (#809), Later (#813), and releases (#815); none implement batch Week Ahead planning. There are no open PRs and no eligible unassigned/timmy issue for this slice.

## Product gap Search supports selecting several issues and batch-planning them into Today, Later, or a release, while the newly shipped Week Ahead action only handles the single open preview. On a phone, planning several discovered issues requires reopening every result and repeating the full flow. ## Vertical slice Add **Plan Week Ahead** to the Search batch action bar. The review flow must let the operator assign each selected open issue to one of the next seven local dates with an estimate, show live daily load/capacity, reject invalid or duplicate placement before assignment, explicitly confirm overload, then claim eligible unassigned work and stage one canonical Week Ahead update. Preserve Search state on cancel/back and report partial claim/sync outcomes truthfully. ## Acceptance - Selected eligible results can be dated and estimated in one mobile review flow, then appear exactly once in Week Ahead. - Missing estimates, invalid dates, day item-limit overflow, and duplicate placement block confirmation before claims. - Capacity overload shows exact planned/capacity minutes and requires explicit confirmation. - Cancel/back preserves query, filters, selection, and scroll and mutates nothing. - Partial claim or sync failure remains recoverable and never reports all items planned. - Controls remain keyboard accessible, at least 44px, and have no horizontal overflow at 320x568 and 390x844. - Behavioral unit/UI tests and a packaged mobile browser journey cover the flow. ## Non-duplication evidence All 599 historical issue titles and recent commits were checked. #1194/#1195 implements only single-preview Search → Week Ahead. Historical batch Search issues cover Today (#809), Later (#813), and releases (#815); none implement batch Week Ahead planning. There are no open PRs and no eligible unassigned/timmy issue for this slice.
timmy was assigned by rockachopa 2026-08-20 21:52:41 +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#1196
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?