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

Complete the mobile Save to Drafts handoff #621

New Issue
Closed
opened 2026-08-12 04:50:54 +00:00 by timmy · 0 comments
timmy commented 2026-08-12 04:50:54 +00:00
Owner
Copy Link

Problem

Mobile capture persists an unfiled issue, closes the capture sheet, and leaves the operator in the previous My Work queue with only transient status copy. The saved card and its existing Choose repository continuation remain hidden behind a separate Drafts dock action. This weakens confidence that text and screenshots were saved.

Vertical slice

After Save to Drafts succeeds, open the Drafts queue, mark Drafts as the current mobile destination, render and focus the exact saved capture card, and announce the next step. Preserve existing persistence, attachment, quarantine, and failure behavior.

Acceptance criteria

  • A successful save closes the sheet and immediately renders Drafts.
  • The Drafts dock action has aria-current=page.
  • The exact saved card is programmatically focusable and receives focus after the overlay closes.
  • The status announces Saved to Drafts. Choose a repository when you’re ready to file it.
  • The card exposes existing Needs filing, Choose repository, and screenshot state.
  • Persistence failure leaves the composer content open and does not navigate.
  • Mobile actions remain at least 44px and the card is not obscured by the dock.

Non-duplication evidence

Related completed work created capture-first New (#613), preserved screenshots (#615), purged private screenshot drafts (#617), cold-offline capture (#301), draft recovery (#211), and the task dock (#236). None completes the post-save handoff to the newly persisted card. Current open issues #1-#5 and #11 cover other owners and unrelated dashboard work.

## Problem Mobile capture persists an unfiled issue, closes the capture sheet, and leaves the operator in the previous My Work queue with only transient status copy. The saved card and its existing Choose repository continuation remain hidden behind a separate Drafts dock action. This weakens confidence that text and screenshots were saved. ## Vertical slice After Save to Drafts succeeds, open the Drafts queue, mark Drafts as the current mobile destination, render and focus the exact saved capture card, and announce the next step. Preserve existing persistence, attachment, quarantine, and failure behavior. ## Acceptance criteria - A successful save closes the sheet and immediately renders Drafts. - The Drafts dock action has `aria-current=page`. - The exact saved card is programmatically focusable and receives focus after the overlay closes. - The status announces `Saved to Drafts. Choose a repository when you’re ready to file it.` - The card exposes existing Needs filing, Choose repository, and screenshot state. - Persistence failure leaves the composer content open and does not navigate. - Mobile actions remain at least 44px and the card is not obscured by the dock. ## Non-duplication evidence Related completed work created capture-first New (#613), preserved screenshots (#615), purged private screenshot drafts (#617), cold-offline capture (#301), draft recovery (#211), and the task dock (#236). None completes the post-save handoff to the newly persisted card. Current open issues #1-#5 and #11 cover other owners and unrelated dashboard work.
timmy self-assigned this 2026-08-12 04:50:54 +00:00
timmy closed this issue 2026-08-12 04:57:57 +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#621
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?