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

Turn Today recap feedback into an adjusted plan #583

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

User problem

Today recap records estimate-versus-actual data, but the mobile flow stops after saving and exposes internal work identities. Operators cannot turn timing feedback into a better remaining plan without manually reopening Plan Today and remembering actuals.

Vertical slice

  • Render recap rows with recognizable work titles/repository context and bounded identity fallback.
  • Show per-item estimate, actual, and signed variance.
  • Save the recap, then hand the same remaining Today queue into Plan Today.
  • Offer explicit per-item “use actual as estimate” recommendations; never mutate estimates until Plan Today is saved.
  • Preserve ordinary/offline planner behavior if recap history or save is unavailable.

Acceptance tests

  • A timed item renders a recognizable label and per-item variance rather than a raw identity as its primary label.
  • “Save recap & adjust plan” persists the stable recap session and opens Plan Today with the current ordered queue.
  • Applying a recommendation changes only the planner draft; Save plan/Save & start uses the existing Today persistence path.
  • Failed recap saves retain the retryable draft and do not silently alter the plan.
  • Mobile 390x844 and 320x568 layouts retain 44px controls, wrapping labels, no horizontal overflow, and safe-area-aware actions.
  • Focused tests and the full suite pass.

Non-duplication

Historical issues #577, #579, #581 added timing, recap history, and offline draft retention; #459 added capacity-aware planning. No open/closed issue or recent commit connects recap feedback into replanning or provides readable per-item recap context. Existing open issues are assigned to other humans and are unrelated.

## User problem Today recap records estimate-versus-actual data, but the mobile flow stops after saving and exposes internal work identities. Operators cannot turn timing feedback into a better remaining plan without manually reopening Plan Today and remembering actuals. ## Vertical slice - Render recap rows with recognizable work titles/repository context and bounded identity fallback. - Show per-item estimate, actual, and signed variance. - Save the recap, then hand the same remaining Today queue into Plan Today. - Offer explicit per-item “use actual as estimate” recommendations; never mutate estimates until Plan Today is saved. - Preserve ordinary/offline planner behavior if recap history or save is unavailable. ## Acceptance tests - A timed item renders a recognizable label and per-item variance rather than a raw identity as its primary label. - “Save recap & adjust plan” persists the stable recap session and opens Plan Today with the current ordered queue. - Applying a recommendation changes only the planner draft; Save plan/Save & start uses the existing Today persistence path. - Failed recap saves retain the retryable draft and do not silently alter the plan. - Mobile 390x844 and 320x568 layouts retain 44px controls, wrapping labels, no horizontal overflow, and safe-area-aware actions. - Focused tests and the full suite pass. ## Non-duplication Historical issues #577, #579, #581 added timing, recap history, and offline draft retention; #459 added capacity-aware planning. No open/closed issue or recent commit connects recap feedback into replanning or provides readable per-item recap context. Existing open issues are assigned to other humans and are unrelated.
timmy was assigned by rockachopa 2026-08-11 18:20:53 +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#583
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?