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

Mute future updates during mobile triage #751

New Issue
Closed
opened 2026-08-13 15:48:49 +00:00 by timmy · 0 comments
timmy commented 2026-08-13 15:48:49 +00:00
Owner
Copy Link

Problem

Mobile Updates triage can process the current notification but cannot unsubscribe from a noisy issue or pull request, so later comments recreate inbox and push-notification load. No open/closed issue or recent commit implements thread subscription management.

Scope

Add an online-only Mute future updates & next action for trusted issue/PR notification targets. Resolve repository/number server-side from the notification, unsubscribe only the authenticated operator, mark the current notification read, then advance the resumable triage pass. Preserve truthful partial-outcome recovery when unsubscribe succeeds but marking read fails.

Acceptance

  • Supported subscribed issue/PR updates expose a mobile-safe mute-and-next action.
  • Mutation uses the trusted notification target and current operator; malformed/foreign/mismatched targets fail before mutation.
  • Unsubscribe failure keeps the current item unread and does not advance.
  • If unsubscribe succeeds but mark-read fails, report that future updates are muted while the item remains unread, and retry read/advance without repeating unsubscribe.
  • Offline mode never claims success.
  • Behavioral API/frontend tests and the full suite pass.
## Problem Mobile Updates triage can process the current notification but cannot unsubscribe from a noisy issue or pull request, so later comments recreate inbox and push-notification load. No open/closed issue or recent commit implements thread subscription management. ## Scope Add an online-only **Mute future updates & next** action for trusted issue/PR notification targets. Resolve repository/number server-side from the notification, unsubscribe only the authenticated operator, mark the current notification read, then advance the resumable triage pass. Preserve truthful partial-outcome recovery when unsubscribe succeeds but marking read fails. ## Acceptance - Supported subscribed issue/PR updates expose a mobile-safe mute-and-next action. - Mutation uses the trusted notification target and current operator; malformed/foreign/mismatched targets fail before mutation. - Unsubscribe failure keeps the current item unread and does not advance. - If unsubscribe succeeds but mark-read fails, report that future updates are muted while the item remains unread, and retry read/advance without repeating unsubscribe. - Offline mode never claims success. - Behavioral API/frontend tests and the full suite pass.
timmy self-assigned this 2026-08-13 15:48:49 +00:00
timmy closed this issue 2026-08-13 15:57:38 +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#751
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?