-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[18.0][MIG] tracking_manager: Migration to 18.0 #3238
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
Conversation
- remove tracking_model (less model, less code, less issue) - add automatic rule for default config (this avoid missing tracked field after module installation)
For example on the product if you open the 'stock.putaway.rule' you have activated the tracking on putaway_rule_ids change on rule should be posted on the related product
- track m2m simplify using native mail_thread and process them like text - simplify code for track one2many - avoid useless code on model not impacted by the tracking
Instead of complexe tracking throught the context just track change and process the message at the end using the precommit feature (the message are posted just before commiting)
Co-authored-by: Yoshi Tashiro (Quartile) <[email protected]>
Currently translated at 100.0% (25 of 25 strings) Translation: server-tools-17.0/server-tools-17.0-tracking_manager Translate-URL: https://translation.odoo-community.org/projects/server-tools-17-0/server-tools-17-0-tracking_manager/it/
Currently translated at 100.0% (25 of 25 strings) Translation: server-tools-17.0/server-tools-17.0-tracking_manager Translate-URL: https://translation.odoo-community.org/projects/server-tools-17-0/server-tools-17-0-tracking_manager/zh_CN/
Previously the bank_ids field was used but account adds messages in partner when a related bank account is created/modified/deleted, causing tests to fail. The user_ids field of res.partner is now used to avoid the side effect in tests and the fake model is removed. TT50571
…subscribed to notes Example use case: - Enable custom tracking in project.project - Activate the task_ids field as custom tracking - Create a project and assign it to a user (different from ours) and make it a note follower - Create a task in the project - The project message of the task tracking task will not be sent to the note followers TT50676
…child_ids of res.partner) Example use case: - Define the child_ids field of res.partner as tracking. - Modify contact Brandon Freeman and leave parent_id empty (Azure Interior) - No error should be displayed TT51146
…ld that we do not have access Example use case: - Install hr_fleet - Set the employee_ids field of hr.employee as a tracking field - Modify the user to not have permissions in Fleet - Modify the name of an employee TT51160 [FIX] tracking_manager: Test compatibility Related to OCA@b41e7ae Do not set the child_ids field as tracking in the setup to avoid incorrect data in some cases TT51160
Related to odoo/odoo@cac20c5 Now it is necessary to have an ir.actions.act_window record
d32831b
to
f1c3ce0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
functional & code review: LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested in Runboat and works as intended, Code LGTM
This PR has the |
f1c3ce0
to
39f6949
Compare
@pedrobaeza could you review/merge? |
/ocabot migration tracking_manager |
What a great day to merge this nice PR. Let's do it! |
@pedrobaeza The merge process could not be finalized, because command
|
/ocabot merge nobump |
On my way to merge this fine PR! |
Congratulations, your PR was merged at 8c5ea46. Thanks a lot for contributing to OCA. ❤️ |
supersede: #3138