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

Make mobile New a capture-first flow #613

New Issue
Closed
opened 2026-08-12 02:50:05 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-12 02:50:05 +00:00
Member
Copy Link

Problem

The mobile dock’s New action opens the full repository-first issue form. On a phone, an operator must cross repository search and planning metadata before reaching the title, even though the dashboard already supports durable account-bound unfiled captures. This makes capturing work during an interruption unnecessarily slow.

Evidence on origin/main:

  • frontend/index.html places repository selection before title and shows all issue metadata immediately.
  • frontend/dashboard.js focuses repository search when no repository is selected.
  • Save for filing already persists title/body without a network mutation, and Drafts already resumes that capture safely.

Slice

Turn New into a capture-first flow: focus title and show title/note plus Save to Drafts and File now. Reveal repository, attachment, planning metadata, duplicate review, and create/start actions only after File now. Existing saved/resumed or repository-bearing drafts should enter filing mode directly.

Acceptance

  • New opens with title focused and filing metadata collapsed.
  • Save to Drafts performs no request and preserves the existing account-bound unfiled-capture behavior.
  • File now reveals the complete existing issue filing flow without losing title/note.
  • Repository-bearing resumed drafts open directly in filing mode.
  • Back/Cancel preserves the recoverable draft and restores focus to New.
  • At 320px and 390px widths, actions remain at least 44px and content has no horizontal overflow.
  • Focused tests and the full suite pass.
## Problem The mobile dock’s **New** action opens the full repository-first issue form. On a phone, an operator must cross repository search and planning metadata before reaching the title, even though the dashboard already supports durable account-bound unfiled captures. This makes capturing work during an interruption unnecessarily slow. Evidence on `origin/main`: - `frontend/index.html` places repository selection before title and shows all issue metadata immediately. - `frontend/dashboard.js` focuses repository search when no repository is selected. - `Save for filing` already persists title/body without a network mutation, and Drafts already resumes that capture safely. ## Slice Turn New into a capture-first flow: focus title and show title/note plus **Save to Drafts** and **File now**. Reveal repository, attachment, planning metadata, duplicate review, and create/start actions only after File now. Existing saved/resumed or repository-bearing drafts should enter filing mode directly. ## Acceptance - New opens with title focused and filing metadata collapsed. - Save to Drafts performs no request and preserves the existing account-bound unfiled-capture behavior. - File now reveals the complete existing issue filing flow without losing title/note. - Repository-bearing resumed drafts open directly in filing mode. - Back/Cancel preserves the recoverable draft and restores focus to New. - At 320px and 390px widths, actions remain at least 44px and content has no horizontal overflow. - Focused tests and the full suite pass.
timmy was assigned by rockachopa 2026-08-12 02:50:05 +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#613
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?