Model Change Logging

[felixrindt]

• tests
• Full-text-search in the FilterForm
• rename db_instance to be a copy of the instance from the post_init signal
• views
  • generic view
  • teaser on index page
• refactor json structure {str: ..., fields: [ {slug: ..., data: ...}, ... ]}
• refactor |linkify for get_absolute_url
• refactor object select
  • heterolog heavy select2
• view_logentry permission for managers?
• log group permissions

Ideas:

• clickable links to absolute urls -> doesn't really fit our needs
• diffs on large text changes -> difflib exists, but it's more work than I want to currently spend for the benefit.
• clicking an object link makes it the filter?! --> not useful enough

[coveralls]

Coverage increased (+0.6%) to 89.376% when pulling 1d00d6c on feature/logging into 074d9b0 on main.

[jeriox]

lgtm

[felixrindt]

We need to decide where to show the log and to whom.
Rendering the log requires - due to the architecture, a lot of queries.

• Events, Shifts and Participations are currently logged together. I propose a separate view visible to event responsibles where they can view the log.
• We can add logging to users (but not groups, sadly, as we can't access that model) as well, though I wouldn't show the log anywhere specifically. Instead
• We can create a View where you can filter logs based on content type, timeframe and acting user. Useful for support staff and managers(?)/staff users!

[jeriox]

We need to decide where to show the log and to whom.
Rendering the log requires - due to the architecture, a lot of queries.

* Events, Shifts and Participations are currently logged together. I propose a separate view visible to event responsibles where they can view the log.

sounds good

* We can add logging to users (but not groups, sadly, as we can't access that model) as well, though I wouldn't show the log anywhere specifically. Instead

* We can create a View where you can filter logs based on content type, timeframe and acting user. Useful for support staff and managers(?)/staff users!

also sounds good. I still like the idea of having a few of the latest actions on the homepage for managers with a link to the view that you just mentioned.