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

Review and rebalance Week Ahead before confirmation #1188

New Issue
Closed
opened 2026-08-20 17:22:17 +00:00 by timmy · 0 comments
timmy commented 2026-08-20 17:22:17 +00:00
Owner
Copy Link

User problem

The seven-day mobile planning pass currently closes immediately after Day 7. Operators cannot review total load across the week or see that one work item was allocated to multiple dates, so the resulting plan can be overloaded and internally inconsistent.

Evidence

  • frontend/week-plan.js changes the final action to Save week, and frontend/dashboard.js closes after that save.
  • The date strip reports counts, not planned minutes against daily capacity.
  • Candidate filtering is per-date, while src/today_store.py validates unique dates but not unique work IDs across dates.
  • Historical issue and commit search found no weekly review/rebalance implementation; #1177/#1180/#1182/#1184/#1186 cover initial planning, offline durability, rollover, reconciliation, and continuous entry only.

Acceptance criteria

  • Saving Day 7 opens a mobile Review week step instead of closing the planner.
  • Review shows each day’s planned minutes, capacity, and overload state.
  • Work allocated on multiple days is clearly flagged and final confirmation is blocked until repaired.
  • A user can move a planned item to another date without copying it; estimate and all unrelated day plans remain intact.
  • Backend rejects duplicate cross-day work IDs without advancing the revision.
  • Existing offline staging and per-day conflict behavior remain intact.
  • Behavioral frontend/backend tests and the full suite pass.
## User problem The seven-day mobile planning pass currently closes immediately after Day 7. Operators cannot review total load across the week or see that one work item was allocated to multiple dates, so the resulting plan can be overloaded and internally inconsistent. ## Evidence - `frontend/week-plan.js` changes the final action to Save week, and `frontend/dashboard.js` closes after that save. - The date strip reports counts, not planned minutes against daily capacity. - Candidate filtering is per-date, while `src/today_store.py` validates unique dates but not unique work IDs across dates. - Historical issue and commit search found no weekly review/rebalance implementation; #1177/#1180/#1182/#1184/#1186 cover initial planning, offline durability, rollover, reconciliation, and continuous entry only. ## Acceptance criteria - Saving Day 7 opens a mobile Review week step instead of closing the planner. - Review shows each day’s planned minutes, capacity, and overload state. - Work allocated on multiple days is clearly flagged and final confirmation is blocked until repaired. - A user can move a planned item to another date without copying it; estimate and all unrelated day plans remain intact. - Backend rejects duplicate cross-day work IDs without advancing the revision. - Existing offline staging and per-day conflict behavior remain intact. - Behavioral frontend/backend tests and the full suite pass.
timmy self-assigned this 2026-08-20 17:22:17 +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#1188
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?