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

Continue Today after handing off or releasing active work #449

New Issue
Closed
opened 2026-08-10 03:30:26 +00:00 by timmy · 0 comments
timmy commented 2026-08-10 03:30:26 +00:00
Owner
Copy Link

User problem

On mobile, handing off or releasing the active Today issue removes it from My Work but bypasses the Today transition used by close, merge, and comment actions. The dashboard can silently open the next item without the dependency/readiness gate, or leave the focused session inconsistent.

Slice

Make ownership exits complete the active Today checkpoint and continue through the existing demand-driven readiness transition. Keep non-active issue behavior unchanged and make active action labels explicit.

Acceptance criteria

  • Handing off the active Today issue performs one ownership mutation, removes it from Today, and continues once through readiness-aware next-item selection.
  • Releasing the active Today issue has the same transition semantics.
  • A blocked or unknown-readiness next item uses the existing readiness gate rather than opening blindly.
  • Mutation failure or cancellation preserves Today order and checkpoint.
  • A non-active handoff/release does not advance the active Today session.
  • Active actions communicate their continuation behavior and remain usable at a 320px mobile viewport.
  • Focused and full automated suites pass.

Non-duplication evidence

Issues #183 and #281 added release and handoff, while #437 added readiness-aware Today advancement. Current origin/main handlers still call paintMyWork directly and do not call runTodayTransition, leaving this end-to-end flow unimplemented. No open issue or recent commit covers ownership-exit continuation.

## User problem On mobile, handing off or releasing the active Today issue removes it from My Work but bypasses the Today transition used by close, merge, and comment actions. The dashboard can silently open the next item without the dependency/readiness gate, or leave the focused session inconsistent. ## Slice Make ownership exits complete the active Today checkpoint and continue through the existing demand-driven readiness transition. Keep non-active issue behavior unchanged and make active action labels explicit. ## Acceptance criteria - Handing off the active Today issue performs one ownership mutation, removes it from Today, and continues once through readiness-aware next-item selection. - Releasing the active Today issue has the same transition semantics. - A blocked or unknown-readiness next item uses the existing readiness gate rather than opening blindly. - Mutation failure or cancellation preserves Today order and checkpoint. - A non-active handoff/release does not advance the active Today session. - Active actions communicate their continuation behavior and remain usable at a 320px mobile viewport. - Focused and full automated suites pass. ## Non-duplication evidence Issues #183 and #281 added release and handoff, while #437 added readiness-aware Today advancement. Current origin/main handlers still call paintMyWork directly and do not call runTodayTransition, leaving this end-to-end flow unimplemented. No open issue or recent commit covers ownership-exit continuation.
timmy self-assigned this 2026-08-10 03:30:27 +00:00
timmy closed this issue 2026-08-10 03:43:54 +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#449
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?