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

Resolve offline checklist conflicts from mobile Drafts #913

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

User problem

Offline checklist progress is safely stopped when Gitea has changed, but the Needs attention card can only retry the same stale revision or discard work. Mobile operators need to reconcile local task-state changes with the latest issue without losing collaborators’ edits.

Acceptance criteria

  • A conflicted issue-content outbox record is identified as a checklist conflict and offers a Review changes action.
  • Review merges only unambiguous local checklist-state deltas onto the latest issue body while preserving remote prose and unrelated checklist edits.
  • Ambiguous, renamed, or deleted checklist items are reported and never silently overwritten.
  • Applying the review replaces the stale queued mutation with the merged body and latest revision, then retries through the existing conflict-safe outbox.
  • Cancel leaves the conflict intact; another upstream race returns it to Needs attention.
  • Account isolation and existing offline completion/close ordering remain intact.
  • Mobile controls remain keyboard/screen-reader operable and at least 44px.

Implementation must use strict TDD and preserve the full suite.

## User problem Offline checklist progress is safely stopped when Gitea has changed, but the Needs attention card can only retry the same stale revision or discard work. Mobile operators need to reconcile local task-state changes with the latest issue without losing collaborators’ edits. ## Acceptance criteria - A conflicted issue-content outbox record is identified as a checklist conflict and offers a Review changes action. - Review merges only unambiguous local checklist-state deltas onto the latest issue body while preserving remote prose and unrelated checklist edits. - Ambiguous, renamed, or deleted checklist items are reported and never silently overwritten. - Applying the review replaces the stale queued mutation with the merged body and latest revision, then retries through the existing conflict-safe outbox. - Cancel leaves the conflict intact; another upstream race returns it to Needs attention. - Account isolation and existing offline completion/close ordering remain intact. - Mobile controls remain keyboard/screen-reader operable and at least 44px. Implementation must use strict TDD and preserve the full suite.
timmy self-assigned this 2026-08-15 19:51:49 +00:00
timmy closed this issue 2026-08-15 20:04:13 +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#913
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?