# Suggestion for how to assign issues to user requestor based on email?

**URL:** <https://community.fibery.io/t/suggestion-for-how-to-assign-issues-to-user-requestor-based-on-email/1106>\
**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:** 2

<div class="post-metadata">

**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:** [October 28, 2020, 8:28pm UTC](https://community.fibery.io/t/suggestion-for-how-to-assign-issues-to-user-requestor-based-on-email/1106/2 "2020-10-28T20:28:43Z")

</div>

You can achieve step 3. by using an auto-relation.  
Instead of using the Assignment extension, create a relationship between the Issue type and the User type, and set it to automatically link when the value of the Issue field used for email (added by Zapier) matches the email field for the User.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/132cc4363de5acb5cf27d4d68c04cd2daa441659.png)  
The disadvantage of this is that these sort of relationships to Users don’t provide the notification functionality that the Assignment extension does, but if you can live with that, it gets you what you wanted.  
Hopefully, a more developed notification functionality won’t be too long coming 🙂  
See [here](https://community.fibery.io/t/set-up-notifications-for-secondary-user-fields/904) and [here](https://community.fibery.io/t/set-up-notifications-for-secondary-user-fields/904) and [here](https://community.fibery.io/t/watcher-of-an-entity-use-the-assignment-extension/563).

---

_[View the full topic](https://community.fibery.io/t/suggestion-for-how-to-assign-issues-to-user-requestor-based-on-email/1106)._