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

Open Week Ahead planned work and return to the overview #1222

New Issue
Closed
opened 2026-08-21 13:09:07 +00:00 by timmy · 0 comments
timmy commented 2026-08-21 13:09:07 +00:00
Owner
Copy Link

User problem

Week Ahead now shows a read-first seven-day mobile plan, but planned issue and pull rows are static copy. Operators must close the overview and find the work again before they can inspect it.

Vertical slice

Make known planned issue/pull rows semantic 44px controls that open the existing addressable work detail. Browser Back/close must reveal the still-open Week Ahead overview and restore focus to the originating planned row. Missing metadata and unavailable offline details stay truthful and non-actionable. Opening details must not mutate the plan.

Acceptance tests

  • Known issue and pull rows render as full-width buttons with canonical work identity and minimum 44px target.
  • Activating a row delegates to the existing work-route/detail flow without a Week Ahead write.
  • Closing detail returns to the same Week Ahead overview and focuses the originating row.
  • Unknown work remains non-actionable and labels details unavailable.
  • Offline work without a saved detail reports reconnect guidance and leaves the overview intact.
  • Rendered 320px/390px journeys have no horizontal overflow or page errors.
  • Focused tests and the full suite pass.

Evidence / non-duplication

frontend/week-plan.js currently renders planned work as <div class="week-review-item-copy"> and binds only Move/Edit. frontend/dashboard.js already owns canonical openRoutedWork. A read-only scan of 612 issue titles, 606 PR titles, releases, and recent commits found Week Ahead overview/offline/calendar work but no planned-row-to-detail flow.

## User problem Week Ahead now shows a read-first seven-day mobile plan, but planned issue and pull rows are static copy. Operators must close the overview and find the work again before they can inspect it. ## Vertical slice Make known planned issue/pull rows semantic 44px controls that open the existing addressable work detail. Browser Back/close must reveal the still-open Week Ahead overview and restore focus to the originating planned row. Missing metadata and unavailable offline details stay truthful and non-actionable. Opening details must not mutate the plan. ## Acceptance tests - Known issue and pull rows render as full-width buttons with canonical work identity and minimum 44px target. - Activating a row delegates to the existing work-route/detail flow without a Week Ahead write. - Closing detail returns to the same Week Ahead overview and focuses the originating row. - Unknown work remains non-actionable and labels details unavailable. - Offline work without a saved detail reports reconnect guidance and leaves the overview intact. - Rendered 320px/390px journeys have no horizontal overflow or page errors. - Focused tests and the full suite pass. ## Evidence / non-duplication `frontend/week-plan.js` currently renders planned work as `<div class="week-review-item-copy">` and binds only Move/Edit. `frontend/dashboard.js` already owns canonical `openRoutedWork`. A read-only scan of 612 issue titles, 606 PR titles, releases, and recent commits found Week Ahead overview/offline/calendar work but no planned-row-to-detail flow.
timmy self-assigned this 2026-08-21 13:09:07 +00:00
timmy closed this issue 2026-08-21 13:50:38 +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#1222
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?