The short answer
Duplicated items drift because nothing connects them after the moment of copying. A “create item in another board” automation is a one-time event: from that second on, you have two independent items that happen to look alike. Every status change, comment, date move, or new column that touches only one of them widens the gap. The permanent fix isn’t a better sync automation — it’s not having two items: one item that lives on both boards.The anatomy of drift
- Edits land on one copy. Someone updates the status where they work; the other board still shows last week.
- Updates split. A question is asked on copy A, answered nowhere, re-asked on copy B. The context of the work is now in two half-threads.
- Sync automations are event-based and lossy. Recipes pause, hit rate limits, or error silently; a missed event = permanent difference nobody notices until it matters.
- New columns aren’t mapped. Add a column to one board and every existing recipe quietly ignores it.
- Two-way sync echoes. Point automations both directions and you get loops, races, and “who changed this?” mysteries.
- Deletes don’t propagate. Archive the original; the orphan copy lives on, wrong forever.
The permanent fix: one item, many boards
With Same Item Multiple Boards, the item isn’t copied to the second board — it exists there. There is no second item to drift:- Columns stay equal because they’re the same item’s columns, matched by name and type (supported columns).
- Updates are one thread readable from every board.
- Subitems come along automatically.
- If anything ever looks off, the Discrepancy Report finds it and applies the latest value.