# Search: allow search by entity URL

**URL:** <https://community.fibery.io/t/search-allow-search-by-entity-url/3052>\
**Category:** Ideas & Features\
**Tags:** search\
**Created:** [July 8, 2022, 2:45am UTC](https://community.fibery.io/t/search-allow-search-by-entity-url/3052 "2022-07-08T02:45:32Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [July 8, 2022, 2:45am UTC](https://community.fibery.io/t/search-allow-search-by-entity-url/3052/1 "2022-07-08T02:45:32Z")

</div>

FIbery Searching (whether the Ctrl+K variety, the Rich-Text-linking “#” variety, or a Relation field) currently has some very frustrating limitations – namely:

1. Inability to limit the search scope (either manually or intelligently).
2. Insufficient detail in search results to distinguish similarly-named results.
3. Poor index coverage (only Name and Rich Text fields).

If I want to link to a Task “BUILD Homepage” in a Rich Text by typing “#BUILD Home”, I may get 20 results that all present the exact same name – BUILD Homepage – with no additional detail! – because my Task Names do not include their Project Name. So the search results give me no way to tell which Task belongs to which Project. 😢

This is, frankly, embarrassing.

Asana’s solution is to organize search results into different sections for different entity types (Project, Task, etc.), and each result is also shown with additional context/detail.

**A temporary work-around** for this frustrating Fibery limitation could be to **index entity URLs**. Then we could at least use other methods to find the entity we need, and simply copy its URL to where it should be linked (i.e. enter its URL in the Search to locate the actual entity).

**The real solution** is more like:  
**1)** Increase the amount of detail displayed in all search results  
**2)** Search scoping  
**3)** Better index coverage, so we could e.g. include (part of) the Project Name when searching for a Task, to narrow the results.  
**4)** Bonus points for intelligently ranking search results by “proximity” (or some similar metric) and displaying the reason for each search result’s position (e.g. “Same Project as current entity”).

**Or how about this for an idea 💡 – When I hover over a search result’s Public Id** , show a popup with more details on that entity, like maybe all its pinned fields – even better if they are active!

---

_[View the full topic](https://community.fibery.io/t/search-allow-search-by-entity-url/3052)._
