Proposal: either a new automation, or an expansion of the “clear assignees” (i.e., unassign) function, to remove users from an item’s “Team Subscribers.”
To expand: once someone is assigned to an item (either manually or via automation), they are automatically subscribed to the updates provided to that item. Which is great for receiving any relevant comments, however they see fit, as defined by their notification settings.
However, when they’re un-assigned from an item, the user is not removed from its subscriber list, so they continue to receive updates even if they are no longer responsible for the task(s) at hand. Which can become burdensome, especially for executives who want to eliminate or reduce inbox congestion.
Currently, the only way to remove a team member from being subscribed is to manually remove the users from the subscriber section in each items’ update section, which necessitates a lot of click-thru’s and additional steps. This becomes even more of a hassle when a team deals with a high volume of items. Not to mention that some team members can be less tech savvy then others, so leaders can find themself having to repeat how to unsubscribe or do it for them, which can slow a process down exponentially.
However, if we were able to add an “unsubscribe assignees from updates” to the custom list (allowing us to stack it in an automation with an “and then…” prompt) we could decide when/if it would be appropriate to remove that status.
Alternatively, the “clear assignees” script could automatically remove subscriber status as a part of it’s process and standardize the association between being “assigned” to an item and thus “assigned” to its updates.