On our Project Management space, I have an automation that add myself into a people field when I create a Task for myself and when the people field is empty at creation. To assign the Task to myself, I’m using the Update action of the automation.
Every time I create a Task for myself, I’m notified. I want to be notified when someone assign me to a task but not when I assign myself to it.
I don’t know what’s the best way to address this but perhaps a new source of notification could be added on personal notifications settings.
There’s a button at the bottom of the automation to select whether the automation notifies the a user on their own changes or not. Is this what you’re looking for?
Currently I’m using the notification function of the people field. The automation is only to assign the person to the created Task but I’m going to explore the possibility to fully migrate to the automation. Thanks
I need to create a 2nd automation : one for the auto Assignment on event Task Created and one for the notification on event Entity linked to a Task.
if the User is watching the task, he will receive 2 notifications : 1 from the automation and 1 from the Watch engine. Normally, the Users that are added after the creation aren’t watching the task. But if for some reason they Watch the task, it can be confusing as there’s some uncovered scenarios/greys area.
People field is set to assign entities to current user when created as default value
People field has a toggle to disable notifications to user who created the entity
This way automations can consistently trigger a notification but people field defaults can be disabled.
Re: present workarounds for you Jonathan, if you move the auto-assign behavior to a 3rd party tool that is authenticated as your account (Make, Zapier, n8n), you will not get a notification when you are assigned to tasks by that automation.
Fibery rightly differentiates between actions automations and scripts take, and actual user actions. So the fastest resolution is to make your user take the action.
Agree with you, people field should be populated with more options. But I think that some consolidation between the notifications option on fields and the notifications section on personal settings are needed. It’s a little bit confusing to have one part of notifications functions in one place and the other part in another place.
Thanks for the tip. Currently, I prefer to keep the things simple and clean. I will wait for an official solution.
Making business logic for notifications is hard. If you haven’t already seen it, check out the flow diagram in this article for how slack decides whether to send a notification or not:
At some point, it would be nice if we had a diagram of how Fibery logic works, and then people in the community can argue between themselves about which bits they agree/disagree with
