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

Preserve screenshots in capture-first mobile Drafts #615

New Issue
Closed
opened 2026-08-12 03:21:14 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-12 03:21:14 +00:00
Member
Copy Link

Problem

The capture-first New flow introduced in #613 keeps repository metadata out of the way, but the screenshot control is still hidden behind File now and unfiled Drafts persist only title and note. A phone user who captures evidence before knowing the repository can therefore save the thought but lose its screenshot. Existing screenshot delivery (#469, #473, #491) only covers repository-aware queued issues.

Vertical slice

  • Expose the existing screenshot picker in the capture-first stage.
  • Durably persist an optimized screenshot with an account-bound unfiled capture.
  • Restore the screenshot when Choose repository resumes the capture.
  • Delete the source Draft only after title, note, and screenshot have safely transferred to issue capture; preserve it on storage/restore failure.
  • Remove screenshot data on discard and bounded-list pruning.

Acceptance

  • PNG/JPEG/WebP selection and preview work before repository selection at mobile widths.
  • Saving waits for durable screenshot storage and reports failures without closing or clearing the composer.
  • Drafts indicate screenshot presence; matching-account resume restores the screenshot and exact metadata.
  • Account mismatch cannot load private screenshot data.
  • Resume, cancel, reload, and failed transfer do not lose the Draft; successful handoff/discard/pruning cleans its screenshot.
  • Focused behavioral tests and full suite pass.
## Problem The capture-first New flow introduced in #613 keeps repository metadata out of the way, but the screenshot control is still hidden behind **File now** and unfiled Drafts persist only title and note. A phone user who captures evidence before knowing the repository can therefore save the thought but lose its screenshot. Existing screenshot delivery (#469, #473, #491) only covers repository-aware queued issues. ## Vertical slice - Expose the existing screenshot picker in the capture-first stage. - Durably persist an optimized screenshot with an account-bound unfiled capture. - Restore the screenshot when **Choose repository** resumes the capture. - Delete the source Draft only after title, note, and screenshot have safely transferred to issue capture; preserve it on storage/restore failure. - Remove screenshot data on discard and bounded-list pruning. ## Acceptance - PNG/JPEG/WebP selection and preview work before repository selection at mobile widths. - Saving waits for durable screenshot storage and reports failures without closing or clearing the composer. - Drafts indicate screenshot presence; matching-account resume restores the screenshot and exact metadata. - Account mismatch cannot load private screenshot data. - Resume, cancel, reload, and failed transfer do not lose the Draft; successful handoff/discard/pruning cleans its screenshot. - Focused behavioral tests and full suite pass.
timmy was assigned by rockachopa 2026-08-12 03:21:14 +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#615
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?