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

Schedule unfinished Today work during session wrap-up #990

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

User problem

Ending a timed Today session saves a recap but explicitly leaves the plan unchanged. Unfinished work remains in Today and must be cleaned up reactively the next morning.

Evidence

  • frontend/today-recap.js ends the checkpoint with “Your plan is unchanged.”
  • Existing Today removal and Later scheduling already support moving work without mutating the underlying Gitea issue.
  • No open or closed issue title describes end-of-day wrap-up or scheduling unfinished Today work; #579/#583 cover recap capture/variance and #603 covers next-day stale-plan recovery.

Slice

After recap save, offer a mobile wrap-up step for unfinished Today items. Let the operator schedule each item for tomorrow morning or deliberately leave it in Today. Persist through the existing Today/Later stores and show a truthful outcome.

Acceptance

  • Saving an end-session recap opens wrap-up with unfinished Today items in plan order.
  • Scheduling for tomorrow removes the item from Today and adds one Later entry for 09:00 local time without mutating/closing the Gitea issue.
  • Leaving an item preserves its Today membership, estimate, and order.
  • Repeat confirmation does not duplicate Later entries.
  • The flow is usable at 390x844 with 44px controls and no horizontal overflow.
  • Focused behavioral tests, full suite, and packaged mobile journey pass.
## User problem Ending a timed Today session saves a recap but explicitly leaves the plan unchanged. Unfinished work remains in Today and must be cleaned up reactively the next morning. ## Evidence - `frontend/today-recap.js` ends the checkpoint with “Your plan is unchanged.” - Existing Today removal and Later scheduling already support moving work without mutating the underlying Gitea issue. - No open or closed issue title describes end-of-day wrap-up or scheduling unfinished Today work; #579/#583 cover recap capture/variance and #603 covers next-day stale-plan recovery. ## Slice After recap save, offer a mobile wrap-up step for unfinished Today items. Let the operator schedule each item for tomorrow morning or deliberately leave it in Today. Persist through the existing Today/Later stores and show a truthful outcome. ## Acceptance - Saving an end-session recap opens wrap-up with unfinished Today items in plan order. - Scheduling for tomorrow removes the item from Today and adds one Later entry for 09:00 local time without mutating/closing the Gitea issue. - Leaving an item preserves its Today membership, estimate, and order. - Repeat confirmation does not duplicate Later entries. - The flow is usable at 390x844 with 44px controls and no horizontal overflow. - Focused behavioral tests, full suite, and packaged mobile journey pass.
timmy was assigned by rockachopa 2026-08-16 21:51:57 +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#990
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?