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

Finish a mobile checklist and continue Today #911

New Issue
Closed
opened 2026-08-15 19:22:08 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 19:22:08 +00:00
Owner
Copy Link

Evidence

Mobile checklist updates stop at “Checklist updated” even when the final task is complete. The checklist renders near the top of the issue sheet (frontend/index.html), while the existing close action is below conversation, editing, planning, and handoff controls. Existing close-and-continue behavior already safely handles online and durable offline closure, but it is not reachable at checklist completion without a long mobile scroll.

Historical issue/PR titles and recent commits were checked: #905 toggles checklist items, #907 queues them offline, #909 coalesces offline changes, and #391 implements generic close-and-continue. None connects final-checklist completion to that flow.

User flow

After the final checklist item is confirmed (or durably queued offline), show a thumb-reachable completion action beside the checklist. In Today it offers Close & next (offline: Queue close & next); outside Today it offers Close issue. Keep open dismisses the prompt. Never close automatically.

Acceptance tests

  • A partially complete checklist does not show the action; completing the last item does.
  • Today, non-Today, and offline labels are correct and reuse the existing confirmed closure path.
  • Unchecking a task, opening an issue with no tasks, closed/read-only Filed details, and failed/stale updates hide the action.
  • The action requires existing close confirmation, then advances Today exactly once; offline content admission precedes closure admission.
  • At 390×844 the action is safe-area-aware, at least 44px, and has no horizontal overflow.
## Evidence Mobile checklist updates stop at “Checklist updated” even when the final task is complete. The checklist renders near the top of the issue sheet (`frontend/index.html`), while the existing close action is below conversation, editing, planning, and handoff controls. Existing close-and-continue behavior already safely handles online and durable offline closure, but it is not reachable at checklist completion without a long mobile scroll. Historical issue/PR titles and recent commits were checked: #905 toggles checklist items, #907 queues them offline, #909 coalesces offline changes, and #391 implements generic close-and-continue. None connects final-checklist completion to that flow. ## User flow After the final checklist item is confirmed (or durably queued offline), show a thumb-reachable completion action beside the checklist. In Today it offers **Close & next** (offline: **Queue close & next**); outside Today it offers **Close issue**. Keep open dismisses the prompt. Never close automatically. ## Acceptance tests - A partially complete checklist does not show the action; completing the last item does. - Today, non-Today, and offline labels are correct and reuse the existing confirmed closure path. - Unchecking a task, opening an issue with no tasks, closed/read-only Filed details, and failed/stale updates hide the action. - The action requires existing close confirmation, then advances Today exactly once; offline content admission precedes closure admission. - At 390×844 the action is safe-area-aware, at least 44px, and has no horizontal overflow.
timmy self-assigned this 2026-08-15 19:22:08 +00:00
timmy closed this issue 2026-08-15 19:32:08 +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#911
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?