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

Resume fully planned issue drafts across devices #859

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

Problem

Account-synchronized mobile Drafts preserve title, body, blockers, and evidence, but discard filing decisions already made in the create flow. frontend/unfiled-captures.js exports only those reduced fields and resume() resets repository and labels; src/unfiled_draft_store.py and src/main.py enforce that reduced schema. A user who continues on another phone must reselect repository, issue type, owner intent, labels, milestone, due date, and Today estimate.

No eligible open issue is assigned to Timmy or unassigned. Historical-title and recent-commit review found adjacent work (#845 templates, #847 metadata loading, #849 estimate requirement, #851/#853/#857 Draft synchronization/conflicts), but no issue that synchronizes the filing plan itself.

User flow

  1. Prepare a Draft with repository, template, owner intent, labels, milestone, due date, blockers, and Today estimate.
  2. Save/sync it and continue on another signed-in device.
  3. Resume with the same filing controls restored and proceed to review/Create & start without re-planning.

Acceptance

  • Full filing metadata round-trips through local Draft storage, account sync, and resume.
  • The API validates bounded repository/template/owner/label/milestone/due-date/estimate/intent values and rejects invalid values.
  • Existing minimal Drafts remain compatible.
  • Cross-device import/reconciliation preserves the complete plan and evidence.
  • Behavioral tests prove RED first; focused and full suites pass.
## Problem Account-synchronized mobile Drafts preserve title, body, blockers, and evidence, but discard filing decisions already made in the create flow. `frontend/unfiled-captures.js` exports only those reduced fields and `resume()` resets repository and labels; `src/unfiled_draft_store.py` and `src/main.py` enforce that reduced schema. A user who continues on another phone must reselect repository, issue type, owner intent, labels, milestone, due date, and Today estimate. No eligible open issue is assigned to Timmy or unassigned. Historical-title and recent-commit review found adjacent work (#845 templates, #847 metadata loading, #849 estimate requirement, #851/#853/#857 Draft synchronization/conflicts), but no issue that synchronizes the filing plan itself. ## User flow 1. Prepare a Draft with repository, template, owner intent, labels, milestone, due date, blockers, and Today estimate. 2. Save/sync it and continue on another signed-in device. 3. Resume with the same filing controls restored and proceed to review/Create & start without re-planning. ## Acceptance - Full filing metadata round-trips through local Draft storage, account sync, and resume. - The API validates bounded repository/template/owner/label/milestone/due-date/estimate/intent values and rejects invalid values. - Existing minimal Drafts remain compatible. - Cross-device import/reconciliation preserves the complete plan and evidence. - Behavioral tests prove RED first; focused and full suites pass.
timmy self-assigned this 2026-08-14 23:49:09 +00:00
timmy closed this issue 2026-08-15 00:10:23 +00:00
timmy reopened this issue 2026-08-15 00:24:55 +00:00
timmy closed this issue 2026-08-15 00:30:21 +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#859
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?