Auto-assign the creator as the subitem's owner

Auto-assign the creator as the subitem's owner

TL;DR: Whenever someone creates a new subitem, they automatically become its owner. No more "who added this?" investigations or manual ownership assignment. Setup takes 1 minute.

What this does

Recipe: "When subitem is created, assign creator as owner."
The moment a new subitem is added, the People column on that subitem is auto-populated with whoever created it. No matter who's adding subitems — team members, guests, automations triggered by other people — the creator owns it.

When to use it

  • Accountability by default — every subitem has a clear owner from the start
  • You'd rather opt out of ownership (delete the value) than chase missing assignments
  • Customer support / triage workflows where the person who logs the issue owns it until reassigned
  • Standardizing onboarding workflows where each new task is self-assigned to its creator
If you want every new subitem assigned to a specific person (not the creator), use the "When subitem is created, set owner to value" variant instead — it hard-codes a single owner regardless of who created it.

Before you start

  • A People column on the subitem — this is where the owner is set

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: select your subitem's People column (the "owner" destination).
    Click Create automation.

Test that it works

    Create a new subitem on any item.
    Open the subitem and check the People column — your name should be there automatically.
    Have a teammate create a subitem under the same parent — confirm their name lands in the People column.

Common gotchas

  • The People column must exist on the subitem. If it doesn't, the automation has nowhere to write.
  • Creator means the user who clicked "Add subitem" — not the parent's owner. If a teammate adds a subitem on your item, they own it (not you).
  • Automations that create subitems also count. If a recipe like "When status changes, create a subitem" fires, the user who triggered the upstream change becomes the new subitem's owner.
  • Existing subitems are not back-filled. This recipe fires on creation only. To assign owners to subitems already on the board, do it manually or use a status-triggered People-column automation.
  • For role-based assignment (e.g. all "Design" subitems go to one person, all "QA" go to another) use the by-name variant: "When subitem is created and if the name is this name, set owner to value."

Next up

Related

  •  Create subitems automatically  (parent landing)
  •  Link subitem to its parent on creation  (companion default — wire subitems to parents at creation)
  •  Sync values between parent & subitem  (inherit values from the parent)

Still stuck?

Email  hello@fantasymedia.io  and we'll help you wire up the right ownership rule.