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

Load complete mobile conversations without leaving My Work #209

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

Problem

Mobile assigned issue and pull-request sheets fetch only the first 20 comments and label them “Recent discussion.” Long-running work can omit the newest context, forcing users out to Gitea before replying, closing, reviewing, or merging. Existing pagination covers work queues, not conversations.

Vertical slice

Load the newest bounded conversation page for assigned issue and pull sheets, provide an independently retryable Load older messages action, preserve chronological order and deduplicate by comment ID, and reconcile a successful authored comment exactly once.

Acceptance criteria

  • A 47-comment issue or pull initially renders the newest bounded page in chronological order.
  • “Load older messages” prepends the preceding page without duplicate comments and disappears only when history is exhausted.
  • A failed older-page load preserves current conversation and draft and offers retry.
  • Posted comments append exactly once using the confirmed upstream response.
  • Comment page and limit are bounded server-side; assigned-work authorization remains enforced; responses are no-store.
  • Mobile sheets remain usable at 320px without horizontal page overflow.
  • Behavioral frontend/API tests and the full suite pass.

No historical issue/PR title or recent commit implements comment-history pagination; #147/#169 paginate queues and #157 only added a single bounded recent-comments page.

## Problem Mobile assigned issue and pull-request sheets fetch only the first 20 comments and label them “Recent discussion.” Long-running work can omit the newest context, forcing users out to Gitea before replying, closing, reviewing, or merging. Existing pagination covers work queues, not conversations. ## Vertical slice Load the newest bounded conversation page for assigned issue and pull sheets, provide an independently retryable **Load older messages** action, preserve chronological order and deduplicate by comment ID, and reconcile a successful authored comment exactly once. ## Acceptance criteria - A 47-comment issue or pull initially renders the newest bounded page in chronological order. - “Load older messages” prepends the preceding page without duplicate comments and disappears only when history is exhausted. - A failed older-page load preserves current conversation and draft and offers retry. - Posted comments append exactly once using the confirmed upstream response. - Comment page and limit are bounded server-side; assigned-work authorization remains enforced; responses are `no-store`. - Mobile sheets remain usable at 320px without horizontal page overflow. - Behavioral frontend/API tests and the full suite pass. No historical issue/PR title or recent commit implements comment-history pagination; #147/#169 paginate queues and #157 only added a single bounded recent-comments page.
timmy self-assigned this 2026-08-07 16:09:34 +00:00
timmy closed this issue 2026-08-07 16:23:33 +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#209
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?