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

Report a Today blocker, defer it, and continue #1066

New Issue
Closed
opened 2026-08-18 06:23:52 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-18 06:23:52 +00:00
Member
Copy Link

User problem

On mobile, an operator who discovers a blocker during an active Today item can post a progress update, but must then reopen the item, defer it separately, and manually continue. This interrupts the focused session and risks either losing the blocker context or leaving blocked work active.

Vertical slice

Add a Post blocker & move on action to the active Today progress sheet. Require a blocker update and future return time. Durably admit the exact issue/PR comment first, then add the item to Later, remove it from Today, and continue through the existing readiness-aware next-item transition. Preserve an admitted-but-not-transitioned checkpoint so retry cannot duplicate the comment.

Acceptance criteria

  • Action is available only for the checkpointed active Today issue or PR.
  • Blocker text and a valid future return time are required.
  • Comment admission happens before planning mutation; admission failure leaves Today/Later unchanged and retains the draft.
  • After admission, retry of a failed planning transition does not admit a second comment.
  • Successful transition adds the item to Later, removes it from Today, and opens the next ready item (or existing recap for the final item).
  • Existing voice, mention, photo, activity, offline admission, and ordinary Post now behavior remain intact.
  • Controls are mobile-safe at 320px/390px and the full test suite and packaged mobile journey pass.

Non-duplication evidence

No open issue is eligible for timmy/unassigned work. Historical review of 535 issues found adjacent but distinct work: #1052 posts progress without advancing; #455 defers active work without reporting a blocker; #429 comments and advances without retaining the blocked item in Later. Recent commits through #1065 add evidence/activity/voice/mentions but do not combine durable reporting with defer-and-continue.

## User problem On mobile, an operator who discovers a blocker during an active Today item can post a progress update, but must then reopen the item, defer it separately, and manually continue. This interrupts the focused session and risks either losing the blocker context or leaving blocked work active. ## Vertical slice Add a **Post blocker & move on** action to the active Today progress sheet. Require a blocker update and future return time. Durably admit the exact issue/PR comment first, then add the item to Later, remove it from Today, and continue through the existing readiness-aware next-item transition. Preserve an admitted-but-not-transitioned checkpoint so retry cannot duplicate the comment. ## Acceptance criteria - Action is available only for the checkpointed active Today issue or PR. - Blocker text and a valid future return time are required. - Comment admission happens before planning mutation; admission failure leaves Today/Later unchanged and retains the draft. - After admission, retry of a failed planning transition does not admit a second comment. - Successful transition adds the item to Later, removes it from Today, and opens the next ready item (or existing recap for the final item). - Existing voice, mention, photo, activity, offline admission, and ordinary **Post now** behavior remain intact. - Controls are mobile-safe at 320px/390px and the full test suite and packaged mobile journey pass. ## Non-duplication evidence No open issue is eligible for timmy/unassigned work. Historical review of 535 issues found adjacent but distinct work: #1052 posts progress without advancing; #455 defers active work without reporting a blocker; #429 comments and advances without retaining the blocked item in Later. Recent commits through #1065 add evidence/activity/voice/mentions but do not combine durable reporting with defer-and-continue.
timmy was assigned by rockachopa 2026-08-18 06:23:52 +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#1066
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?