# Provide Context for Duplicate Names

**URL:** <https://community.fibery.io/t/provide-context-for-duplicate-names/1534>\
**Category:** Ideas & Features\
**Created:** [April 7, 2021, 1:42pm UTC](https://community.fibery.io/t/provide-context-for-duplicate-names/1534 "2021-04-07T13:42:46Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**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:** [April 12, 2021, 2:33am UTC](https://community.fibery.io/t/provide-context-for-duplicate-names/1534/7 "2021-04-12T02:33:42Z")

</div>

This is a good request, and one simple thing I’d like to see, which is very important if you are using Fibery to track work items, would be seeing which items are closed in the list:

> [@\[DONE\] Seeing "Closed" Entities grayed out in Search Dialog](https://community.fibery.io/t/seeing-closed-entities-grayed-out-in-search-dialog/1298):
>
> As my Fibery instance grows, and the number of entities also grow, it’s becoming harder to find things with the limited search functionality while we wait on better indexing of content, and filters in that dialog. One thing that would really help short-term is adding the excellent “graying” you guys do of Entities with a “closed” type of State. It would be very helpful to see when in the Search Dialog simply closed entities as “gray.” Often I want to link live tasks to other places, like comm…

Also, @Oshyan has request right here:

> [@Filter search results based on Field Values](https://community.fibery.io/t/filter-closed-entities-by-default-in-all-searches/1052/2):
>
> The more I think about this as I am using Fibery, the more I think it might be good to be a global setting of some kind. For example I’d also like to have this filtering for back-links! And having to add filter controls to search and backlinks, and maybe other places may be non-ideal, or at least may be down the road for implementation. I have a thought as to how it might work though, still being customizable and flexible, but without making the UI too complex. These are just ideas, of course. S…

That has additional related solutions, like this one:

> [@Filter search results based on Field Values](https://community.fibery.io/t/filter-search-results-based-on-field-values/1052/4):
>
> This kind of touches on something I’ve made a request on ( _outside the forum_ ): to be able to display certain fields in search results, like with fields you select to show in the collection.

You are talking about generally the “#” dialog, which I otherwise refer to as the “Ctrl + K” dialog - it could use a definition by the Fibery team so it gets a universally accepted way to be referred to, too!. The fact that you can see Entities, Views, and Docs is useful, but does create these needs, since only Entities can have a state and other attributes, while Views and Docs don’t really have any aside from their names.

And while on the subject, on a daily basis my team has told me - and this happens for my own use, too - that they instinctively want to click on a “Type” and see a list of the Entities in it. This is a very common navigation in work management tools. But now, you only get an auto-generated table for each Type, and if you move the Type to another app, that doesn’t work. **So I’d really like to see Types in searches, too**. And it would be great to be able to find an App also in that search, for quicker navigation to each of them.

Thanks!

---

_[View the full topic](https://community.fibery.io/t/provide-context-for-duplicate-names/1534)._
