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

Explain each mobile evidence screenshot before filing #827

New Issue
Closed
opened 2026-08-14 13:23:35 +00:00 by timmy · 0 comments
timmy commented 2026-08-14 13:23:35 +00:00
Owner
Copy Link

Problem

Mobile issue capture can review and reorder up to five evidence screenshots, but each image is identified only by filename and position. Reviewers must infer what each screenshot proves, especially after offline delivery or retries.

User flow

Add an optional bounded note to each screenshot in the existing evidence review. The note remains paired with its screenshot through reorder, removal, Draft restore, offline outbox delivery, and retry, then renders immediately before that image in the ordered Gitea evidence comment. Empty notes preserve today's Markdown.

Acceptance criteria

  • Selecting an evidence thumbnail exposes its own accessible note field.
  • Notes remain attached through reorder/removal and Draft/outbox serialization.
  • Foreground and background delivery generate identical ordered, Markdown-safe captions.
  • Legacy records without note metadata restore and deliver unchanged.
  • Mobile controls remain keyboard-safe and usable at 320px width.
  • Behavioral tests cover pairing, persistence, safe Markdown, and delivery; full suite is green.

Evidence / non-duplication

Current origin/main at 807364c supports bundle capture (#823) and review/reorder (#825), but frontend/issue-evidence-review.js only exposes filename/position and frontend/issue-attachment.js emits bare image Markdown. All 417 historical issue titles and recent commits were searched; none cover per-image evidence notes or captions.

## Problem Mobile issue capture can review and reorder up to five evidence screenshots, but each image is identified only by filename and position. Reviewers must infer what each screenshot proves, especially after offline delivery or retries. ## User flow Add an optional bounded note to each screenshot in the existing evidence review. The note remains paired with its screenshot through reorder, removal, Draft restore, offline outbox delivery, and retry, then renders immediately before that image in the ordered Gitea evidence comment. Empty notes preserve today's Markdown. ## Acceptance criteria - Selecting an evidence thumbnail exposes its own accessible note field. - Notes remain attached through reorder/removal and Draft/outbox serialization. - Foreground and background delivery generate identical ordered, Markdown-safe captions. - Legacy records without note metadata restore and deliver unchanged. - Mobile controls remain keyboard-safe and usable at 320px width. - Behavioral tests cover pairing, persistence, safe Markdown, and delivery; full suite is green. ## Evidence / non-duplication Current `origin/main` at `807364c` supports bundle capture (#823) and review/reorder (#825), but `frontend/issue-evidence-review.js` only exposes filename/position and `frontend/issue-attachment.js` emits bare image Markdown. All 417 historical issue titles and recent commits were searched; none cover per-image evidence notes or captions.
timmy self-assigned this 2026-08-14 13:23:35 +00:00
timmy closed this issue 2026-08-14 13:44:15 +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#827
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?