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

Prioritize actionable work in mobile Updates triage #773

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

Problem

The complete mobile Updates snapshot is currently triaged mostly newest-first because ordinary unread work collapses to the same priority. An older critical issue, requested review, or due assignment can therefore sit behind routine comments.

Scope

Rank unread Updates before a triage session by actionable work metadata: critical/P0 first, requested reviews second, overdue/due-today assignments third, other assignments fourth, then routine unread updates newest-first. Persist the resulting identity order through existing session checkpoints and show a concise reason beside triage progress.

Acceptance tests

  • Mixed snapshots open in the documented actionability order with deterministic newest-first/tie ordering inside each tier.
  • The ranked identity order survives reload/resume unchanged.
  • Progress exposes Critical, Review requested, Overdue, Due today, or Assigned to you where applicable.
  • Routine updates retain deterministic newest-first behavior.
  • Existing triage decisions, undo, prefetch, offline handling, and full suite remain green.
  • Mobile progress remains concise and accessible without changing the fixed decision bar.

Historical issue titles and recent commits were checked; related #755 prioritizes the Work launcher queue, while #753 and #749 make discovery complete/atomic. None orders items within Updates triage.

## Problem The complete mobile Updates snapshot is currently triaged mostly newest-first because ordinary unread work collapses to the same priority. An older critical issue, requested review, or due assignment can therefore sit behind routine comments. ## Scope Rank unread Updates before a triage session by actionable work metadata: critical/P0 first, requested reviews second, overdue/due-today assignments third, other assignments fourth, then routine unread updates newest-first. Persist the resulting identity order through existing session checkpoints and show a concise reason beside triage progress. ## Acceptance tests - Mixed snapshots open in the documented actionability order with deterministic newest-first/tie ordering inside each tier. - The ranked identity order survives reload/resume unchanged. - Progress exposes Critical, Review requested, Overdue, Due today, or Assigned to you where applicable. - Routine updates retain deterministic newest-first behavior. - Existing triage decisions, undo, prefetch, offline handling, and full suite remain green. - Mobile progress remains concise and accessible without changing the fixed decision bar. Historical issue titles and recent commits were checked; related #755 prioritizes the Work launcher queue, while #753 and #749 make discovery complete/atomic. None orders items within Updates triage.
timmy self-assigned this 2026-08-13 21:20:07 +00:00
timmy closed this issue 2026-08-13 21:26:59 +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#773
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?