Guide
Use filters to narrow down a selection using a combination of conditions:
Filters work in a similar way across Fibery:
This is a common guide although we'll use Views as an example.
Setting up
Add a filter rule
To add a basic filter:
select Filters
click + Add Filter and select Add Filter Rule
pick a Field you would like to filter by
pick an operator — for example, is any of or is after
pick a value
Combine rules with and and or
Narrow down the selection even further by adding more rules
This Filter set demonstrates how multiple AND conditions narrow down the results. Each condition further restricts the dataset until only items matching all rules remain.
Quick (Pinned) filters
You can create Quick Filters in all top level views (Table, Board, Timeline, Calendar, List). To create a pinned filter, create a filter or a filter group and pin it.
There are two types of pinned filters:
Editable filters. In such filters a user can change values, like set state, set assignee, etc.
Filter Buttons. Here a user can just toggle this filter on and off. Note that for buttons you can combine several filters in a single group.
You can convert existing pinned filters (not groups) to editable filters. Click … near pinned filter and select Let users change filter value option.
You can also pin filters on relation and embedded Views. It may help to reduce amount of Views you create, but in relation views it will also increase visual noise, so use it carefully! You can also re-order filters (and pinned filters as a result). Just drag and drop a filter in Filters menu.
Notes:
Nest conditions with filter groups
For a complex combination of and and or, use filter groups.
Filter groups let you say “show me items that match this set of rules OR that other set of rules” instead of cramming everything into one flat filter.
Without groups, every condition would be forced into a single long AND/OR chain, which quickly becomes confusing or even impossible to express. Groups let you:
Mix AND and OR logic cleanly.
Separate different “scenarios” for when an item should be visible.
Keep complex filters more readable and maintainable.
In this example, there are two filter groups:
Group 1 (AND logic inside)
Group 2 (AND logic inside, wrapped with OR)
State is any of Ready for Dev, In Progress, Implemented
Release is not empty
→ This group selects items that are in one of the active workflow states and already have a Release assigned.
The groups are combined with an OR at the top level. That means the system will show:
Groups can be nested up to 3 levels deep. If you need more (we are impressed!), describe your use case in the community.
Set any relative value in Date Filter
When filtering by Date Field, you can choose from convenient preset options like "today," "yesterday," and "one week from now," or use the "custom date" option to select either specific dates or relative timeframes.
You have the freedom to combine absolute and relative dates at both ends of your date range, moving beyond simple preset ranges like "past week."
Here are some examples of what you can do:
Set a range from a specific date to another specific date (e.g., from January 1st → to January 15th)
Mix a specific date with a relative one (e.g., from January 1st → to 5 days ago)
Use relative dates on both ends (e.g., from 10 days ago → to 2 weeks from now)
Pro tip: Need to filter for today's data? Simply use "0 days ago" or "0 days from now" as your relative value.
Filter by related entities fields (relations)
You can filter Entities using fields from related databases. When setting up filters, you’ll see an > arrow next to relation fields, allowing you to access and filter by fields from the related database.
For example, if your Tasks database is connected to Teams, Epics, and Departments, you can now filter tasks using fields from any of these related databases.
You can also hide empty "No parent" groups (like "No Phase", "No Project", "No Status", etc.) when they contain zero items. Simply enable the "Hide Empty 'No...' Groups" toggle in the Filter tab in view settings to keep your views clean and focused on actual content. Empty sections will automatically reappear when you add items to them.
Filter by to-many relation count
You can filter directly by the count of items in a to-many relation. In filters, collections (like Bugs) now have a “Count” option, so you can set conditions such as: Bugs Count > 2
Nuances
Global vs. my filters on Views
On top of filters for everyone, you are free to add your own personal filters that won't affect other users looking at the same View:
Global and personal filters are combined with and.
Setting filter values for newly created Entities
When possible, we try to automatically set the appropriate values for newly created Entities based on filters.
The goal is to make sure the newly added card stays on the screen.
When determining values proves to be tricky (ex. when rules are combined with or), we skip this step. In this case, the card will disappear soon after creation.
For multi-selects filtered using is any of operator, we set all the values.
Filter per DB (+ columns and rows)
When cards of multiple DBs are present on the same View, you can specify custom filters for each DB independently:
In a similar way, you can configure filters for rows and columns.
Relative date filters
is on or after month ago
[Nov 7,… ) – so any future date is included as well.
is within the past month
(Nov 7, Dec 7]
If the day of the month on the original date is greater than the number of days in the final month, the day of the month will change to the last day in the final month.
"This month", "This week", "This year" filter
You can filter views by past/current/next week/month/quarter/year.