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

**URL:** <https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356>\
**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:** 1\
**Showing post:** 1

<div class="post-metadata">

**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")

</div>

## 😛 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.

---

_[View the full topic](https://community.fibery.io/t/february-5-2026-pinned-filters-where-users-can-change-values-previous-field-values-in-validation-rules/10356)._
