# Sep 21, 2023 / šŸ„¹ Watch Entity (through tears), AI Search is out of beta, no fixed bugs **URL:** \ **Category:** Changelog\ **Created:** [September 21, 2023, 10:58am UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182 "2023-09-21T10:58:09Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![MaxL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/maxl/32/6137_2.png) [@MaxL](https://community.fibery.io/u/MaxL)\ **Post date:** [September 22, 2023, 12:25pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/21 "2023-09-22T12:25:26Z")
How do I disable the auto-watching of entities that I have created or at least hide unnecessary changes from automation rules? I get spammed with tons of notifications from changes due to automation for our tickets that trigger after creation due to that changeā€¦ And [this](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/16) is just not true, there is no such automation rule on our database yet they are still auto-watched. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 22, 2023, 12:28pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/22 "2023-09-22T12:28:32Z")
> [@MaxL](#): > > And [this](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/16) is just not true, there is no such automation rule on our database yet they are still auto-watched. I think the point is that, from now on, creators are not automatically watchers, but those who were previously made watchers based on the default rule, will not have been removed as watchers. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 22, 2023, 12:29pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/23 "2023-09-22T12:29:36Z")
> [@MaxL](#): > > How do I disable the auto-watching of entities that I have created or at least hide unnecessary changes from automation rules? You can turn off watch on any entity you like. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/946bae20e34109e2e65dcea4a60e894c4ffe1a22.png) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 22, 2023, 12:33pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/24 "2023-09-22T12:33:20Z")
> [@MaxL](#): > > How do I disable the auto-watching of entities that I have created or at least hide unnecessary changes from automation rules? I get spammed with tons of notifications from changes due to automation for our tickets that trigger after creation due to that changeā€¦ We already released a version when auto-watch for newly created entities is disabled. For entities created from yesterday till today (~11 am CET) watch was enabled. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 22, 2023, 12:33pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/25 "2023-09-22T12:33:58Z")
> [@MaxL](#): > > And [this](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/16) is just not true, there is no such automation rule on our database yet they are still auto-watched. This rule you can create for yourself if you need it. It is just an example ---
**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\ **Post date:** [September 22, 2023, 1:14pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/26 "2023-09-22T13:14:29Z")
> [@mdubakov](#): > > ## šŸ¦ Fixed Bugs > > šŸ˜° None. Is something missing is [this bug report](https://community.fibery.io/t/hide-empty-rows-columns-for-views-in-smart-folder/5156) ? For the first time I got zero feedback on a post here. ---
**Author:** ![MaxL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/maxl/32/6137_2.png) [@MaxL](https://community.fibery.io/u/MaxL)\ **Post date:** [September 22, 2023, 3:27pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/27 "2023-09-22T15:27:10Z")
My point is that new entities (that I just created) are still getting auto-watched, even without any rule. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/97629b9ce909ef9361c94426247538c77f369c11.png) This was created just a few seconds ago. > [@Chr1sG](#): > > I think the point is that, from now on, creators are not automatically watchers, but those who were previously made watchers based on the default rule, will not have been removed as watchers. Yes, thatā€™s what I would expect. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 22, 2023, 3:29pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/28 "2023-09-22T15:29:52Z")
> [@MaxL](#): > > My point is that new entities (that I just created) are still getting auto-watched, even without any rule. Please note that we have another rule as well, entity you assigned to are also auto-watched. Here I believe this was the case. ---
**Author:** ![MaxL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/maxl/32/6137_2.png) [@MaxL](https://community.fibery.io/u/MaxL)\ **Post date:** [September 22, 2023, 3:31pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/29 "2023-09-22T15:31:28Z")
> [@mdubakov](#): > > Please note that we have another rule as well, entity you assigned to are also auto-watched. Here I believe this was the case. Ah, I see. Please make that optional the same way as well. We auto-assign people on creation. Having them get notification about every individual change in the ticket is extreme overkill (and a behaviour change without any way to disable it) and should be based on a choice by the user. ---
**Author:** ![MaxL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/maxl/32/6137_2.png) [@MaxL](https://community.fibery.io/u/MaxL)\ **Post date:** [September 22, 2023, 3:33pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/30 "2023-09-22T15:33:19Z")
As a general feedback besides the auto-watching: I would expect the auto-watching to toggle-able on a per-user basis in their settings as some might want this and others not. Doing it on a per-database basis might work for some workflows but not for others. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 22, 2023, 3:35pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/31 "2023-09-22T15:35:15Z")
Iā€™m pretty sure that notification of changes to Assignees has always been enabled, even before the new ā€˜watchā€™ functionality was added. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 22, 2023, 3:37pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/32 "2023-09-22T15:37:42Z")
> [@MaxL](#): > > I would expect the auto-watching to toggle-able on a per-user basis in their settings as some might want this and others not. Doing it on a per-database basis might work for some workflows but not for others. Each user can define his/her own filters for the Inbox: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1667049792763fd5556f6149acdc31495ef8d117.png) ---
**Author:** ![MaxL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/maxl/32/6137_2.png) [@MaxL](https://community.fibery.io/u/MaxL)\ **Post date:** [September 22, 2023, 3:53pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/33 "2023-09-22T15:53:44Z")
> [@Chr1sG](#): > > Iā€™m pretty sure that notification of changes to Assignees has always been enabled, even before the new ā€˜watchā€™ functionality was added. No. You would only get notified about comments when you were assigned, not about changes in every single field. > [@Chr1sG](#): > > Each user can define his/her own filters for the Inbox: > > ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1667049792763fd5556f6149acdc31495ef8d117.png) That filter does not work. I only need notifications about specific changes on specific entity types. Neither does the filter allow filtering for that (e.g. specific fields) nor should every single user in a company be required to setup the filters manually. We already have automation that sends notifications on changing of specific fields that we need people to get notified about, we donā€™t need notifications for every field (e.g. some are just not interesting for the assignee and only for planning/tracking by project leads or managers) Iā€™m really confused as to how anyone would think that ā€œbreaking existing workflows without a way to fix itā€ is okayā€¦ ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 22, 2023, 4:07pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/34 "2023-09-22T16:07:07Z")
> [@MaxL](#): > > You would only get notified about comments when you were assigned, not about changes in every single field. Ah yes, youā€™re right, it was comments only. My bad, sorry. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 23, 2023, 7:05am UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/35 "2023-09-23T07:05:57Z")
> [@MaxL](#): > > Iā€™m really confused as to how anyone would think that ā€œbreaking existing workflows without a way to fix itā€ is okayā€¦ I am not sure what you mean here. The fallback is to have this filter, so you will not have Watch notifications at all and almost everything will be like without Watch feature. ![Screenshot 2023-09-23 at 10.05.28 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f3bbf4dd3610e8c11d7f5f519b6b032046f41a45.png) ---
**Author:** ![MaxL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/maxl/32/6137_2.png) [@MaxL](https://community.fibery.io/u/MaxL)\ **Post date:** [September 25, 2023, 11:00am UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/36 "2023-09-25T11:00:59Z")
> [@mdubakov](#): > > I am not sure what you mean here. The fallback is to have this filter, so you will not have Watch notifications at all and almost everything will be like without Watch feature. > > ![Screenshot 2023-09-23 at 10.05.28 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f3bbf4dd3610e8c11d7f5f519b6b032046f41a45.png) Ah, I see. But while this at least gets rid of the spam in the notification this would mean that there is no way to manually decide which entities to watch and which you donā€™t want to watch. I really donā€™t understand how auto-watching canā€™t just be a toggle in your user profile (or an automation like what you added for entity creation) ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 25, 2023, 11:28am UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/37 "2023-09-25T11:28:09Z")
> [@MaxL](#): > > there is no way to manually decide which entities to watch and which you donā€™t want to watch You can manually unwatch anything ---
**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\ **Post date:** [September 26, 2023, 8:17am UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/38 "2023-09-26T08:17:18Z")
> [@mdubakov](#): > > Weā€™ve removed automatic Watch of entity when you created it. > It seems this is what causing most of the problems. The other case of notification spam I notice is when I take actions that result in changes like comments and so I get informed that a comment was added through the automation I triggered. But I can see that filtering this out might be more hassle than the savings. šŸ™‚ ---
**Author:** ![MaxL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/maxl/32/6137_2.png) [@MaxL](https://community.fibery.io/u/MaxL)\ **Post date:** [September 26, 2023, 3:11pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/39 "2023-09-26T15:11:36Z")
> [@Chr1sG](#): > > You can manually unwatch anything Right, but having to do two additional clicks just to restore the previous. wanted behaviour is really not ideal. (And doesnā€™t even solve the issue fully as someone else might assign you, then you are back to square one getting spammed until you go online again and are able to go through the motions of unwatching it) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 26, 2023, 3:14pm UTC](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182/40 "2023-09-26T15:14:48Z")
We removed notifications for Rules on prod as well now, so basically two major sources of spam removed: - No more auto-watch when you create entity - No notifications from automatic Rules for watched entities. Letā€™s see how it will work [Previous page](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182.md?page=1) [Next page](https://community.fibery.io/t/sep-21-2023-watch-entity-through-tears-ai-search-is-out-of-beta-no-fixed-bugs/5182.md?page=3)