Good point. I think Default value for People fields is actually a better approach to this.
Consider:
- 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.