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

Persist exact Week Ahead task times for calendar handoff #1270

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

Evidence

Week Ahead persists day, order, estimates, capacity, and privacy-safe free windows, but frontend/week-calendar.js derives task times transiently from one daily start cursor. Reopening the saved plan or using another signed-in phone loses those exact choices, so users must repeat calendar timing or edit exported events. Historical issues #1198, #1210, #1258, #1260, and #1266 cover generated exports, busy-time avoidance, persisted free windows, saved-plan export, and capacity reflow—not persisted per-task times. No open/closed title or recent commit implements this behavior.

Slice

Add bounded per-task start times to each encrypted, revisioned Week Ahead day. In calendar handoff, show an accessible time input for every selected task, validate whole-task placement against overlaps/free windows/day bounds, save exact times through the existing offline/revisioned plan flow, and export those saved times on reload/device handoff. Day/order/estimate changes must retain only still-valid placements.

Acceptance

  • Exact per-task times survive save, reload, and account-scoped encrypted persistence.
  • Calendar handoff initializes from saved times and exports those exact blocks.
  • Overlap, out-of-day, and out-of-retained-free-window times are rejected without a write.
  • Moving/removing work drops stale timing metadata; unrelated valid times remain.
  • 320px mobile controls remain touch-safe with no horizontal overflow.
  • Behavioral tests prove RED then GREEN; full suite and packaged mobile journey pass.
## Evidence Week Ahead persists day, order, estimates, capacity, and privacy-safe free windows, but `frontend/week-calendar.js` derives task times transiently from one daily start cursor. Reopening the saved plan or using another signed-in phone loses those exact choices, so users must repeat calendar timing or edit exported events. Historical issues #1198, #1210, #1258, #1260, and #1266 cover generated exports, busy-time avoidance, persisted free windows, saved-plan export, and capacity reflow—not persisted per-task times. No open/closed title or recent commit implements this behavior. ## Slice Add bounded per-task start times to each encrypted, revisioned Week Ahead day. In calendar handoff, show an accessible time input for every selected task, validate whole-task placement against overlaps/free windows/day bounds, save exact times through the existing offline/revisioned plan flow, and export those saved times on reload/device handoff. Day/order/estimate changes must retain only still-valid placements. ## Acceptance - Exact per-task times survive save, reload, and account-scoped encrypted persistence. - Calendar handoff initializes from saved times and exports those exact blocks. - Overlap, out-of-day, and out-of-retained-free-window times are rejected without a write. - Moving/removing work drops stale timing metadata; unrelated valid times remain. - 320px mobile controls remain touch-safe with no horizontal overflow. - Behavioral tests prove RED then GREEN; full suite and packaged mobile journey pass.
timmy was assigned by rockachopa 2026-08-22 16:26:31 +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#1270
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?