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

Expose unread Updates in the mobile queue switcher #639

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

Problem

The thumb-reachable mobile Queues sheet exposes Today, Attention, Later, and Drafts, but not the existing dedicated Updates queue. Mobile operators must open the buried queue settings to intentionally triage unread conversations even though reply, acknowledge, mark-read, and next-item actions already exist. Attention is not equivalent because it combines unread updates with requested reviews.

Vertical slice

Add Updates to the mobile queue sheet with its live unread count and route selection through the existing Updates filter. Preserve the stable five-action dock and existing conversation triage behavior. Keep the aggregate Queues badge non-overlapping by treating Updates as a drill-down already represented within Attention, rather than adding it twice.

Acceptance

  • Queues sheet always renders Today, Attention, Updates, Later, and Drafts.
  • Updates has accessible unread-conversation copy and a live count.
  • Selecting Updates closes the sheet, activates the existing Updates filter, and focuses My Work.
  • Aggregate Queues badge does not double-count Updates already represented in Attention.
  • Focus restoration, 44px mobile targets, offline shell distribution, focused tests, and full suite remain green.

Audit proof: complete issue/PR title history through #638 and recent commits through c016261 contain no prior Updates destination in the mobile switcher. Related #627 intentionally shipped only four destinations; update-action issues #539, #545, and #549 are complementary.

## Problem The thumb-reachable mobile Queues sheet exposes Today, Attention, Later, and Drafts, but not the existing dedicated Updates queue. Mobile operators must open the buried queue settings to intentionally triage unread conversations even though reply, acknowledge, mark-read, and next-item actions already exist. Attention is not equivalent because it combines unread updates with requested reviews. ## Vertical slice Add Updates to the mobile queue sheet with its live unread count and route selection through the existing Updates filter. Preserve the stable five-action dock and existing conversation triage behavior. Keep the aggregate Queues badge non-overlapping by treating Updates as a drill-down already represented within Attention, rather than adding it twice. ## Acceptance - Queues sheet always renders Today, Attention, Updates, Later, and Drafts. - Updates has accessible unread-conversation copy and a live count. - Selecting Updates closes the sheet, activates the existing Updates filter, and focuses My Work. - Aggregate Queues badge does not double-count Updates already represented in Attention. - Focus restoration, 44px mobile targets, offline shell distribution, focused tests, and full suite remain green. Audit proof: complete issue/PR title history through #638 and recent commits through c016261 contain no prior Updates destination in the mobile switcher. Related #627 intentionally shipped only four destinations; update-action issues #539, #545, and #549 are complementary.
timmy closed this issue 2026-08-12 09:54: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
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#639
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?