# \#history **URL:** https://community.fibery.io/tag/history/9.md [Latest](https://community.fibery.io/latest.md) · [Categories](https://community.fibery.io/categories.md) · [Tags](https://community.fibery.io/tags.md) --- ## [See previous states of history, not only the changes made](https://community.fibery.io/t/see-previous-states-of-history-not-only-the-changes-made/11318)
**Author:** [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Replies:** 14\ **Last updated:** [October 1, 2026, 9:35pm UTC](https://community.fibery.io/t/see-previous-states-of-history-not-only-the-changes-made/11318 "2026-10-01T21:35:06Z")
There has been a lot of work recently on the historical data of things. (Automations and views activity). The problem is that this list shows the changes, and you can see details of each change, but it is very difficult… --- ## [Don't have field creation/deletion affect modification date](https://community.fibery.io/t/dont-have-field-creation-deletion-affect-modification-date/10713)
**Author:** [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Replies:** 1\ **Last updated:** [April 7, 2026, 2:03pm UTC](https://community.fibery.io/t/dont-have-field-creation-deletion-affect-modification-date/10713 "2026-04-07T14:03:29Z")
For our task database, individuals and departments have views to track their tasks. This includes showing tasks that are not “Done” (state field), or the modification date is on or later than one week ago. However, I rec… --- ## [\[UI/UX\] History & Audit Log - Filter Out/Exclude e.g. Enum Databases](https://community.fibery.io/t/ui-ux-history-audit-log-filter-out-exclude-e-g-enum-databases/10649)
**Author:** [@Sev](https://community.fibery.io/u/Sev)\ **Replies:** 0\ **Last updated:** [March 26, 2026, 4:07pm UTC](https://community.fibery.io/t/ui-ux-history-audit-log-filter-out-exclude-e-g-enum-databases/10649 "2026-03-26T16:07:56Z")
It would be wonderful to be able to filter out i.e. exclude databases or maybe even other field values in the history log, since something like an select/enum field change can easily cause three entries in the log for th… --- ## [Find maximum historical value of a Number Field (script)](https://community.fibery.io/t/find-maximum-historical-value-of-a-number-field-script/10621)
**Author:** [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Replies:** 0\ **Last updated:** [March 23, 2026, 10:56am UTC](https://community.fibery.io/t/find-maximum-historical-value-of-a-number-field-script/10621 "2026-03-23T10:56:06Z")
Okay, so we’ve got a bit carried away after this :sweat\_smile:: Here’s another challenge solved in the same way — by creating a script working with our newly introduced History API. Problem to solve For each entity i… --- ## [Find when a Number Field value crossed a threshold via History API (script)](https://community.fibery.io/t/find-when-a-number-field-value-crossed-a-threshold-via-history-api-script/10618)
**Author:** [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Replies:** 0\ **Last updated:** [March 23, 2026, 7:50am UTC](https://community.fibery.io/t/find-when-a-number-field-value-crossed-a-threshold-via-history-api-script/10618 "2026-03-23T07:50:30Z")
With the recent introduction of History API, we were able to solve a problem deemed too messy to solve before. I thought we might as well share the solution in case anyone faces a similar challenge. Problem to solve For… --- ## ["Time Machine" (Version History) for Databases](https://community.fibery.io/t/time-machine-version-history-for-databases/10554)
**Author:** [@ID.000](https://community.fibery.io/u/ID.000)\ **Replies:** 6\ **Last updated:** [March 16, 2026, 1:09pm UTC](https://community.fibery.io/t/time-machine-version-history-for-databases/10554 "2026-03-16T13:09:52Z")
Hi Fibery team! Here is a “food for thought” suggestion regarding data safety and UX. In Google Sheets, we have Version History, which allows us to instantly see and restore the state of the entire document at any speci… --- ## [Differentiate visually new comments in rich text field version history](https://community.fibery.io/t/differentiate-visually-new-comments-in-rich-text-field-version-history/10487)
**Author:** [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Replies:** 0\ **Last updated:** [March 4, 2026, 9:47am UTC](https://community.fibery.io/t/differentiate-visually-new-comments-in-rich-text-field-version-history/10487 "2026-03-04T09:47:58Z")
When looking at the version history to track the changes, it sometimes seems like a version did not actually have any changes. After looking closely (and manually comparing with the previous version), I then identify tha… --- ## [Track changes between versions in rich text](https://community.fibery.io/t/track-changes-between-versions-in-rich-text/10486)
**Author:** [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Replies:** 0\ **Last updated:** [March 4, 2026, 9:41am UTC](https://community.fibery.io/t/track-changes-between-versions-in-rich-text/10486 "2026-03-04T09:41:01Z")
Some of our people have asked about being able to “track changes” in rich text. Not quite the same thing as versioning. They would like to be able to compare the state of the text now to the initial state. This is especi… --- ## ["Version history" of an entity](https://community.fibery.io/t/version-history-of-an-entity/9440)
**Author:** [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Replies:** 0\ **Last updated:** [August 22, 2025, 9:33am UTC](https://community.fibery.io/t/version-history-of-an-entity/9440 "2025-08-22T09:33:22Z")
Version history in rich text is very useful. But in entity activity, it tells us what changed when, but you need to manually imagine these changes moving backwards to understand how that entity looked at that point in ti… --- ## [Feature Request: Show "Timestamp" for Activity Log](https://community.fibery.io/t/feature-request-show-timestamp-for-activity-log/6482)
**Author:** [@Illusory](https://community.fibery.io/u/Illusory)\ **Replies:** 5\ **Last updated:** [August 8, 2024, 2:45pm UTC](https://community.fibery.io/t/feature-request-show-timestamp-for-activity-log/6482 "2024-08-08T14:45:48Z")
Hi there! For auditing purposes, the “When” column is nice but it would be helpful to see the actual timestamp that an event took place. Assuming When is just a converted timestamp, can we also add the timestamp as a col… --- ## [\[IN DEV\] Edits on documents don't show on log unless it's title](https://community.fibery.io/t/in-dev-edits-on-documents-dont-show-on-log-unless-its-title/5742)
**Author:** [@Jose\_Quesada](https://community.fibery.io/u/Jose_Quesada)\ **Replies:** 2\ **Last updated:** [January 24, 2024, 5:52pm UTC](https://community.fibery.io/t/in-dev-edits-on-documents-dont-show-on-log-unless-its-title/5742 "2024-01-24T17:52:39Z")
We have a doc-based workflow (ie no databases, no structured information, only a graph of docs pointing to each other – shared brain. I would love to look at the log and see what has changed in a space. Unfortunately, d… --- ## [Activity Stream](https://community.fibery.io/t/activity-stream/109)
**Author:** [@Shafqat\_Ullah](https://community.fibery.io/u/Shafqat_Ullah)\ **Replies:** 5\ **Last updated:** [August 2, 2023, 10:17am UTC](https://community.fibery.io/t/activity-stream/109 "2023-08-02T10:17:54Z")
A dedicated page for all key user activities aggregated from user selectable “spaces”. What type of activities get listed can be configurable. Any @mentions should be highlighted too in this activity feed. --- ## [Entity Snapshots (named versioning)](https://community.fibery.io/t/entity-snapshots-named-versioning/2462)
**Author:** [@cannibalflea](https://community.fibery.io/u/cannibalflea)\ **Replies:** 3\ **Last updated:** [February 1, 2022, 5:21pm UTC](https://community.fibery.io/t/entity-snapshots-named-versioning/2462 "2022-02-01T17:21:37Z")
I know the issue of versioning (and named versioning) has been discussed extensively in the community and the feeling is that with rich text versioning (which is really great) and the audit log for the entity fields, not… --- ## [Versioning in Rich Text Fields (and entities as a whole, too)](https://community.fibery.io/t/versioning-in-rich-text-fields-and-entities-as-a-whole-too/260)
**Author:** [@Shafqat\_Ullah](https://community.fibery.io/u/Shafqat_Ullah)\ **Replies:** 21\ **Last updated:** [July 30, 2021, 10:54pm UTC](https://community.fibery.io/t/versioning-in-rich-text-fields-and-entities-as-a-whole-too/260 "2021-07-30T22:54:06Z")
Hi, I think versioning in general is an important feature and versioning of each entity as a whole is not only useful, it is a requirement in certain compliance context. To begin with, the rich text fields should have … --- ## [Named Versions in Docs and Rich-Text Field History](https://community.fibery.io/t/named-versions-in-docs-and-rich-text-field-history/1856)
**Author:** [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Replies:** 0\ **Last updated:** [July 30, 2021, 2:55pm UTC](https://community.fibery.io/t/named-versions-in-docs-and-rich-text-field-history/1856 "2021-07-30T14:55:51Z")
Sometimes it is useful to add Named Versions to quickly find them later and see the changes.