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

Attach screenshots to unread update replies online and offline #527

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

User problem

On mobile, unread-update conversations support fast replies and “Reply, mark read & next”, but operators cannot attach screenshot evidence without leaving the focused flow and reopening the underlying issue or pull request.

Scope

Add screenshot selection, removable preview, screenshot-only replies, and durable online/offline delivery to unread-update replies. Re-resolve notification targets server-side, preserve drafts on failure, and ensure read-and-next advances only after upload and reply confirmation.

Acceptance criteria

  • PNG/JPEG/WebP screenshots can be previewed, removed, optimized to the existing 2 MB boundary, and sent with optional text.
  • Notification-scoped upload resolves only the authenticated notification’s issue/pull target.
  • Online retries do not duplicate upload or reply.
  • Offline admission stores bytes in the account-bound IndexedDB authored lane and background retry checkpoints upload markdown.
  • “Reply, mark read & next” marks read and advances only after confirmed upload and reply; failures preserve the unread item and draft.
  • The flow remains usable at 320 px and 390 px widths with keyboard-safe controls and 44 px touch targets.
  • Behavioral tests cover server authorization, outbox/background delivery, composer integration, and mobile layout.
## User problem On mobile, unread-update conversations support fast replies and “Reply, mark read & next”, but operators cannot attach screenshot evidence without leaving the focused flow and reopening the underlying issue or pull request. ## Scope Add screenshot selection, removable preview, screenshot-only replies, and durable online/offline delivery to unread-update replies. Re-resolve notification targets server-side, preserve drafts on failure, and ensure read-and-next advances only after upload and reply confirmation. ## Acceptance criteria - PNG/JPEG/WebP screenshots can be previewed, removed, optimized to the existing 2 MB boundary, and sent with optional text. - Notification-scoped upload resolves only the authenticated notification’s issue/pull target. - Online retries do not duplicate upload or reply. - Offline admission stores bytes in the account-bound IndexedDB authored lane and background retry checkpoints upload markdown. - “Reply, mark read & next” marks read and advances only after confirmed upload and reply; failures preserve the unread item and draft. - The flow remains usable at 320 px and 390 px widths with keyboard-safe controls and 44 px touch targets. - Behavioral tests cover server authorization, outbox/background delivery, composer integration, and mobile layout.
timmy self-assigned this 2026-08-11 00:51:22 +00:00
timmy closed this issue 2026-08-11 01:10:55 +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#527
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?