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

Read complete unread-update conversations from mobile My Work #219

New Issue
Closed
opened 2026-08-07 18:34:25 +00:00 by timmy · 0 comments
timmy commented 2026-08-07 18:34:25 +00:00
Owner
Copy Link

User outcome

Mobile users can read the complete issue or pull-request conversation behind an unread update and reply in context without leaving My Work.

Evidence

The update sheet currently exposes only latest_comment (src/gitea_proxy.py::notification_detail, frontend/index.html), while full paginated conversation support exists only for assigned issue/PR sheets. Unmatched notification cards therefore cannot reconstruct prior discussion. This behavior is absent from all 113 historical issue titles and recent commits through 3824ff1; #151/#153 cover latest-comment context/reply and #209 covers assigned sheets only.

Acceptance

  • Notification detail includes the newest bounded comment page in chronological order with total/has-more metadata.
  • Loading older messages prepends one deduplicated page; repeated taps are single-flight and stale responses cannot leak into a newly opened update.
  • Failures preserve already loaded messages and reply drafts and remain retryable.
  • Supported subjects are limited to same-origin Issue/Pull API paths; errors are sanitized and responses are no-store.
  • Mobile reader controls remain touch-safe and do not create horizontal overflow.
  • Focused behavioral tests and full suite pass.
## User outcome Mobile users can read the complete issue or pull-request conversation behind an unread update and reply in context without leaving My Work. ## Evidence The update sheet currently exposes only `latest_comment` (`src/gitea_proxy.py::notification_detail`, `frontend/index.html`), while full paginated conversation support exists only for assigned issue/PR sheets. Unmatched notification cards therefore cannot reconstruct prior discussion. This behavior is absent from all 113 historical issue titles and recent commits through `3824ff1`; #151/#153 cover latest-comment context/reply and #209 covers assigned sheets only. ## Acceptance - Notification detail includes the newest bounded comment page in chronological order with total/has-more metadata. - Loading older messages prepends one deduplicated page; repeated taps are single-flight and stale responses cannot leak into a newly opened update. - Failures preserve already loaded messages and reply drafts and remain retryable. - Supported subjects are limited to same-origin Issue/Pull API paths; errors are sanitized and responses are no-store. - Mobile reader controls remain touch-safe and do not create horizontal overflow. - Focused behavioral tests and full suite pass.
timmy self-assigned this 2026-08-07 18:34:25 +00:00
timmy closed this issue 2026-08-07 18:49:44 +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#219
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?