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

Acknowledge unread updates with a reaction and open the next #539

New Issue
Closed
opened 2026-08-11 03:56:20 +00:00 by timmy · 0 comments
timmy commented 2026-08-11 03:56:20 +00:00
Owner
Copy Link

User outcome

From the unread-update reader on a phone, acknowledge the latest issue or pull-request comment with a +1 and advance to the next unread update in one tap, without composing a low-information reply.

Scope

  • Resolve the latest comment from the authenticated notification thread; never trust client-supplied repository or comment IDs.
  • Add the operator's +1 only when absent, then mark the notification read.
  • Retry safely when the reaction succeeded but mark-read failed.
  • Keep the current update open on failure; advance through the existing reader on confirmed success.
  • Disable the online-only action for cached/offline conversations and retain Queue read and next.
  • Provide an accessible, thumb-sized mobile control and status feedback.

Acceptance

  • Unsupported or malformed notification subjects perform no mutation.
  • First acknowledgement adds one +1 and marks the thread read.
  • Retry never duplicates the operator reaction and can complete mark-read.
  • Success removes only the current update and opens the next unread update.
  • Failures preserve the conversation and remain retryable; concurrent taps share one operation.
  • Offline UI is truthful and existing queued-read behavior remains available.
  • Focused behavior tests, rendered mobile checks, and full suite pass.

Evidence

The existing update sheet supports reply/read progression but no lightweight acknowledgement. Gitea exposes comment-reaction endpoints, while current notification detail already resolves trusted thread context. Historical issue and commit review found no reaction-based acknowledgement flow; related #135, #193, #351, #451, and #503 cover read/reply progression only.

## User outcome From the unread-update reader on a phone, acknowledge the latest issue or pull-request comment with a +1 and advance to the next unread update in one tap, without composing a low-information reply. ## Scope - Resolve the latest comment from the authenticated notification thread; never trust client-supplied repository or comment IDs. - Add the operator's +1 only when absent, then mark the notification read. - Retry safely when the reaction succeeded but mark-read failed. - Keep the current update open on failure; advance through the existing reader on confirmed success. - Disable the online-only action for cached/offline conversations and retain Queue read and next. - Provide an accessible, thumb-sized mobile control and status feedback. ## Acceptance - Unsupported or malformed notification subjects perform no mutation. - First acknowledgement adds one +1 and marks the thread read. - Retry never duplicates the operator reaction and can complete mark-read. - Success removes only the current update and opens the next unread update. - Failures preserve the conversation and remain retryable; concurrent taps share one operation. - Offline UI is truthful and existing queued-read behavior remains available. - Focused behavior tests, rendered mobile checks, and full suite pass. ## Evidence The existing update sheet supports reply/read progression but no lightweight acknowledgement. Gitea exposes comment-reaction endpoints, while current notification detail already resolves trusted thread context. Historical issue and commit review found no reaction-based acknowledgement flow; related #135, #193, #351, #451, and #503 cover read/reply progression only.
timmy self-assigned this 2026-08-11 03:56:20 +00:00
timmy closed this issue 2026-08-11 04:12:19 +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#539
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?