TL;DR: When a subitem's column changes, automatically push that value to the matching column on the parent item. The reverse direction of the standard parent → subitem sync. Useful when a single key subitem (status, latest update, owner) should drive the parent's column.
What this does
Recipe:"When subitem column changes, copy that value to this column on parent item."
Whenever a subitem's chosen column changes, the new value is copied up to the matching column on the parent item. Every subitem update overwrites the parent — so this works best when one subitem clearly "owns" the value, or when subitems are sequential and only one is active at a time.
When to use it
A "lead" subitem (e.g. the latest active task) should drive the parent's status, owner, or date
Subitem-level inputs feed a parent-level summary column users browse
Cross-board reporting where parent values are aggregated externally and need to reflect subitem activity
Workflow where subitems are sequential — only one is "active" — and the parent should mirror it
Every subitem update overwrites the parent. If multiple subitems change the same column, the LAST change wins. For filtered logic (only one named subitem feeds the parent, or only when status matches), see the by-name and conditional variants under Smart rules & by-name automations.
Before you start
The same column type on both parent and subitem (Status → Status, Date → Date)
Column names don't need to match — you map them in the automation
The parent's destination column must not be read-only (Mirror, Formula, Last updated)
Set it up
Open Automate → Create on your board.
Copy the recipe text above and find it in your board's automation center, then click Use Template.
Configure:
Subitem column — the source that triggers the sync
Parent column — the destination (must match the subitem's type)
Click Create automation.
Test that it works
Change the value on any subitem's chosen column.
Open the parent item — confirm the matching column now reflects the new value.
Change the same column on a different subitem under the same parent. Confirm the parent updates again to match the latest change (last write wins).
Common gotchas
Last-write-wins. Multiple subitems changing the same column will keep overwriting the parent. If you need only one subitem to drive the parent, use the by-name variant: "When subitem column changes and if the subitem's name is this name, copy that value to this column on its parent item."
Conditional variants exist. If you want the sync to fire only when a label condition is met, see "When subitem column changes and only if this label/status is/is not this label, copy that value to this column of the parent item."
Column types must match. Status → Status. You can't sync a Status to a Date.
Loop risk. If you also have a parent → subitem cascade on the same column pair, you can create a feedback loop. Test before deploying both directions on the same column.