[V17] - tracking_manager Is not showing many2many field changes properly

[Marrieta99]

Module

tracking_manager

Describe the bug

Once tracking_manager is installed in my database, relational field changes in every model are shown as "None -> None" regardless of what change was made

To Reproduce

Affected versions:
V17

Steps to reproduce the behavior:

1. Install tracking_manager module.
2. Modify a many2many field that is tracked by default (model does not even have active_custom_tracking set)
3. Field changes are shown like this in the chatter
   
4. This also happens with models that have active_custom_tracking set as True. Previous or current values of tracked many2many fields don't show.

Expected behavior
Previous and current value of the field should be displayed, as shown here

Additional context
I have encountered this issue in te V17 enterprise version

[melissalateb]

Hi, I installed the tracking_manager module in Odoo 17, and I'm still encountering the same issue described here.

Changes to tracked Many2Many fields are still displayed as "None -> None" in the chatter, even after updating my database.

Could you confirm if this issue has been fixed? If so, could you guide me on what might be missing in my setup?

Thank you in advance for your help!

[Marrieta99]

Did you have the module installed in your database when the bug was introduced, or did you install it after it was solved?
I am currently on Commit 9ecb5cd of the 17.0 branch of the server-tools repo (31 Dec 2024 17:25) and the bug appears to not be present anymore.
To update the older version of this module I pulled the changes from the GitHub repo, uploaded the updated code to my hosted Odoo database and then manually updated the module itself in there

[melissalateb]

I downloaded it from the Odoo Community shop app OCA in V17 https://odoo-community.org/shop/tracking-manager-12250, but after checking, the link is probably not up to date. I just cloned the latest version, and it works perfectly for this part, thank you! :)

Also, I opened an issue on another topic for the same module: #3165