Hi @Leon.
You can use trigger formulas and a “History” field to implement something like your idea for a field that tracks changes. The following trigger formula (when applied only on changes to a “Status” field) should keep a newline-separated history of all changes to the Status field with the date that the change was made. Feel free to tweak the formula to match your preferred formatting, or add/remove additional data.
old_values = value
new_value = $Status
if not old_values and not new_value:
return ""
return "{}\nChanged to {} on {}".format(
old_values, new_value or 'Blank', TODAY()).strip()
Grist does maintain some history of recent changes to tables. The ‘Document History’ link in the lower left corner of the Tools section has an activity tab that shows recent changes, but it’s not as searchable and not as well-suited for looking at older changes.
Looking ahead, would you say your use case would be better supported if Grist had a way to automatically create records in a table when a record in a different table is modified (say a separate History table that gets populated anytime a Status is modified)? Or is the trigger formula field closer to what you were looking for?
Regards,
George