Monday, July 21, 2025
3 changes · master
Resolved issues and error corrections
The rental schedule’s “To Do Today” filter now correctly accounts for each user’s local timezone. This prevents rental orders from appearing on the wrong day for users outside UTC, improving day-to-day scheduling accuracy.
Original PR description
__Issue:__ The "To Do Today" filter used the user's local date to build a datetime range but treated it as if it were already in UTC. This caused incorrect filtering in non-UTC timezones __Fix:__ - Convert those datetimes to UTC using `.to_utc()` in the filter domain opw-4886069 Forward-Port-Of: odoo/enterprise#90358 Forward-Port-Of: odoo/enterprise#89718
Updates the Mexican DIOT report so it uses the latest report column references introduced by related accounting changes. This keeps DIOT tax reporting aligned with the corrected column logic and helps avoid incorrect or broken report values.
Original PR description
Description of the issue/feature this PR addresses: The language used in the DIOT documentation was confusing and even though we had the exact same description for two columns it turns out they were…
Description of the issue/feature this PR addresses: The language used in the DIOT documentation was confusing and even though we had the exact same description for two columns it turns out they were different, so we need to change the logic of a few columns to make it work as needed. This issue was addressed in PR: https://github.com/odoo/odoo/pull/217441, but a small adjustment still needs to be made in the l10n_mx_reports module. Current behavior before PR: The l10n_mx_diot_get_values function uses references to the old account.report.expression that were removed in the pr mentioned above. Desired behavior after PR is merged: The l10n_mx_diot_get_values function uses the new references to account.report.expression that were introduced in the pr of the community repo. opw-[4920577](https://www.odoo.com/odoo/my-tasks/4920577) "I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr" Forward-Port-Of: odoo/enterprise#90119 Forward-Port-Of: odoo/enterprise#89481
This change updates the enterprise Discuss test setup so it includes HR-related data models needed during automated testing. It prevents a runbot crash in the AI composer test, helping keep validation pipelines reliable without changing end-user behavior.
Original PR description
Before this commit, recently added unit test "can handle command and disable mentions in AI composer" crashed on runbot with the following error message: ``` cannot find a definition for model…
Before this commit, recently added unit test "can handle command and disable mentions in AI composer" crashed on runbot with the following error message: ``` cannot find a definition for model "hr.employee": could not get model from server environment (did you forget to use `defineModels()?`) ``` Somehow the mock models in this test suite is aware of model "hr.employee". While this model exists with this module installed, the hoot suite in `test_discuss_full_enterprise` only imports mail models which hasn't `hr.employee`, thus we'd expect the suite to not be aware of this model and shouldn't attempt to load it. While we don't know why the hr.employee model definition is obtained on runbot on this test suite, functionally it makes sense to have this model installed. At the same time, we'd expect that the JS model definition are optional and just there in case we want to "cheat" model definition from the one fetched. This commit attempts to fix the issue by defining hr models rather than mail models in this test suite. Hr models have mail models in addition to hr models like hr.employee, thus we expect to fix the crash. Fixes runbot-error-230073 Forward-Port-Of: odoo/enterprise#90604