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

Capture photo evidence in mobile conversation replies #941

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

User problem

Mobile field users can take a photo while filing a new issue, but issue comments, pull-request comments, and unread-update replies only expose a generic file picker. Follow-up evidence therefore requires leaving Stackchain to use the camera, then returning and choosing the image.

Scope

Add explicit Take photo and Choose existing actions to all three conversation composers. Route both sources through the existing validated attachment, preview, upload, offline outbox, retry, and idempotency behavior. Keep controls touch-safe and free of horizontal overflow at 320px.

Acceptance

  • Each issue-comment, pull-comment, and update-reply composer has a camera input with accept="image/*" capture="environment" and a separate PNG/JPEG/WebP picker.
  • Either source feeds the same attachment controller and preserves existing preview/remove/upload behavior.
  • Controls are at least 44px tall and do not overflow at 320px.
  • Focused behavioral tests and the full suite pass.

Historical issue and commit search found screenshot attachments (#467/#515/#527) and camera capture scoped to New issue (#937), but no conversation-composer camera flow.

## User problem Mobile field users can take a photo while filing a new issue, but issue comments, pull-request comments, and unread-update replies only expose a generic file picker. Follow-up evidence therefore requires leaving Stackchain to use the camera, then returning and choosing the image. ## Scope Add explicit **Take photo** and **Choose existing** actions to all three conversation composers. Route both sources through the existing validated attachment, preview, upload, offline outbox, retry, and idempotency behavior. Keep controls touch-safe and free of horizontal overflow at 320px. ## Acceptance - Each issue-comment, pull-comment, and update-reply composer has a camera input with `accept="image/*" capture="environment"` and a separate PNG/JPEG/WebP picker. - Either source feeds the same attachment controller and preserves existing preview/remove/upload behavior. - Controls are at least 44px tall and do not overflow at 320px. - Focused behavioral tests and the full suite pass. Historical issue and commit search found screenshot attachments (#467/#515/#527) and camera capture scoped to New issue (#937), but no conversation-composer camera flow.
timmy closed this issue 2026-08-16 05:37:40 +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
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#941
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?