Skip to content

[19.0][MIG] tracking_manager: Migration to 19.0 - #3596

Merged
OCA-git-bot merged 37 commits into
OCA:19.0from
c4a8-odoo:copilot/migrate-tracking-manager-18-0-to-19-0
May 20, 2026
Merged

[19.0][MIG] tracking_manager: Migration to 19.0#3596
OCA-git-bot merged 37 commits into
OCA:19.0from
c4a8-odoo:copilot/migrate-tracking-manager-18-0-to-19-0

Conversation

@CRogos

@CRogos CRogos commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

supersede #3470

@apik-mgu could you review

Kev-Roche and others added 30 commits April 13, 2026 18:50
- 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) <tashiro@quartile.co>
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
Copilot AI pushed a commit to c4a8-odoo/module-oca-server-tools that referenced this pull request Apr 16, 2026
Add tracking_manager module (migrated from 18.0 to 19.0) as a local
dependency for tracking_manager_domain. This avoids needing an
unreleased git URL in test-requirements.txt.

tracking_manager is the upstream module for tracking_manager_domain and
is being contributed upstream to OCA/server-tools as PR OCA#3596.

Co-authored-by: CRogos <1799080+CRogos@users.noreply.github.com>
@CRogos

CRogos commented Apr 29, 2026

Copy link
Copy Markdown
Contributor Author

@cuongnmtm , @NICO-SOLUTIONS could you review?

@cuongnmtm cuongnmtm left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review LGTM

@MohamedOsman7 MohamedOsman7 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code & functional review LGTM

@OCA-git-bot

Copy link
Copy Markdown
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@CRogos

CRogos commented May 19, 2026

Copy link
Copy Markdown
Contributor Author

@pedrobaeza could you merge?

@pedrobaeza

Copy link
Copy Markdown
Member

/ocabot migration tracking_manager

The commit history is not OK, as the migration commit re-adds files that were previously deleted. Please check.

@OCA-git-bot OCA-git-bot added this to the 19.0 milestone May 20, 2026
@OCA-git-bot OCA-git-bot mentioned this pull request May 20, 2026
43 tasks
@CRogos

CRogos commented May 20, 2026

Copy link
Copy Markdown
Contributor Author

The commit history is not OK, as the migration commit re-adds files that were previously deleted. Please check.

@pedrobaeza Sorry I don't get which files you are referring? The migration commit reverts most of the changes of the previous commit (keeps the tests), but does not add any files? Should I remove this commit instead of reverting the changes in the migration commit?

image

@pedrobaeza

Copy link
Copy Markdown
Member

Oh, sorry, my fault. I saw the commit content badly.

/ocabot merge nobump

@OCA-git-bot

Copy link
Copy Markdown
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 19.0-ocabot-merge-pr-3596-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot
OCA-git-bot merged commit 225d75e into OCA:19.0 May 20, 2026
7 checks passed
@OCA-git-bot

Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at 8f452c7. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.