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

Retire completed work from Week Ahead #1235

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

Product gap

Completed issues remain in Week Ahead after a successful close, so mobile operators continue to see stale load and can export obsolete calendar blocks. The current close flow updates My Work and Today but not the durable Week plan.

Vertical slice

After an online issue close succeeds, retire that issue identity and estimate from every Week Ahead day, preserve all sibling order/capacity and unrelated days, stage one durable revision-aware Week update, refresh an open Week overview, and report saved vs sync-pending truthfully. Failed issue closure must not change Week Ahead.

Acceptance tests

  • Controller retirement removes the identity and estimate from all days, preserves siblings/capacity/unrelated days, and stages exactly one write.
  • Unknown identities and read-only offline snapshots produce no mutation.
  • Successful close invokes retirement; failed close does not. A failed Week delivery leaves the revised plan pending for lifecycle retry.
  • Packaged mobile behavior at 320x568 and 390x844 closes planned work, returns to a refreshed overview, recalculates load, keeps controls >=44px, and has no horizontal overflow.
  • Focused tests and the full suite pass.

No open/closed issue title or recent commit implements completed-work retirement from Week Ahead; adjacent work only opens planned details and reconciles Today.

## Product gap Completed issues remain in Week Ahead after a successful close, so mobile operators continue to see stale load and can export obsolete calendar blocks. The current close flow updates My Work and Today but not the durable Week plan. ## Vertical slice After an online issue close succeeds, retire that issue identity and estimate from every Week Ahead day, preserve all sibling order/capacity and unrelated days, stage one durable revision-aware Week update, refresh an open Week overview, and report saved vs sync-pending truthfully. Failed issue closure must not change Week Ahead. ## Acceptance tests - Controller retirement removes the identity and estimate from all days, preserves siblings/capacity/unrelated days, and stages exactly one write. - Unknown identities and read-only offline snapshots produce no mutation. - Successful close invokes retirement; failed close does not. A failed Week delivery leaves the revised plan pending for lifecycle retry. - Packaged mobile behavior at 320x568 and 390x844 closes planned work, returns to a refreshed overview, recalculates load, keeps controls >=44px, and has no horizontal overflow. - Focused tests and the full suite pass. No open/closed issue title or recent commit implements completed-work retirement from Week Ahead; adjacent work only opens planned details and reconciles Today.
timmy was assigned by rockachopa 2026-08-21 19:50: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#1235
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?