# Filter when linking issues in table **URL:** \ **Category:** Get Help\ **Created:** [January 15, 2026, 5:07pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248 "2026-01-15T17:07:41Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Fabian](https://avatars.discourse-cdn.com/v4/letter/f/f6c823/32.png) [@Fabian](https://community.fibery.io/u/Fabian)\ **Post date:** [January 15, 2026, 5:07pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/1 "2026-01-15T17:07:41Z")
Hey, I created an abstract example of my real problem. This is my data: Note that two children have the same name and are only distinguishable by Family. ![Screenshot 2026-01-15 at 17.45.10](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3ff5fe2edffca215d74d230c71e105fc93df8f30.png) From the schools point of view, I want to select and link children to the school. I created a table view, where I can select children: ![Screenshot 2026-01-15 at 17.53.13](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/38b9d82ac1ab0058e1741b7f378c99f9c138379d.png) Since the names are equal, I cannot per se distinguish between Tim Jones & Tim Smith. It would be easy, if the drop down could display additional fields like Family. It is possible to create a filter in order to filter for the Family: ![Screenshot 2026-01-15 at 17.54.40](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/30f7adfd87942296ba03ddb1a7c1e419f3e9e176.png) My Problem: Unfortunately, this filter remains set even for other newly created views with the database school. ![Screenshot 2026-01-15 at 18.04.29](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f1fcf30dca0e8b8ce9ad65c4f692f97454be2c09.png) If I change the Filter in the new School table to Smith, it also changes in the first table. That makes co-editing on separate views impossible. It there a better way to link Children to Schools (from School point of view?) ---
**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:** [January 15, 2026, 5:12pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/2 "2026-01-15T17:12:31Z")
Why not add a `First name` field to your children database, and then define the `Name` field with a formula as `[First name] + “ “ + Family.Name` (or `Family.Name + ", " + [First name]` if you’d prefer) You could also rename the `Name` field to `Full name` if you want to avoid ambiguity ---
**Author:** ![Fabian](https://avatars.discourse-cdn.com/v4/letter/f/f6c823/32.png) [@Fabian](https://community.fibery.io/u/Fabian)\ **Post date:** [January 16, 2026, 2:00pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/3 "2026-01-16T14:00:21Z")
The example is a very simplified abstraction of the real data. In the real dataset it is not feasible to extend the Name field to create different entity Ids. Those are distinguished by their relation in a more complex hierarchy tree. ---
**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:** [January 16, 2026, 2:07pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/4 "2026-01-16T14:07:28Z")
> [@Fabian](#): > > In the real dataset it is not feasible to extend the Name field to create different entity Ids. Those are distinguished by their relation in a more complex hierarchy tree. Can you explain what you mean. The name has no effect on entity Ids ---
**Author:** ![Fabian](https://avatars.discourse-cdn.com/v4/letter/f/f6c823/32.png) [@Fabian](https://community.fibery.io/u/Fabian)\ **Post date:** [January 16, 2026, 4:07pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/5 "2026-01-16T16:07:34Z")
Sorry, I mean the visible name that appears when I want to link a child entity in the drop down. It is not feasible for us to change that in order to avoid duplicate names. We need other options to distinguish the child enities with the same name. ---
**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:** [January 16, 2026, 4:26pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/6 "2026-01-16T16:26:26Z")
> [@Fabian](#): > > It is not feasible for us to change that in order to avoid duplicate names. Why? Are you saying that you want to have multiple entities with the name `Tim` rather than having `Tim Jones` and `Tim Smith`? Why? Is it because there are some users who need to know that the child is called Tim but not know the family name? Or …? ---
**Author:** ![Fabian](https://avatars.discourse-cdn.com/v4/letter/f/f6c823/32.png) [@Fabian](https://community.fibery.io/u/Fabian)\ **Post date:** [January 16, 2026, 4:57pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/7 "2026-01-16T16:57:03Z")
Hey Chris, we have a 5 tier hierarchy: Space → Module → Submodule → Work Package → Task Work Packages can have names which can be quite long: e.g. “Audio and video theme alignment” We have those Work Packages for each Submodule, so we have a lot of duplicates with that name. I would like to avoid prefixing every Work Packages with Space / Module / Submodule because of the resulting long names. Especially because we have created this hierarchy to give context to the Work Packages. I appreciate your interest in the details, I suppose you want to help us solving the issue by questioning our structure, which is very welcome. But on the other hand, it would also help if you could answer my question, if there is a better way to link entities? Thanks a lot. ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [January 16, 2026, 5:03pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/8 "2026-01-16T17:03:44Z")
Please vote for this feature which would solve your problem. Many of us have this same pain point and there’s no real solution that doesn’t involve unique long, ugly entity names. > [@Display fields in "link or create" window](https://community.fibery.io/t/display-fields-in-link-or-create-window/5679): > > I have many things in a single database that are all named the same. For example, in my “Iteration” database I already have over 200 records called “Iteration 1” and there will ultimately be thousands more named the same way in the future. I wish that when I clicked on “Link or create”, I would be able to view some fields (like “Client” or “Due Date” or “Team” for example) that are on the entity I’m trying to link to. Currently the only fields that are shown are “Name” and “ID” and “Database”… ---
**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:** [January 16, 2026, 7:57pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/9 "2026-01-16T19:57:34Z")
> [@Fabian](#): > > t would also help if you could answer my question, if there is a better way to link entities? Unfortunately, the direct answer is that it’s currently not possible to see anything but the name when linking. I guess I should have answered that first before digging into the details of the use case. It’s just a habit I have of trying to keep asking q.s until I get the to the root cause… ---
**Author:** ![Renato\_Carvalho](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/renato_carvalho/32/11001_2.png) [@Renato\_Carvalho](https://community.fibery.io/u/Renato_Carvalho)\ **Post date:** [January 16, 2026, 9:42pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/10 "2026-01-16T21:42:44Z")
I believe this is what @Fabian wanted. I asked for this in other places. That’s something that would be really, really useful. ---
**Author:** ![Fabian](https://avatars.discourse-cdn.com/v4/letter/f/f6c823/32.png) [@Fabian](https://community.fibery.io/u/Fabian)\ **Post date:** [January 19, 2026, 12:25pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/11 "2026-01-19T12:25:22Z")
It could be more manageble with the drop down filter: ![Screenshot 2026-01-15 at 18.04.29](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f1fcf30dca0e8b8ce9ad65c4f692f97454be2c09.png) However, as mentioned above, this filter setting is fixed for every other view. I do not understand the reasoning behind this. This makes it impossible to prepare separate views with pre-defined drop-down filters. Moreover, this drop down filter can only be set by the Architect access level - which makes it impossible for Editor users to filter according to their needs. It should be more like the personal filter feature. ---
**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:** [January 19, 2026, 12:34pm UTC](https://community.fibery.io/t/filter-when-linking-issues-in-table/10248/12 "2026-01-19T12:34:25Z")
> [@Fabian](#): > > I do not understand the reasoning behind this. > > This makes it impossible to prepare separate views with pre-defined drop-down filters. This functionality is called ‘[relation filter](https://the.fibery.io/@public/User_Guide/Guide/Relation-Filters-and-Sorts-177)’ and is indeed not intended to address your use case of wanting to find specific, different subsets each time.