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

Open Today blockers in the in-app work preview #443

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

Problem

Today readiness surfaces prerequisite blockers, but each blocker is only an external Gitea link. On a phone this ejects the user from the focused Today flow even though Stackchain already has an in-app issue preview and assign/start workflow.

Vertical slice

Make readiness blockers open the existing in-app issue preview. Preserve the readiness gate underneath and offer the existing owned/unassigned start actions, with Today-capacity protection and safe Gitea fallback.

Acceptance criteria

  • Tapping a readiness blocker opens an in-app preview instead of a new browser tab.
  • The preview shows the correct repository/number and supports owned Start in Today and unassigned Assign & start behavior.
  • Closing/back returns focus to the originating blocker and leaves the blocked planned item/order unchanged.
  • A full Today queue blocks assignment before mutation.
  • Failed/offline preview keeps a safe Gitea fallback.
  • At 320px blocker controls remain at least 44px tall and do not create horizontal overflow.
  • Behavioral tests cover the integrated flow and the full suite remains green.

Non-duplication evidence

Open issues #1-#5 and #11 are assigned to other humans and cover unrelated legacy widgets/design. Historical #435/#436 only surfaced blockers, #437/#438 skipped blocked execution items, and #441/#442 bounded readiness latency. Search preview #197/#198 did not connect Today blockers to that flow. No open PR exists.

## Problem Today readiness surfaces prerequisite blockers, but each blocker is only an external Gitea link. On a phone this ejects the user from the focused Today flow even though Stackchain already has an in-app issue preview and assign/start workflow. ## Vertical slice Make readiness blockers open the existing in-app issue preview. Preserve the readiness gate underneath and offer the existing owned/unassigned start actions, with Today-capacity protection and safe Gitea fallback. ## Acceptance criteria - Tapping a readiness blocker opens an in-app preview instead of a new browser tab. - The preview shows the correct repository/number and supports owned `Start in Today` and unassigned `Assign & start` behavior. - Closing/back returns focus to the originating blocker and leaves the blocked planned item/order unchanged. - A full Today queue blocks assignment before mutation. - Failed/offline preview keeps a safe Gitea fallback. - At 320px blocker controls remain at least 44px tall and do not create horizontal overflow. - Behavioral tests cover the integrated flow and the full suite remains green. ## Non-duplication evidence Open issues #1-#5 and #11 are assigned to other humans and cover unrelated legacy widgets/design. Historical #435/#436 only surfaced blockers, #437/#438 skipped blocked execution items, and #441/#442 bounded readiness latency. Search preview #197/#198 did not connect Today blockers to that flow. No open PR exists.
timmy closed this issue 2026-08-10 02:07:07 +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
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#443
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?