Tuesday, March 10, 2026
6 changes · 17.0
Resolved issues and error corrections
This change resolves a test failure related to displaying budget information in project updates. The fix ensures that test users automatically receive the necessary permissions (`account.group_account_readonly`) to see budget details, regardless of whether the `account_accountant` module is installed. This prevents test failures and ensures accurate reporting.
Original PR description
Before: Test failed when only `project_account_budget` was installed because the user lacked `account.group_account_readonly`. Budget info in project update description requires this group, but it's only auto-assigned when `account_accountant` module is installed. After: Explicitly grant `account.group_account_readonly` to test user. This ensures budget information (spent/remaining percentages and amounts) is included in the project update description, regardless of whether `account_accountant` is installed. Note: No need in 18.0 as `account_accountant` gets installed automatically on installing `project_account_budget` Related PR: https://github.com/odoo/enterprise/pull/102126 runbot error: 241113
This update fixes an issue where timesheet descriptions were not correctly synchronized when updating values in the grid view. Specifically, when a timesheet cell was modified, a new line with the updated description was created, but it wasn't grouped with the original line. This change ensures that timesheet descriptions remain consistent across the grid view, improving data accuracy and usability.
Original PR description
To reproduce: ============= - on timesheet group by Project > Task > Description - on a line with a description, update a 0:00 cell to an other value - refresh or change view to list and back to grid - a new line with description '/' is created with the updated value Problem: ======== when creating the new timesheet it's by default given the name '/' which for the grid view is not in same group as the original line with the description. Solution: ========= when creating the new timesheet, we give it the same description as the original line. opw-5909249
This update clarifies Odoo's server logs during data imports by adding more specific information about which model the data was imported to. Previously, it was difficult to quickly identify the source of import logs, making troubleshooting support issues more time-consuming. This change improves the efficiency of our support team and overall data import process.
Original PR description
When investigating support tickets (and the server logs), it is not always clear if: 1) The `info`` log from base_import refers to a dry run or a "real" import 2) The "done" log does not explicitly specify which model the data was imported to While an experienced user can still extrapolate what happened by the immediate context of the preceding/following log lines, it makes it unnecessary difficult to see at first glance where the data was imported to. This PR aims at rectifying it to improve the quality of life of people investigating the server logs. OPW-5999195 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#252734
This update resolves a technical issue that caused a traceback when using the pivot table autofill feature. The fix corrects a misnamed function call, ensuring consistent behavior with vertical autofills. While the core functionality remains unchanged, this resolves a potential error and improves stability.
Original PR description
When autofilling a positional pivot row header horizontally, we would get a traceback because we were calling `_autofillPivotColHeader` instead of `_autofillPivotRowHeader`. Note that this fix only fixes the traceback, the result is not correct, but is consistent with autofilling a positional col header vertically. Task: [5909266](https://www.odoo.com/odoo/2328/tasks/5909266)
This update corrects an error in the documentation for a key Odoo date utility function. The original description was misleading, reflecting incorrect behavior. This change ensures the documentation accurately represents the function's purpose and improves clarity for developers.
Original PR description
Docstring was probably copied from `start_of` and not fixed up, so described the wrong semantics. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects an issue in the demo data for the MRR report on sale orders. The change ensures the report accurately reflects MRR calculations by setting an initial MRR value of 15 for the subscription_log_2 demo record in version 17.0, improving the demo's realism.
Original PR description
The MRR report on sale orders uses sale.order.log files to track changes in MRR over time. This demo data may be useful to show how the MRR report should look in a real database, as it is difficult to replicate historical logs functionally. In version 17.0, the sale order subscription_log_2 should have an initial MRR of 15.