Skip to main content

DevTodo and Board Synchronization

Why it matters​

Board tracks global status flow. DevTodo tracks developer execution order. These layers are synchronized to avoid drift.

Synchronization behavior​

  • Accepting/planning tickets can create/ensure linked DevTodo tasks.
  • Reassigning/clearing assignee normalizes linked tasks.
  • Status transitions produce task.synced domain events.
  • Reopen scenarios can reactivate linked tasks.

Operational checks​

  • If board and DevTodo diverge, inspect:
    • ticket assignee,
    • current ticket status,
    • outbox entries for task.synced.