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

Plan an ordered Today queue in one mobile flow #385

New Issue
Closed
opened 2026-08-09 08:30:06 +00:00 by timmy · 0 comments
timmy commented 2026-08-09 08:30:06 +00:00
Owner
Copy Link

Product gap

Today planning is currently fragmented across per-card Add to Today controls, queue settings, separate reordering controls, and a separate Start work action. On a phone, building an ordered five-item plan requires repeated context switches and provides no persistent capacity overview.

Vertical slice

Add a focused mobile Plan Today flow where an operator can draft an ordered plan from active My Work, see capacity, cancel without mutation, save atomically, or save and immediately start the first item.

Acceptance criteria

  • Planner opens with the existing ordered Today plan and an explicit N of 5 selected status.
  • Active My Work candidates can be selected once, removed, and reordered; a sixth selection is visibly rejected.
  • Cancel performs no local or server mutation and restores focus.
  • Save commits the exact ordered plan through existing account-scoped Today synchronization.
  • Save & start enters the existing work-session flow at the first selected item.
  • At narrow mobile widths, controls are thumb-safe, keyboard/safe-area aware, and have no horizontal overflow.
  • Behavioral tests cover draft/cancel, capacity, ordering, persistence, and start handoff.

Non-duplication evidence

Historical issue/PR review through #384 found #279 (single-card Today queue and traversal), #299 (priority queue selection), and #357-#382 (cross-device planning synchronization), but no focused multi-item planner, draft/cancel semantics, capacity-guided selection, or combined Save & start flow. Recent main history through 19122c6 contains synchronization/runtime work only.

## Product gap Today planning is currently fragmented across per-card Add to Today controls, queue settings, separate reordering controls, and a separate Start work action. On a phone, building an ordered five-item plan requires repeated context switches and provides no persistent capacity overview. ## Vertical slice Add a focused mobile **Plan Today** flow where an operator can draft an ordered plan from active My Work, see capacity, cancel without mutation, save atomically, or save and immediately start the first item. ## Acceptance criteria - Planner opens with the existing ordered Today plan and an explicit `N of 5 selected` status. - Active My Work candidates can be selected once, removed, and reordered; a sixth selection is visibly rejected. - Cancel performs no local or server mutation and restores focus. - Save commits the exact ordered plan through existing account-scoped Today synchronization. - Save & start enters the existing work-session flow at the first selected item. - At narrow mobile widths, controls are thumb-safe, keyboard/safe-area aware, and have no horizontal overflow. - Behavioral tests cover draft/cancel, capacity, ordering, persistence, and start handoff. ## Non-duplication evidence Historical issue/PR review through #384 found #279 (single-card Today queue and traversal), #299 (priority queue selection), and #357-#382 (cross-device planning synchronization), but no focused multi-item planner, draft/cancel semantics, capacity-guided selection, or combined Save & start flow. Recent main history through 19122c6 contains synchronization/runtime work only.
timmy self-assigned this 2026-08-09 08:30:06 +00:00
timmy closed this issue 2026-08-09 08:39:14 +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#385
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?