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

Surface blockers while planning Today work #435

New Issue
Closed
opened 2026-08-09 23:50:03 +00:00 by timmy · 0 comments
timmy commented 2026-08-09 23:50:03 +00:00
Owner
Copy Link

User problem

On mobile, Plan Today can spend one of five slots on an issue that has unresolved Gitea dependencies without warning. Operators discover the blocker only after committing to the work and must leave the dashboard to investigate it.

Scope

  • Load and normalize issue dependencies in the existing Plan Today preview path.
  • Show unresolved blockers in the preview.
  • Require an explicit blocked-item override instead of the normal Add action.
  • Keep planning usable when dependency status is unavailable without claiming an issue is unblocked.
  • Render the flow without horizontal overflow at 320px and with touch-safe actions.

Acceptance tests

  1. Previewing an issue with open dependencies lists each blocker with repository, number, title, and state.
  2. The ordinary Add action is unavailable while blockers remain; an explicit Add blocked item anyway action adds it.
  3. Closed dependencies do not block the normal Add flow.
  4. Dependency lookup failure displays Blocker status unavailable and does not claim the issue is unblocked.
  5. Existing five-item capacity and duplicate protections remain intact.
  6. Focused backend/frontend tests and the full suite pass.

No historical issue title or recent commit covers dependency-aware Today planning.

## User problem On mobile, Plan Today can spend one of five slots on an issue that has unresolved Gitea dependencies without warning. Operators discover the blocker only after committing to the work and must leave the dashboard to investigate it. ## Scope - Load and normalize issue dependencies in the existing Plan Today preview path. - Show unresolved blockers in the preview. - Require an explicit blocked-item override instead of the normal Add action. - Keep planning usable when dependency status is unavailable without claiming an issue is unblocked. - Render the flow without horizontal overflow at 320px and with touch-safe actions. ## Acceptance tests 1. Previewing an issue with open dependencies lists each blocker with repository, number, title, and state. 2. The ordinary Add action is unavailable while blockers remain; an explicit Add blocked item anyway action adds it. 3. Closed dependencies do not block the normal Add flow. 4. Dependency lookup failure displays Blocker status unavailable and does not claim the issue is unblocked. 5. Existing five-item capacity and duplicate protections remain intact. 6. Focused backend/frontend tests and the full suite pass. No historical issue title or recent commit covers dependency-aware Today planning.
timmy self-assigned this 2026-08-09 23:50:03 +00:00
timmy closed this issue 2026-08-10 00:02:48 +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#435
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?