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

Attach screenshots while capturing mobile issues #469

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

User problem

Mobile issue capture supports durable offline creation, duplicate review, planning metadata, and Create & start, but screenshots can only be attached after an issue is assigned. Reporting a visual defect therefore requires creating, waiting for sync, finding the issue again, then attaching evidence.

Scope

Add screenshot selection, preview/removal, durable outbox persistence, and staged post-create delivery to the New issue flow. Creation must remain exactly-once; retries after upload/comment failure resume against the confirmed issue rather than creating a duplicate.

Acceptance criteria

  • PNG, JPEG, and WebP up to 2 MB can be selected, previewed, removed, and replaced in New issue without horizontal overflow at 320px.
  • Duplicate review happens before issue creation or upload.
  • Online and offline Create & assign/Create & start preserve the image and eventually create one issue, upload one asset, and post one markdown comment.
  • A failure after issue creation retries only the unfinished attachment stages using the confirmed issue identity.
  • Editing/deleting a queued capture and private-data purge remove persisted image bytes.
  • Behavioral tests cover selection, persistence, staged retry, and mobile integration.

Non-duplication evidence

All 237 historical issue titles and recent origin/main commits were checked. #467/#468 added screenshots to comments on already-assigned issues; no issue or commit covers attachment during new-issue capture. Open issues #1-#5 and #11 are assigned to other humans and unrelated.

## User problem Mobile issue capture supports durable offline creation, duplicate review, planning metadata, and Create & start, but screenshots can only be attached after an issue is assigned. Reporting a visual defect therefore requires creating, waiting for sync, finding the issue again, then attaching evidence. ## Scope Add screenshot selection, preview/removal, durable outbox persistence, and staged post-create delivery to the New issue flow. Creation must remain exactly-once; retries after upload/comment failure resume against the confirmed issue rather than creating a duplicate. ## Acceptance criteria - PNG, JPEG, and WebP up to 2 MB can be selected, previewed, removed, and replaced in New issue without horizontal overflow at 320px. - Duplicate review happens before issue creation or upload. - Online and offline Create & assign/Create & start preserve the image and eventually create one issue, upload one asset, and post one markdown comment. - A failure after issue creation retries only the unfinished attachment stages using the confirmed issue identity. - Editing/deleting a queued capture and private-data purge remove persisted image bytes. - Behavioral tests cover selection, persistence, staged retry, and mobile integration. ## Non-duplication evidence All 237 historical issue titles and recent origin/main commits were checked. #467/#468 added screenshots to comments on already-assigned issues; no issue or commit covers attachment during new-issue capture. Open issues #1-#5 and #11 are assigned to other humans and unrelated.
timmy self-assigned this 2026-08-10 09:17:08 +00:00
timmy closed this issue 2026-08-10 09:36:50 +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#469
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?