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

Add unread Gitea updates to the mobile My Work inbox #133

New Issue
Closed
opened 2026-08-06 19:49:50 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-06 19:49:50 +00:00
Member
Copy Link

User problem

Assigned work and review requests are visible on mobile, but unread mentions, comments, and status updates on unassigned work are invisible. Users must hunt through Gitea to discover conversations that need attention.

Vertical slice

Fetch authenticated unread Gitea notification threads in the pooled live snapshot, isolate notification failures from context/activity, and add an Updates filter to My Work. Correlate a notification with an existing issue/PR card instead of duplicating it; unmatched notifications remain actionable cards linking to the latest comment (or subject fallback).

Acceptance criteria

  • The proxy requests unread notifications with a bounded 50-item limit and returns normalized safe fields.
  • Notification failures degrade only the notifications section of /api/v1/live.
  • Matching notifications enrich existing work cards; unmatched threads appear once as Updates.
  • Mobile Updates filter exposes a count, session persistence, 44px touch targets, and safe Gitea deep links.
  • Fresh empty updates and stale notification state are explicit.
  • Focused behavioral tests and the complete suite pass.

Evidence: current source has no notification API use or Updates responsibility; historical issue titles and recent commits contain no equivalent behavior.

## User problem Assigned work and review requests are visible on mobile, but unread mentions, comments, and status updates on unassigned work are invisible. Users must hunt through Gitea to discover conversations that need attention. ## Vertical slice Fetch authenticated unread Gitea notification threads in the pooled live snapshot, isolate notification failures from context/activity, and add an Updates filter to My Work. Correlate a notification with an existing issue/PR card instead of duplicating it; unmatched notifications remain actionable cards linking to the latest comment (or subject fallback). ## Acceptance criteria - The proxy requests unread notifications with a bounded 50-item limit and returns normalized safe fields. - Notification failures degrade only the notifications section of `/api/v1/live`. - Matching notifications enrich existing work cards; unmatched threads appear once as Updates. - Mobile Updates filter exposes a count, session persistence, 44px touch targets, and safe Gitea deep links. - Fresh empty updates and stale notification state are explicit. - Focused behavioral tests and the complete suite pass. Evidence: current source has no notification API use or Updates responsibility; historical issue titles and recent commits contain no equivalent behavior.
timmy was assigned by rockachopa 2026-08-06 19:49:50 +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#133
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?