Stop automatically subscribing automation creators to items created from their automation

Feature requests
, , , ,
1

I have searched for other threads on this, and while I came across a couple they were more than a year old with no solution. I have created an automation process for my company that automatically creates an item on another board and links the two.

I have sorted out through some trial and error that because I created the automation, I am automatically subscribed to all the new items in the linked board. This is highly inconvenient, because I get bell notifications for every update on every item (there are over 100) which multiple teams are working on. I need my notifications feature to be limited to my own work so I can stay on top of updates from my own tasks.

The only way I have found to stop this is by going into each item in the linked board, selecting “manage subscribers,” and unsubscribe myself from each item (which takes multiple clicks). This will take forever. Can someone explain to me why i’m automatically subscribed to items that are created through an automation? Is there no way to change that? If not, it seems like a bug! This is happening with all kinds of automations where items are created, including automations that create subitems for a new task – even if I’m not the creator/owner of the item, it subscribes me to the subitem. Seems the only reason this is happening is because I created the automation.

Please help! Thanks

2

Just adding my support for any feature / change that could remove the auto-assigning behaviour. I’ve just noticed it and I find it unhelpful that I can’t stop this from happening.

1 Like
3

To reword this in a more generic way:
The actor associated with an action performed by an automation should be the user that triggered the automation, and NOT the author of the automation. In cases where the automation is not triggered by a user action (e.g. timers, etc.), the actor should be the system user “Automations” and NOT the author of the automation.

This is a similar to an old feature request and the two should probably be merged and have their votes combined.