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

Skip blocked items while running the Today queue #437

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

Problem

Today planning now surfaces dependency blockers, but execution still starts, resumes, and advances strictly by queue position. A dependency can remain deliberately overridden or become open after planning, causing the mobile Work flow to land on a known dead end.

Slice

Before Start, Resume, Continue, and Next, classify issue dependencies. Keep blocked items in their original plan order, route to the earliest known-ready item, and present an accessible readiness gate for blocked or unavailable status with explicit Work anyway / Retry / Review plan choices. Pull requests and non-issue items remain runnable.

Acceptance

  • A blocked first issue does not prevent opening the earliest known-ready Today item.
  • Blocked items remain in their saved order and are never silently removed or moved.
  • Newly blocked checkpoints gate Resume/Continue/Next without falsely completing the session.
  • Unknown dependency status is never labelled ready and supports Retry plus explicit override.
  • Work anyway opens the selected item once and preserves its checkpoint.
  • At 320px, blocker details wrap, actions are touch-safe, browser Back closes the gate, and focus is restored.
  • Behavioral tests cover ready/blocked/unknown/all-blocked selection and the full suite remains green.

Non-duplicate evidence

#435 only warns during Plan Today. Historical issue/title and recent-commit searches show no dependency readiness check in Today execution; #409 and #421-#430 cover execution entry/advance without blocker routing.

## Problem Today planning now surfaces dependency blockers, but execution still starts, resumes, and advances strictly by queue position. A dependency can remain deliberately overridden or become open after planning, causing the mobile Work flow to land on a known dead end. ## Slice Before Start, Resume, Continue, and Next, classify issue dependencies. Keep blocked items in their original plan order, route to the earliest known-ready item, and present an accessible readiness gate for blocked or unavailable status with explicit Work anyway / Retry / Review plan choices. Pull requests and non-issue items remain runnable. ## Acceptance - A blocked first issue does not prevent opening the earliest known-ready Today item. - Blocked items remain in their saved order and are never silently removed or moved. - Newly blocked checkpoints gate Resume/Continue/Next without falsely completing the session. - Unknown dependency status is never labelled ready and supports Retry plus explicit override. - Work anyway opens the selected item once and preserves its checkpoint. - At 320px, blocker details wrap, actions are touch-safe, browser Back closes the gate, and focus is restored. - Behavioral tests cover ready/blocked/unknown/all-blocked selection and the full suite remains green. ## Non-duplicate evidence #435 only warns during Plan Today. Historical issue/title and recent-commit searches show no dependency readiness check in Today execution; #409 and #421-#430 cover execution entry/advance without blocker routing.
timmy self-assigned this 2026-08-10 00:28:59 +00:00
timmy closed this issue 2026-08-10 00:40:45 +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#437
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?