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

Add checklist steps inline from mobile issue detail #915

New Issue
Closed
opened 2026-08-15 20:52:49 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-15 20:52:49 +00:00
Member
Copy Link

Product gap

Mobile issue detail can toggle, queue, reconcile, and finish existing checklist items, but adding a newly discovered step requires opening the full raw-Markdown editor. Issues without a checklist cannot become an executable plan inline.

Scope

  • Add a touch-safe inline Add step flow beside the rendered checklist.
  • Append one validated unchecked Markdown task while preserving title, prose, and task state.
  • Support durable offline admission and pending rendering through the existing issue-content outbox.
  • Reconcile locally added tasks against a newer remote body without reverting remote prose or task changes; ambiguous duplicates remain in Drafts attention.
  • Hide the control for closed/read-only outcomes and provide accessible status/focus behavior.

Acceptance

  1. Existing and checklist-free open assigned issues expose a 44px Add step control on phone layouts.
  2. Blank and normalized duplicate labels are rejected without mutation.
  3. Online add uses revision-checked issue content; offline add remains after reload and syncs exactly once.
  4. Conflict merge appends a unique local task to the latest remote body while preserving remote edits.
  5. Focused behavioral tests and full suite pass.

Audit evidence: current origin/main supports only checklist toggles (issue-sheet.js, checklist-conflict.js); no matching open/closed issue, PR, release, or recent commit was found.

## Product gap Mobile issue detail can toggle, queue, reconcile, and finish existing checklist items, but adding a newly discovered step requires opening the full raw-Markdown editor. Issues without a checklist cannot become an executable plan inline. ## Scope - Add a touch-safe inline **Add step** flow beside the rendered checklist. - Append one validated unchecked Markdown task while preserving title, prose, and task state. - Support durable offline admission and pending rendering through the existing issue-content outbox. - Reconcile locally added tasks against a newer remote body without reverting remote prose or task changes; ambiguous duplicates remain in Drafts attention. - Hide the control for closed/read-only outcomes and provide accessible status/focus behavior. ## Acceptance 1. Existing and checklist-free open assigned issues expose a 44px Add step control on phone layouts. 2. Blank and normalized duplicate labels are rejected without mutation. 3. Online add uses revision-checked issue content; offline add remains after reload and syncs exactly once. 4. Conflict merge appends a unique local task to the latest remote body while preserving remote edits. 5. Focused behavioral tests and full suite pass. Audit evidence: current `origin/main` supports only checklist toggles (`issue-sheet.js`, `checklist-conflict.js`); no matching open/closed issue, PR, release, or recent commit was found.
timmy was assigned by rockachopa 2026-08-15 20:52:49 +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#915
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?