# Suggestion for how to assign issues to user requestor based on email? **URL:** \ **Category:** Get Help\ **Created:** [October 28, 2020, 5:50pm UTC](https://community.fibery.io/t/suggestion-for-how-to-assign-issues-to-user-requestor-based-on-email/1106 "2020-10-28T17:50:29Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [October 28, 2020, 10:57pm UTC](https://community.fibery.io/t/suggestion-for-how-to-assign-issues-to-user-requestor-based-on-email/1106/3 "2020-10-28T22:57:42Z")
Chris, thanks for the promo of this one, which I’ll embed in case somebody else didn’t take a moment and clickthrough: > [@\[DONE\] "Watcher" of an Entity](https://community.fibery.io/t/watcher-of-an-entity-use-the-assignment-extension/563): > > Hi guys, I was interested in creating the equivalent functionality of “watcher” that is offered by a lot of PM apps around their tasks and entities. This is a user who is “subscribed” to an entity’s activity - so they are informed when any status changes, fields are adjusted, comments are made, and so forth. Can I use the “assignment” extension to create this functionality? Or would I need to do this another way if that extension needs to be reserved for only actual assignees? Thanks guys! Did you see this post recently in Twitter? > Our work in progress: > > 🤖 Automatically generate Name using a text formula > 🦚 Share the whole workspace as a template > 🧶 Jira Integration > 🥶 Documents and Entities sharing > > Fibery 2.0 is close... > > — Fibery (@fibery\_io) [October 23, 2020](https://twitter.com/fibery_io/status/1319560763183333377?ref_src=twsrc%5Etfw) The one at the bottom that includes “…Entities sharing” has really raised my hopes that we’ll get a kind of “watcher” you have in other apps. I could really use this, struggling with my team now without that functionality. This is such a basic feature of just about every other tool we’ve used. --- _[View the full topic](https://community.fibery.io/t/suggestion-for-how-to-assign-issues-to-user-requestor-based-on-email/1106)._