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

Plan Search results directly into Week Ahead #1194

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

User problem

On mobile, Search can find an open issue but cannot place it on a specific Week Ahead day. Operators must leave Search, rediscover the issue in My Work, and rebuild context.

Vertical slice

Add a touch-safe Plan ahead flow to an eligible Search preview. The operator chooses one of the next seven local dates, enters an estimate, sees destination load/capacity, and assigns when necessary before durably staging and syncing the canonical issue into Week Ahead. Search state remains intact.

Acceptance

  • Eligible open issue previews expose Plan ahead; closed items and pull requests do not.
  • Exactly seven upcoming local dates show existing load/capacity.
  • Estimate is required; existing placement offers an explicit move, never a duplicate.
  • Destination item limit and overload require explicit handling.
  • Assignment is single-flight and skipped for already-owned issues.
  • Assignment success followed by planning failure reports “Assigned, not planned”.
  • Local staging preserves all other days and supports existing pending-sync recovery.
  • Cancel/Back makes no mutation and restores focus/search state.
  • 320px mobile layout has touch-sized controls and no horizontal overflow.

This is distinct from Search→Today/Later work (#797-#814) and Week Ahead creation/review work (#1177-#1193): no historical issue or recent commit connects a single Search preview directly to a chosen Week Ahead date.

## User problem On mobile, Search can find an open issue but cannot place it on a specific Week Ahead day. Operators must leave Search, rediscover the issue in My Work, and rebuild context. ## Vertical slice Add a touch-safe **Plan ahead** flow to an eligible Search preview. The operator chooses one of the next seven local dates, enters an estimate, sees destination load/capacity, and assigns when necessary before durably staging and syncing the canonical issue into Week Ahead. Search state remains intact. ## Acceptance - Eligible open issue previews expose Plan ahead; closed items and pull requests do not. - Exactly seven upcoming local dates show existing load/capacity. - Estimate is required; existing placement offers an explicit move, never a duplicate. - Destination item limit and overload require explicit handling. - Assignment is single-flight and skipped for already-owned issues. - Assignment success followed by planning failure reports “Assigned, not planned”. - Local staging preserves all other days and supports existing pending-sync recovery. - Cancel/Back makes no mutation and restores focus/search state. - 320px mobile layout has touch-sized controls and no horizontal overflow. This is distinct from Search→Today/Later work (#797-#814) and Week Ahead creation/review work (#1177-#1193): no historical issue or recent commit connects a single Search preview directly to a chosen Week Ahead date.
rockachopa self-assigned this 2026-08-20 20:21:26 +00:00
rockachopa removed their assignment 2026-08-20 20:22:02 +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
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#1194
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?