Guide
Imagine you are linking a Feature to a Release — most often than not, it should be either the latest or the upcoming Release, not the one dating back to 2019. Or when linking a Task to a Project, rarely you want to see archived Projects.
Relation filters allow you to narrow down the selection — for example, exclude old Releases and finished Projects.
Reasons to add relation filters
Simplify the workspace for your teammates
No one likes to sift through a bunch of data. Picking from 3-5 relevant options with a single click is another story!
Cut on loading time
If your related Database has thousands of Entities, you can go from seconds to milliseconds by applying the filters.
Enforce a process or a workflow
For example, don't suggest a Sprint if it's full or an Assignee if they are on vacation.
☝️ Check out Disabling Show other… option section below if you want to be stricter.
As with most Fibery features, it takes one capable person (you!) to make the workspace work better for everyone.
How to configure relation filters?
Configure filters in the same way you do it on Views with Filters:
For relations to User DB, we add a filter to exclude deactivated Users by default.
Using dynamic values
Often one relation dropdown depends on another one:
when planning a Story into a Sprint, show only the Sprints of the relevant Team;
when assigning a person to a Task, show only those who work on the Project;
when linking a Feature to an Epic, show only the Epics in the relevant Product.
In this case, pick a dynamic value marked with 𝑥 instead of a specific Entity. The relation dropdown will adapt as you navigate to different Entities.
Where relation filters apply?
Filters apply, basically, everywhere you see the control on the screenshots above. Namely:
Entity View: Fields on the right and pinned Fields
Table View: relation Field cells
Editable units on all Views and in rich-text mentions
Buttons: ask user to provide value
Automation actions: updating a relation Field
Full Add internal Forms (the dialog for creating a new entity in a view that makes use of a form)
If relation filters use a dynamic value and it's not accessible (ex. there is no This … in automations), we don't apply any of the filters.
The only place where we don't apply the filters is… filters! Sorry, dawg, we can't pimp your Fibery:
The filters also do not apply when you link an Entity via a search popup:
This popup shows recent items by default instead. As usual, if this doesn't fit your workflow, please let us know via Intercom.
Sorting suggested options
Once you narrowed down the number of suggested options to a manageable number using filters, apply relevant sorting:
Sorts work in the same way they do on Views.
Disabling "Show other…" option
To prevent users from picking an option that doesn't satisfy the filter criteria, switch the toggle to off:
This setting applies to UI only, a User is still able to link an arbitrary Entity via the API, by dragging and dropping on a Board or copy and pasting on a Table.
When the option is turned off, we try to automatically set the filter values for newly created Entities, in the same way we do on Views — see Filters.