# šŸ˜› February 5, 2026 / Pinned Filters where users can change values, Previous field values in validation rules **URL:** \ **Category:** Changelog\ **Created:** [February 5, 2026, 2:16pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356 "2026-02-05T14:16:21Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 5, 2026, 2:16pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/1 "2026-02-05T14:16:21Z")
## šŸ˜› 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](https://www.youtube.com/shorts/fBoqMMPoU9k). ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0c5a5c44b499bd92727064d7e6ec600494ba8597.png) ## šŸ¦– Previous field values in validation rules [Validation rules](https://the.fibery.io/@public/User_Guide/Guide/Validation-rules-456) 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. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/14c47c9a5735a1a0bc932a31946dbce778535257.png) 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 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/ff14653305c64ff82a2391b13dd331eaabd9add6.png) 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. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/cc342cf3ed1a3aacc277dc5c18ef06a158b92321.png) ## šŸ¦‹ 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. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 5, 2026, 2:16pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/2 "2026-02-05T14:16:29Z")
---
**Author:** ![Eva\_Folch](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eva_folch/32/11814_2.png) [@Eva\_Folch](https://community.fibery.io/u/Eva_Folch)\ **Post date:** [February 5, 2026, 2:47pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/3 "2026-02-05T14:47:03Z")
> [@mdubakov](#): > > Pinned Filters where users can change values AMAZING!!! Love this feature, totally worth it! ---
**Author:** ![Cddd](https://avatars.discourse-cdn.com/v4/letter/c/b38774/32.png) [@Cddd](https://community.fibery.io/u/Cddd)\ **Post date:** [February 5, 2026, 2:50pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/4 "2026-02-05T14:50:06Z")
> [@mdubakov](#): > > Pinned Filters where users can change values Finally!!! Thank you so much! ---
**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:** [February 5, 2026, 2:57pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/5 "2026-02-05T14:57:01Z")
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?](https://community.fibery.io/t/remove-or-at-least-increase-unit-label-character-limits/5849) 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! ---
**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\ **Post date:** [February 5, 2026, 2:59pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/6 "2026-02-05T14:59:05Z")
This is fantastic ā€“ it unlocks so many use cases we struggled with for user views! ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [February 5, 2026, 3:17pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/7 "2026-02-05T15:17:45Z")
> [@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. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 5, 2026, 3:35pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/8 "2026-02-05T15:35:49Z")
> [@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. ---
**Author:** ![ccollins](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@ccollins](https://community.fibery.io/u/ccollins)\ **Post date:** [February 5, 2026, 3:47pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/9 "2026-02-05T15:47:08Z")
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\ **Author:** ![christamae](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/christamae/32/13729_2.png) [@christamae](https://community.fibery.io/u/christamae)\ **Post date:** [February 5, 2026, 4:13pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/10 "2026-02-05T16:13:24Z") 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. ---
**Author:** ![Pavel](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/pavel/32/3903_2.png) [@Pavel](https://community.fibery.io/u/Pavel)\ **Post date:** [February 5, 2026, 5:22pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/11 "2026-02-05T17:22:58Z")
This is a bug, we indeed fail to create new card if there is an empty pinned filter, looking ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 5, 2026, 6:13pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/12 "2026-02-05T18:13:44Z")
> [@ccollins](#): > > Do you have plans to add relationship filters to these pinned filters? We will think. Looks like not so easy taskā€¦ ---
**Author:** ![Nathan\_Arthur](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nathan_arthur/32/13677_2.png) [@Nathan\_Arthur](https://community.fibery.io/u/Nathan_Arthur)\ **Post date:** [February 5, 2026, 6:42pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/13 "2026-02-05T18:42:07Z")
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ā€. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 5, 2026, 8:38pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/14 "2026-02-05T20:38:20Z")
> [@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 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 5, 2026, 8:57pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/15 "2026-02-05T20:57:13Z")
This problem should be fixed now ---
**Author:** ![chris.burchartz](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chris.burchartz/32/662_2.png) [@chris.burchartz](https://community.fibery.io/u/chris.burchartz)\ **Post date:** [February 6, 2026, 6:21am UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/16 "2026-02-06T06:21:58Z")
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 ---
**Author:** ![chris.burchartz](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chris.burchartz/32/662_2.png) [@chris.burchartz](https://community.fibery.io/u/chris.burchartz)\ **Post date:** [February 6, 2026, 6:24am UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/17 "2026-02-06T06:24:47Z")
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! ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [February 6, 2026, 7:32am UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/18 "2026-02-06T07:32:13Z")
> [@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 : ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/cec401df82dcfef6878533d578a6b269d5d7ae49.png) 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)_. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 6, 2026, 7:42am UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/19 "2026-02-06T07:42:56Z")
@Jonathan1 @chris.burchartz all ideas are good, we will think. ---
**Author:** ![Nathan\_Arthur](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nathan_arthur/32/13677_2.png) [@Nathan\_Arthur](https://community.fibery.io/u/Nathan_Arthur)\ **Post date:** [February 6, 2026, 7:04pm UTC](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356/20 "2026-02-06T19:04:59Z")
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. [Next page](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356.md?page=2)