😛 February 5, 2026 / Pinned Filters where users can change values, Previous field values in validation rules

[mdubakov]

Pinned Filters where users can change values

Now when you create a pinned filter where users. can. change. filter. values. It works for all pinned filters in all views. It unfolds new opportunities for Architects to create Views with pre-setup empty filters. For example, you can let users filter by state, assignees, or other fields. We hope pinned filters with editable values will make your life a little bit easier.

Some important notes:

• Now you can create filters as buttons (old behavior) and filters as editable controls. In some cases buttons are still better, for example, when you want to on/off several conditions at once.
• You can convert existing pinned filters (not groups) to editable filters. Click … near pinned filter and select Let users change filter value option.
• So far it is not possible to pin Personal Filters (but it will be done in nearest future)

Fun fact. Initially we thought this feature is easy. Solution 1 failed. Solution 2 failed as well. Solution 3 got quite complex but we decided to implement it. And we did (and we spent 2 months). Before release we tested it internally and scrapped everything. Solution 4 is what you see right now (and we also spent 2 months on it). Sometimes software is just hard… This feature probably has the longest specification of all Fibery features. We will remember pinned filters forever and we did learn something.

Previous field values in validation rules

Validation rules just got more powerful! You can now access the previous value of a field when creating validation rules. This means you can enforce workflow transitions and maintain data integrity by validating not just where an entity is going, but where it came from.

For example:

• Prevent basic status transitions (Open → Closed): [Step 1 Feature (Previous)].State.Name = "Open" and [Step 1 Feature].State.Name = "Closed"
• Prevent status transitions unless certain conditions are met (e.g., a task can’t move from “In Progress” to “Done” unless someone is assigned): [Step 1 Feature (Previous)].State.Name = "In Progress" and [Step 1 Feature].State.Name = "Done" and [Step 1 Feature].Assignees.Count() = 0

When setting up a validation rule, you’ll see a new variable available: [Step 1 Feature (Previous)] (where “Feature” is your database name). This variable holds the values of the entity field before the current change was made.

So far we are stopping validation rules improvements and collecting feedback for the next steps later this year (maybe).

Integration & Import: specify display options for Number, Percent and Money fields

It’s now possible to specify more details for numerical data, when importing from CSV (or when integrating data from external sources). This includes being able to choose how the number will be interpreted and represented:

• number (integer or decimal, unit)
• money (integer or decimal, currency)
• percent (scaling)

Find these in the field setting dropdown and via the gear symbol.

Single-Click Copy Entity URL from Public ID

You can now instantly copy an entity’s direct URL with a single click on PublicID in Table, List, Board, and Timeline views.

Improvements

• UI: We added clear empty states to the Entity view when no fields are shown or some sections are empty. This helps explain why an Entity page may appear blank.
• Jira integration: Jira generates a lot of updates to and it affects performance and stability of integration. Now we’ve implemented delta-sync of issues to improve speed and reliability. Due to limitations of API delta sync works by downloading issues created or updated one day ago from last sync date.
• Documents: In the last release we introduced an option to disable Documents for the whole workspace. However, users still want to create them in Private space, so re-enabled Documents in Private even when Disable Documents is turned on.

Fixed Bugs

• Date Field: Wrong dates are set when typing date-time range from keyboard
• Rich Text: File upload silently fails if you navigate away (this one took us ~30 hours to fix… some bugs are very hard)
• Import: If a user tries to import a cell containing 1’234.00 CHF then it is not recognised as a number
• Entity history: Missing rule title and link to it from activity history
• Architect mode: It’s impossible to create Nested view for Documents in the User mode
• Forms:
  • Oops error when submit public form if required rich text is empty
  • Unable to set Default Value for Rich Text field

P.S. Feedback wanted. Improvement not-guaranteed.

[Eva_Folch]

@mdubakov

Pinned Filters where users can change values

AMAZING!!! Love this feature, totally worth it!

[Cddd]

@mdubakov

Pinned Filters where users can change values

Finally!!! Thank you so much!

[interr0bangr]

Great week, appreciate the improvements to Validation Rules and Pinned Filters.

Is there a plan to allow pinned filter groups to be handled in a similar way, where maybe the multiple fields would vertically stack?

@mdubakov

Integration & Import: specify display options for Number, Percent and Money fields

Could you please increase the number of characters for the unit labels? 5 is way too limiting, especially since often one of the characters usually needs to be an “s” to handle cases where there’s more than one unit. For example, instead of saying “months” we have to say either “mons” (weird) or “mnths” (also weird and ugly) or “month” (awkward since the value is usually > 1). We also use something called “points”, and have to either write it as “pts” (which some people don’t understand and interpret as “parts”) or “point” (again, awkward for plurals). Ideally there wouldn’t even be a limit, but even giving us 1 more character to work with would make such a difference and I assume would be super easy to do!

[timothy]

This is fantastic – it unlocks so many use cases we struggled with for user views!

[Jonathan1]

@mdubakov

Now you can create filters as buttons (old behavior) and filters as editable controls. In some cases buttons are still better, for example, when you want to on/off several conditions at once.

