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 the same action, e.g. if changing the status of “Task X” in the Work space from “in-progress” to “done”, it shows:
- DB of Status_Work/Tasks “in-progress” removed “Task X” from “Entities”
- DB of Status_Work/Tasks “done” added “Task X” to “Entities”
- DB of Work/Tasks “Status” changed from “in-progress” to “done”
The above is perfect for an audit log, but:
Request 1 Exclude/Include Enum DBs
Most of the time a user needs to see the actual change and does not care about the background workings of the system, in which case it would be nice to be able to exclude all internal enum type databases, since doing this manually is quite a chore to keep up to date. There clearly is a flag that distinguishes these databases from actual architect-created databases, because the former is not even accessible with the properly encoded url, e.g. .../fibery/space/Work/database/Status_Work/Tasks which tells me you have the internal flag to use in the log filters, too, hopefully.
Request 2 Allow “is none of”
This will just expand the possibilites of filtering out things.