# \[DONE\] More flexibility to determine what gets indexed: Text and Select fields **URL:** \ **Category:** Ideas & Features\ **Tags:** search\ **Created:** [June 13, 2022, 3:58am UTC](https://community.fibery.io/t/done-more-flexibility-to-determine-what-gets-indexed-text-and-select-fields/2939 "2022-06-13T03:58:10Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [June 13, 2022, 4:40am UTC](https://community.fibery.io/t/done-more-flexibility-to-determine-what-gets-indexed-text-and-select-fields/2939/2 "2022-06-13T04:40:15Z")
Similar/same? > [@\[DONE\] Add search by fields](https://community.fibery.io/t/add-search-by-fields/2178): > > Currently, it’s not possible to search by fields. For instance, we have a Hiring app with Candidates. Two fields: Email, Phone. We can’t use search by these fields. That is super uncomfortable. We have to add email to the card and use CMD+F to find the person. Also related: > [@Filter search results based on Field Values](https://community.fibery.io/t/filter-search-results-based-on-field-values/1052/18): > > In doing a comparison of ClickUp and Fibery search functions today (Fibery won in a landslide, it’s shocking how bad ClickUp search is!), I again came upon the desire for the more general interpretation of this feature request. I even forgot that there had been further discussion in this topic about the possibility of extending the specific “filter based on workflow status” to the more general “filter based on contents/status of arbitrary fields”, and I came to the forum to make exactly that req… --- _[View the full topic](https://community.fibery.io/t/done-more-flexibility-to-determine-what-gets-indexed-text-and-select-fields/2939)._