Was waiting for that, that’s excellent !

@mdubakov

Solution 4 is what you see right now (and we also spent 2 months on it).

That’s my personal opinion but I prefer to wait some weeks for a cool and very useful feature. I like the features you create every week but I would like to see Fibery grow in terms of options.

@mdubakov

Previous field values in validation rules

Small feedback, if you are interested, on Salesforce, it is named Prior (instead of Previous) which is shorter. I was also waiting for it for further projects, thanks.

[mdubakov]

@interr0bangr

Is there a plan to allow pinned filter groups to be handled in a similar way, where maybe the multiple fields would vertically stack?

No plans, it will complicate things and we don’t want to add such complexity.

[ccollins]

Really great release, thanks Fibery team!

@mdubakov

Pinned Filters where users can change values

Do you have plans to add relationship filters to these pinned filters?

A basic example: we have projects<tasks. On our task entity/views, when selecting assignees, we have it filtered to only show the people on that task’s project (around 5 users instead of the 58 users in the workspace). With the way this new feature works now, we have to scroll through the full 58 user list to find the 5 actual people for that project and the other 53 will always return nothing.

That’s just one basic example, but unfortunately with how our workspace is set up, I don’t think this feature will be very applicable without relation filters. Especially in situations where the relationship doesn’t have a unique name. Which is a shame because this is a very cool feature!

[christamae]

Unsure if this behavior is intended or a bug. If intended, can you explain?
I added the new quick filter for Team & left it empty on my Current Sprint Board view, because I want to currently see work across all teams. When I try to create a new item on that board, I receive an error that the Team value must be an array (even though my Team Field is allowed to be empty). See video for more.

[Pavel]

This is a bug, we indeed fail to create new card if there is an empty pinned filter, looking

[mdubakov]

@ccollins

Do you have plans to add relationship filters to these pinned filters?

We will think. Looks like not so easy task…

[Nathan_Arthur]

We’ve run into this too. (The thing where the page crashes if the user-selectable filter is empty, and you try to create a new entity.)

I also had a user report an issue that seems related: if they configure a user-selectable “any of” filter for a field with multiple values, then create a new entity, the new entity gets that field set to the first of the selected filter values.

Even if this isn’t new, it isn’t good behavior for us. It resulted in a regular ticket being marked as an “URGENT PRODUCTION ISSUE”.

[mdubakov]

@Nathan_Arthur

Even if this isn’t new, it isn’t good behavior for us. It resulted in a regular ticket being marked as an “URGENT PRODUCTION ISSUE”.

This is exactly how we are treating such issues

[mdubakov]

This problem should be fixed now

[chris.burchartz]

Great step forward guys

To bring it to good use, I would love to see these additional behaviours:

1. Filter & sorting within select field filters (like the standard fibery behaviour) → Example: We have a company-field with 500+ entries. We use this for a customer filter. there I only want to see active customers (12-15) but as for now I see a list of all 500 companies.
2. Custom name + icon: Using the Name of the field is unsatisfying - especially if the fieldname is very long. The standard behaviour of pinned filters would be great here.
3. With select fields one can’t see the field values, as the name is already to long.

All 3 things reduce the overall UX quite strongly, as clarity and focus are reduced a lot

Additional extra bonus thingy: Having the ability to combine AND with OR pinned-filters Quite often we need different filtering approaches within the same data set. At the moment we need to settle for AND or OR for all pinned filters (I know: UI and UX will be tough - but worth the time in my opinion)

Keep up the good work!
Chris

[chris.burchartz]

one more thing regarding the great validation topic:
I love the flexibility that comes with using formulas.
I would love to see this for the error message as well! No static message but a formula to render a custom message with context!

[Jonathan1]

@mdubakov

Pinned Filters where users can change values

Small idea to improve the UX of this feature : it should be cool to be able to hide the field name when a value is selected. And also that it takes the color and icon of the value.

There’s an example :

I have a field called Severity. I would like that when I select High for example, the word Severity is any of disappear and the word High is shown with the background red (and the icon if one is selected for this value).

[mdubakov]

@Jonathan1 @chris.burchartz all ideas are good, we will think.

[Nathan_Arthur]

I think I found another bug that’s probably due to the new filter behavior. The sequence of events is:

1. Go to a view
2. Click Filter
3. Add a filter row
4. Choose a field, leave it as “any of”, but don’t choose a value
5. Click the pin. The filter appears at the top of the page.
6. Click the … and choose “Let users change…”. The filter disappears from the top of the page.

(And if you’re me, do this for literally 6 filters, then discover that all your filters are gone! And gone from the Filter dropdown!)

A workaround is to click the pin twice more, before you close the filter dropdown, to turn it off and on again. That seems to put it in a good state.

Note that I was doing this because these user-selectable filters enable a great new feature - I made a table for Work Items, with all the common fields, and then added all the common filter fields to the top as user-selectable filters. I called it “Work Item Report”. Now any user can go there to do essentially-arbitrary filtering (or searching) of Work Items, by any values.