# \[DONE\] "Watcher" of an Entity

**URL:** <https://community.fibery.io/t/done-watcher-of-an-entity/563>\
**Category:** Ideas & Features\
**Tags:** notifications\
**Created:** [February 19, 2020, 6:56am UTC](https://community.fibery.io/t/done-watcher-of-an-entity/563 "2020-02-19T06:56:24Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![HereBeBeasties](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/herebebeasties/32/5429_2.png) [@HereBeBeasties](https://community.fibery.io/u/HereBeBeasties)\
**Post date:** [September 16, 2022, 7:34pm UTC](https://community.fibery.io/t/done-watcher-of-an-entity/563/29 "2022-09-16T19:34:54Z")

</div>

> [@Chr1sG](#):
>
> > [@HereBeBeasties](#):
> >
> > notifications are honestly the biggest drawback … and very nearly made us not buy the product.
> 
> But for every user that complains that product area X is just not good enough, there are other users for whom X is just about good enough. It’s like the pareto principle in multiple dimensions.

I agree that people have different priorities for functionality, but good notifications are pretty much key to staying on top of things and getting work done, in almost all problem domains.

I guarantee you that no one using Fibery where entities need to be observed by someone other than the actual assignee thinks that notifications are “good enough”.

Watchers would be a huge improvement for hopefully very little work. You’d clone/refactor the assignees functionality, remove a couple of bits from it (it won’t be used for avatars badges on summary links, etc.), call it watchers, and be done.

Not only would it _massively_ improve the user experience, but it seems like a relatively easy task that is unlikely to result in compromises or knock-on difficulties elsewhere in the system. (Of course I may be wrong here - I am not a Fibery dev, just an experienced external dev looking in.)

---

_[View the full topic](https://community.fibery.io/t/done-watcher-of-an-entity/563)._