-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comply with GDPR by creating an audit trail #63
Comments
Perhaps, best is to support this in the product for compliance with all sorts of rules and regulations, as the issue occasionally comes up. |
I was thinking that as well. The next question is: for the sake of code maintainability, does it make sense to introduce an ORM, so we can do audit trail in one place? |
What exactly are you suggesting? An additional audit log table where everything goes, when enabled? |
Yes. I propose it to be as simple as possible, with these fields:
we can than calculate differences for each change on the fly if needed (by iterating through objects properties) - for displaying to the user. What do you think? I would prefer to have some kind of ORM, so this can be implemented to work "automagically", but it would be big enough task as it is, and maybe we move this to "phase 2". |
How about simply having created, created_by, created_ip, modified, modified_by, modified_ip fields for all entities in sql tables that matter (similarly to what we have in tt_groups, tt_users, and tt_log now). This looks pretty straightforward and does not over-complicate things.
|
Hi, sorry for the late reply. Sadly this is not enough. We've checked out some options and I implemented a rudimentary support a while ago but did not create a merge request because feature is not finished. You can check the changes here: https://github.com/avidenic/timetracker/tree/audit_log When I find the time I will finish it - add UI, settings etc.... |
According to GDPR there should be an audit trail of actions performed on records (create, update, delete).
Revision trail must save data about:
The question that presents itself is: is it a good idea to do it in code, or install one of mysql logging plugins?
I would avoid triggers, but that is just my personal preference.
The text was updated successfully, but these errors were encountered: