ModelTracker VS django-lifecycle

For that, we created django-model-tracker a Django application that handle tracking Django Models changes with the username of the user who did the change, then the admin team can view the changes and restore the object to an older state.

You could use lifecycle hooks to only trigger the function on certain column updates https://rsinger86.github.io/django-lifecycle/

Even better alternative to signals, IMO, is lifecycle hooks

I've just came across Django Lifecycle Hooks (Recommended by a fellow Redditor) and I want to use it in my site.

To track each order status, we used django-lifecycle package. Whenever the status changes, it triggers the hook and status log is created.

You may want to look at django lifecycle hooks which has a really simple and powerful API for models: https://rsinger86.github.io/django-lifecycle/

If it's bind to saving to database, you have different options like overriding Model.save(), signals, and django-lifecycle.

Several replies mention django signals. That's an option, but a similar tool that provides a much clearer/cleaner implementation is django-lifecycle.

Note, my solution uses django-lifecycle and here is their documentation

The package is still in beta for now but it's already working pretty well. You can learn more and try by yourself here: https://rsinger86.github.io/django-lifecycle/