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

Complete the mobile Filed follow-up loop #874

New Issue
Closed
opened 2026-08-15 06:22:23 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 06:22:23 +00:00
Owner
Copy Link

Problem

The mobile Work queues sheet omits the existing Filed queue, so operators cannot return to issues they delegated without hunting through desktop filters. mobile-task-dock.js also excludes Filed from counts and accessible summaries, while the generic queue launcher opens issue detail even when a filed item has an unread update. Existing #870/#872 implemented authored discovery and read-only detail, but not this mobile follow-up journey.

Vertical slice

  • Add Filed and its open count to the mobile queue sheet and dock announcement.
  • Launch the highest-priority filed item. Open its existing update reader when unread activity exists; otherwise open existing author-authorized read-only detail.
  • Preserve the Filed route/focus when returning.

Acceptance

  • Filed is a touch-sized mobile queue row with an accurate count and accessible queue summary.
  • An unread filed item opens the full update conversation; a quiet filed item opens read-only detail.
  • Empty Filed announces a specific empty state.
  • Focus/route return to Filed; mutation controls remain absent for delegated issues.
  • Focused tests, full suite, release browser gate, and Gitea Actions pass.

Non-duplication

All 440 issue titles and recent commits were reviewed. #870 added Filed filtering/discovery and #872 added read-only detail. Neither adds Filed to the mobile queue sheet/dock nor prioritizes unread filed follow-up. No open issue covers this behavior.

## Problem The mobile Work queues sheet omits the existing Filed queue, so operators cannot return to issues they delegated without hunting through desktop filters. `mobile-task-dock.js` also excludes Filed from counts and accessible summaries, while the generic queue launcher opens issue detail even when a filed item has an unread update. Existing #870/#872 implemented authored discovery and read-only detail, but not this mobile follow-up journey. ## Vertical slice - Add Filed and its open count to the mobile queue sheet and dock announcement. - Launch the highest-priority filed item. Open its existing update reader when unread activity exists; otherwise open existing author-authorized read-only detail. - Preserve the Filed route/focus when returning. ## Acceptance - Filed is a touch-sized mobile queue row with an accurate count and accessible queue summary. - An unread filed item opens the full update conversation; a quiet filed item opens read-only detail. - Empty Filed announces a specific empty state. - Focus/route return to Filed; mutation controls remain absent for delegated issues. - Focused tests, full suite, release browser gate, and Gitea Actions pass. ## Non-duplication All 440 issue titles and recent commits were reviewed. #870 added Filed filtering/discovery and #872 added read-only detail. Neither adds Filed to the mobile queue sheet/dock nor prioritizes unread filed follow-up. No open issue covers this behavior.
timmy self-assigned this 2026-08-15 06:22:23 +00:00
timmy closed this issue 2026-08-15 06:32:57 +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#874
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?