Daily updates from Odoo
Monday, September 23, 2024
11 changes · master
Resolved issues and error corrections
The WhatsApp channel member list now matches the updated styling used for other channel member categories. This keeps the interface visually consistent and easier for users to scan when managing or reviewing WhatsApp conversations.
Original PR description
This PR [1] changed the styling of Channel Member list categories. This commit aims to adapt these changes for WA User Category.   [1]: https://github.com/odoo/odoo/pull/178865 https://github.com/odoo/odoo/pull/181046
Fixed an error that occurred when opening the depreciation schedule for companies using multi-ledgers. This ensures asset depreciation reports remain accessible even when ledger journal groups are included in the report options.
Original PR description
steps to reproduce: - create a multi-ledger, no excluded journals needed - open the depreciation schedule => traceback Reason of the issue: in the options['journals'], multiple models can be present, for example 'account.journal' or 'account.journal.group'. Since this commit https://github.com/odoo/enterprise/commit/a98652896daf5b9f6078a0bf95dd1b1430f01e1a, which significantly improved the multi-ledgers, it the 'journals' with model 'account.journal.group' no longer have the 'selected' attribute as it doesn't make sense.
Fixes an issue where quotation calculators could fail or load the wrong sales order lines when synced fields targeted positions above the first line. Saving from the spreadsheet is now more reliable and avoids unnecessary reloading when all line positions are already available.
Financial budget screens now use clearer wording when creating a budget, avoiding the impression that a new budget is needed every year. The “Show All Accounts” option has also been moved into the budget filter and only appears when it can actually be used, reducing confusion for users.
Original PR description
This commit addresses two issues: 1) The placeholder allowing the creation of a new budget was mentioning 2025 as an example. It was misleading, and a leftover from the first version of the feature: no need to create one new budget per year ; the same object should be reused. 2) The "Show All Accounts" filter was displayed under the extra options filter, and was always shown. Though, clicking it had no effect at all when no budget was selected (in the budget filter). We now put this menuitem directly into the budget filter dropdown, and only display it when at least one budget is selected.
The TDS-TCS report setup for India has been moved into its own supporting module so it is only installed when the related withholding feature is present. This prevents reporting issues for companies that do not use Indian withholding, while keeping TDS-TCS reporting available automatically for those that do.
Original PR description
Before this PR, TDS-TCS functionality was managed in `l10n_in_withholding`, while the TDS-TCS report handler was in `l10n_in_reports`. This caused issues when `l10n_in_withholding` was not installed. To fix this, the report handler has been moved from `l10n_in_reports` to a new module, `l10n_in_reports_tds_tcs`, which is now set to auto-install with `l10n_in_withholding`. task-4037680 Related PR: https://github.com/odoo/odoo/pull/180862
Fixed an issue in the Barcode app where scanning a non-GS1 product barcode together with multiple serial numbers could cause an error when GS1 nomenclature was enabled. This helps warehouse users continue receipt operations smoothly and prevents stuck scan counts on screen after failed parsing.
Original PR description
How to reproduce ================ - Create a product tracked by SN and set a barcode (ex.: productserial1) - Select the Default GS1 Nomenclature in the Inventory Settings - Open the Barcode App > Operations > Receipts > New - Scan a barcode containing the created product's barcode and multiple serial numbers (eg.: 'productserial1,sn1,sn2,sn3,sn4') --> Traceback. Cause of the issue ================== There is two issues: 1. The parser throws an error if it tries to parse a barcode with the GS1 nomenclature and fails and this error wasn't handle bv the BarcodeObject when it parses its barcode. 2. If the BarcodeObject wasn't parsed and has no missing record, it wasn't processed and the barcode's count stay on the screen.
Fixed a crash that occurred when opening the Depreciation Schedule while a multi-ledger journal group was configured. The report now correctly ignores grouping headers and only processes actual journals, improving reliability for finance users.
Original PR description
To reproduce
1) Create a Journal Group (the menu item is now called "multi-ledger") 2) Open the Depreciation Schedule
==> Crash
This happens because the report parses the options['journals'] list badly, considering all elements in it have a 'selected' key. This is not the case when a journal group is defined, as a header element is then added, without that key. We fix it by checking the model associated with the elements of the filter, to only consider real journals, which are guaranteed to have a 'selected' key.Appointment names in the kanban view now include a hover title when the visible text is shortened. This helps users read the full appointment name without opening the record or guessing from truncated text.
Original PR description
This commit is a followup of task~3992107. It correctly sets the title attribute on the appointment name, which might be truncated. Setting `t-att-title` on a char field doesn't work, so it must be set on a wrapping node instead.
This fix removes unnecessary behind-the-scenes logic for a tax price setting that users cannot edit directly. It helps avoid confusing or inconsistent behavior when tax-included prices are derived from company settings and overrides.
Original PR description
As users can not modify directly the `price_include` field, there is no need for an inverse. Also doing a reverse of that field does not make much sense as it is the combination of the `company_price_include` and `price_include_override`. Community PR: odoo/odoo#178571 task-4144792
The subscription Kanban view now displays the health indicator with proper alignment. This minor visual fix makes subscription cards easier to read and keeps the interface looking consistent.
Original PR description
**Before this commit:** Health is not aligned properly in the Kanban view. **After this commit:** It should aligned properly.
Resource-based appointments booked online now show correctly in the Gantt planning view. This prevents missed bookings in operational schedules by removing an inappropriate privacy check for events that are tied to resources rather than individual users.
Original PR description
Purpose ======= Fix the resource events which weren't displayed in the gantt view when booked from the front-end. Specification ============= When an appointment based on resources is booked from the front-end, the event "user_id" field is set to be OdooBot. This is an issue as the read_group domain for the calendar.event model checks the user_id 'res_users_settings_id' field for privacy purpose but OdooBot doesn't have any users settings. => The read_group domain is always evaluated to False. No resource based events booked from the front-end are displayed on the gantt view. Fixing that by updating the privacy domain to be sure every events related to a resource can now be visible and accessible on the gantt view. The privacy field of an event is mainly related to the user settings but resource events aren't typically linked to any user meaning their visibility shouldn't depend on the privacy. Task-4191434