Toggle issue checklist items from mobile detail #905

Closed
opened 2026-08-15 16:31:43 +00:00 by timmy · 0 comments
Owner

Problem

Markdown task lists are visible in mobile issue detail, but every checkbox is disabled. Operators must open the full raw-Markdown editor, locate a marker, and save the whole description to record one completed step.

User outcome

On writable, online assigned issues, an operator can toggle a checklist item directly in mobile detail. The update targets the exact source marker, uses the existing revision-checked content mutation, refreshes local state on success, and fails safely on conflicts or network errors. Offline and read-only details remain non-interactive.

Acceptance criteria

  • Enabled checklist controls are accessible and at least 44×44 CSS pixels on writable online issue details.
  • Activating one control changes only its exact Markdown task marker and submits the loaded expected_updated_at.
  • Fenced code, duplicate labels, nested lists, CRLF input, and [X] markers map to the correct source task.
  • While pending, checklist controls cannot overlap mutations.
  • Success refreshes rendered detail and cached issue revision/body and announces completion.
  • Conflict/network failure restores confirmed state and preserves the full edit recovery path.
  • Offline, completed Filed, and otherwise read-only details retain disabled checkboxes.
  • Behavioral tests cover parser mapping and mobile interaction states.
## Problem Markdown task lists are visible in mobile issue detail, but every checkbox is disabled. Operators must open the full raw-Markdown editor, locate a marker, and save the whole description to record one completed step. ## User outcome On writable, online assigned issues, an operator can toggle a checklist item directly in mobile detail. The update targets the exact source marker, uses the existing revision-checked content mutation, refreshes local state on success, and fails safely on conflicts or network errors. Offline and read-only details remain non-interactive. ## Acceptance criteria - Enabled checklist controls are accessible and at least 44×44 CSS pixels on writable online issue details. - Activating one control changes only its exact Markdown task marker and submits the loaded `expected_updated_at`. - Fenced code, duplicate labels, nested lists, CRLF input, and `[X]` markers map to the correct source task. - While pending, checklist controls cannot overlap mutations. - Success refreshes rendered detail and cached issue revision/body and announces completion. - Conflict/network failure restores confirmed state and preserves the full edit recovery path. - Offline, completed Filed, and otherwise read-only details retain disabled checkboxes. - Behavioral tests cover parser mapping and mobile interaction states.
timmy self-assigned this 2026-08-15 16:31:43 +00:00
timmy closed this issue 2026-08-15 16:54:48 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
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#905
No description provided.