Thank you all for submitting your ideas! :)

Now, you can automate child-parent relations and set actions for the triggered item's Child or Parent. Examples:

Case A, when something happens to Child item, known examples:

When new tag is assigned to Child item, assign this tag to Parent item.

When Child item is completed, update Custom field [type: date] with the trigger date.

When specific Child item is completed, change Parent item’s status to [Status].

Case B, when something happens to Parent item, known examples:

When new tag is assigned to Parent item, assign this tag to all Child items.

When Custom field x is updated with value Y, add this value to all Child items. (When Custom field ‘Contract no’ is updated with value – Any, copy this value to all child items.

If you need help in setting up specific scenarios, feel free to contact me directly.

Cheers,

K.

Thank you for this release! It's very powerful in combination with tags. We will have a much less meticulous workflow now 🫶

That would be great, but I guess in some cases full sync will be usefl, and in other cases a simple inheritance at the creation of the child item will be enough. For instance our use case will be project id or client name, so getting the value of the parent at the creation of the cild allows for good fill rate of the custom fields (always getting the parent value) + allowing scenarios where the child item can use its own value if needed