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

Capture mobile evidence bundles with one issue #823

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

User problem

Mobile bug reports often need a short sequence of screenshots, but Capture work keeps only one image. Operators must file an issue, reopen it, and append evidence manually, breaking the one-pass offline capture flow.

Evidence

  • frontend/issue-attachment.js consumes only files[0] and stores one selected attachment.
  • frontend/unfiled-captures.js, frontend/issue-outbox.js, and frontend/background-issue-sync.js persist and deliver a singular attachment.
  • The service-worker test currently rejects multiple shared images.
  • All historical issue titles/bodies were checked for evidence bundles and multi-image capture; no matching behavior exists.

Acceptance criteria

  • Capture work accepts up to five ordered PNG/JPEG/WebP screenshots and allows removing any one without losing typed issue content.
  • Draft/offline persistence restores the complete ordered bundle.
  • Delivery creates one issue, uploads every image with resumable per-image checkpoints, and posts one Markdown evidence comment without duplicate uploads or issues.
  • Share Target accepts up to five images and preserves them through sign-in continuation.
  • A sixth image is rejected accessibly without discarding the first five.
  • Behavioral tests cover selection limits/order, persistence, retry checkpoints, and share ingestion.
## User problem Mobile bug reports often need a short sequence of screenshots, but Capture work keeps only one image. Operators must file an issue, reopen it, and append evidence manually, breaking the one-pass offline capture flow. ## Evidence - `frontend/issue-attachment.js` consumes only `files[0]` and stores one selected attachment. - `frontend/unfiled-captures.js`, `frontend/issue-outbox.js`, and `frontend/background-issue-sync.js` persist and deliver a singular attachment. - The service-worker test currently rejects multiple shared images. - All historical issue titles/bodies were checked for evidence bundles and multi-image capture; no matching behavior exists. ## Acceptance criteria - Capture work accepts up to five ordered PNG/JPEG/WebP screenshots and allows removing any one without losing typed issue content. - Draft/offline persistence restores the complete ordered bundle. - Delivery creates one issue, uploads every image with resumable per-image checkpoints, and posts one Markdown evidence comment without duplicate uploads or issues. - Share Target accepts up to five images and preserves them through sign-in continuation. - A sixth image is rejected accessibly without discarding the first five. - Behavioral tests cover selection limits/order, persistence, retry checkpoints, and share ingestion.
timmy self-assigned this 2026-08-14 11:21:33 +00:00
timmy closed this issue 2026-08-14 11:45:29 +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#823
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?