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

Turn Following into a changed-first mobile review inbox #1297

New Issue
Closed
opened 2026-08-23 07:24:52 +00:00 by timmy · 0 comments
timmy commented 2026-08-23 07:24:52 +00:00
Owner
Copy Link

Problem

Following stores the issue snapshot captured at watch time, so mobile operators cannot tell when watched work changes. The badge counts bookmarks rather than items needing review.

Slice

Refresh watched issues from Gitea when Following opens, preserve last-known data on partial failures, track account-scoped seen revisions, sort changed items first, and acknowledge a revision only after its preview loads successfully.

Acceptance

  • Changed title/state/update time refreshes and reports has_unseen_change=true; unchanged and closed items remain visible.
  • Partial refresh failure preserves last-known data and reports degraded status.
  • Conditional acknowledgement clears only the exact loaded revision; later activity becomes unseen again.
  • Mobile Following badge counts unseen changes, cards identify New activity without color alone, and opening a changed card clears it only after preview success.
  • Focused API/store/frontend tests, rendered 320px mobile test, and full suite pass.

Non-duplication

#1290 added Watch, #1293 added the static Following queue, and #1295 made admission recoverable. None refresh watched issue state, track seen revisions, or provide a changed-first review inbox.

## Problem Following stores the issue snapshot captured at watch time, so mobile operators cannot tell when watched work changes. The badge counts bookmarks rather than items needing review. ## Slice Refresh watched issues from Gitea when Following opens, preserve last-known data on partial failures, track account-scoped seen revisions, sort changed items first, and acknowledge a revision only after its preview loads successfully. ## Acceptance - Changed title/state/update time refreshes and reports `has_unseen_change=true`; unchanged and closed items remain visible. - Partial refresh failure preserves last-known data and reports degraded status. - Conditional acknowledgement clears only the exact loaded revision; later activity becomes unseen again. - Mobile Following badge counts unseen changes, cards identify New activity without color alone, and opening a changed card clears it only after preview success. - Focused API/store/frontend tests, rendered 320px mobile test, and full suite pass. ## Non-duplication #1290 added Watch, #1293 added the static Following queue, and #1295 made admission recoverable. None refresh watched issue state, track seen revisions, or provide a changed-first review inbox.
timmy self-assigned this 2026-08-23 07:24:52 +00:00
timmy closed this issue 2026-08-23 08:04:16 +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#1297
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?