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

Send multi-photo evidence bundles in mobile conversation replies #943

New Issue
Closed
opened 2026-08-16 05:52:10 +00:00 by timmy · 0 comments
timmy commented 2026-08-16 05:52:10 +00:00
Owner
Copy Link

User problem

Mobile issue, pull-request, and unread-update conversations accept camera evidence, but retain only one photo. Field users documenting before/after state or multi-step failures must post several comments and repeat offline delivery.

Scope

Enable up to five ordered photos in all three mobile conversation composers and deliver text plus the complete bundle as one idempotent comment/reply, online or from the durable outbox. Preserve compatibility with existing single-photo queued records.

Acceptance criteria

  • Repeated camera captures append; gallery input accepts multiple files; a sixth is rejected without losing the first five.
  • Issue comments, PR comments, update replies, and reply/read-next serialize the ordered bundle.
  • Offline admission stores every Blob in IndexedDB while localStorage contains metadata only.
  • Reconnect resumes per-photo upload checkpoints and posts exactly one ordered comment without duplicate upload/reply/read-next actions.
  • At 320px and 390px widths, controls remain touch-safe and the bundle preview does not create horizontal page overflow.
  • Strict RED/GREEN tests cover bundle selection, durable storage, retries, singular-record compatibility, and UI wiring; full suite and Actions pass.
## User problem Mobile issue, pull-request, and unread-update conversations accept camera evidence, but retain only one photo. Field users documenting before/after state or multi-step failures must post several comments and repeat offline delivery. ## Scope Enable up to five ordered photos in all three mobile conversation composers and deliver text plus the complete bundle as one idempotent comment/reply, online or from the durable outbox. Preserve compatibility with existing single-photo queued records. ## Acceptance criteria - Repeated camera captures append; gallery input accepts multiple files; a sixth is rejected without losing the first five. - Issue comments, PR comments, update replies, and reply/read-next serialize the ordered bundle. - Offline admission stores every Blob in IndexedDB while localStorage contains metadata only. - Reconnect resumes per-photo upload checkpoints and posts exactly one ordered comment without duplicate upload/reply/read-next actions. - At 320px and 390px widths, controls remain touch-safe and the bundle preview does not create horizontal page overflow. - Strict RED/GREEN tests cover bundle selection, durable storage, retries, singular-record compatibility, and UI wiring; full suite and Actions pass.
timmy self-assigned this 2026-08-16 05:52:10 +00:00
timmy closed this issue 2026-08-16 06:13: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#943
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?