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

File mobile Drafts in one sequential session #629

New Issue
Closed
opened 2026-08-12 07:03:31 +00:00 by timmy · 0 comments
timmy commented 2026-08-12 07:03:31 +00:00
Owner
Copy Link

Product gap

Mobile operators can safely capture up to 20 unfiled Drafts and reach them through Queues, but filing several Drafts requires returning to the queue and reopening the composer after every item. The current flow resumes only one capture (frontend/dashboard.js) and has no safe continuation after durable outbox admission.

Vertical slice

Add a sequential mobile Draft filing session with stable capture ordering, progress, Previous/Skip navigation, and File & next. Advance only after the current Draft has been durably admitted and safely handed off. Never reuse a repository silently; preserve the current Draft and composer on any failure.

Acceptance

  • Opening a Needs filing card starts a session and announces position/remaining count.
  • Previous and Skip navigate stable capture IDs without deleting Drafts.
  • File & next validates and durably admits the current issue before removing its source Draft and opening the next surviving Draft.
  • Failure leaves the exact current Draft visible and retryable.
  • Final filing returns to an accurate Draft queue.
  • Controls are keyboard/screen-reader accessible, at least 44px, safe-area aware, and fit 320px mobile width.
  • Existing create, create-and-start, save-to-Drafts, attachment, account-safety, and outbox flows remain green.

Non-duplication evidence

Historical scan covered 317 issue titles plus recent commits through 1079ec6. Issues #613–#628 made capture, persistence, handoff, and queue access safe, but no historical title or implementation provides sequential/batch Draft filing, File & next, or a filing session.

## Product gap Mobile operators can safely capture up to 20 unfiled Drafts and reach them through Queues, but filing several Drafts requires returning to the queue and reopening the composer after every item. The current flow resumes only one capture (`frontend/dashboard.js`) and has no safe continuation after durable outbox admission. ## Vertical slice Add a sequential mobile Draft filing session with stable capture ordering, progress, Previous/Skip navigation, and **File & next**. Advance only after the current Draft has been durably admitted and safely handed off. Never reuse a repository silently; preserve the current Draft and composer on any failure. ## Acceptance - Opening a Needs filing card starts a session and announces position/remaining count. - Previous and Skip navigate stable capture IDs without deleting Drafts. - File & next validates and durably admits the current issue before removing its source Draft and opening the next surviving Draft. - Failure leaves the exact current Draft visible and retryable. - Final filing returns to an accurate Draft queue. - Controls are keyboard/screen-reader accessible, at least 44px, safe-area aware, and fit 320px mobile width. - Existing create, create-and-start, save-to-Drafts, attachment, account-safety, and outbox flows remain green. ## Non-duplication evidence Historical scan covered 317 issue titles plus recent commits through `1079ec6`. Issues #613–#628 made capture, persistence, handoff, and queue access safe, but no historical title or implementation provides sequential/batch Draft filing, File & next, or a filing session.
timmy self-assigned this 2026-08-12 07:03:31 +00:00
timmy closed this issue 2026-08-12 07:20:11 +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#629
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?