Friday, November 3, 2023
16 changes · 17.0
Resolved issues and error corrections
This fixes an error that occurred in Field Service planning when users grouped planning entries by project. The change makes project grouping work reliably, avoiding an interruption in planning workflows.
Original PR description
Steps: - Open Field service - Select planning then by user - Group by project - The trace back is coming Issue: - when we trying to group by projects the trace back is raised. Cause: - In '_search_on_comodel' method filtered_domain does't set perfectly, The filtered_domain it is not set for the additional_domain , when we given on additional_domain, on that time filter_domain does not consider the additional_domain, because of that traceback will be coming. Fix: - By adding an 'if' condition for cases when you provide an additional domain, it will work fine. task-3522178 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website header templates no longer force certain preset styling choices, such as uncolored social icons or rounded call-to-action buttons. This lets users' selected header options remain in place after saving, improving consistency between the editor and the published website.
Original PR description
Since [this PR], some headers have some preselected options. For instance, by default the header_sales_one displays social icons without colors and a CTA button with rounded sides. However, if one modifies the option in the panel, it appears to be working, but upon save it goes back to no_icon_color / rounded sides. This happens because the option is forced by the header template. That behavior takes the precedence over the user's option choice. As there is no proper way to make it work without modifying the model, this commit removes the forced option on the templates for Odoo 17. It should be properly reintroduced in master. [this PR]: https://github.com/odoo/odoo/pull/119650 task-3576074
This fixes how website columns keep their intended order on mobile screens by using standard layout ordering rules. It also prevents mobile-only ordering from affecting email mass mailings, avoiding editor-window size from changing what recipients see.
Original PR description
This follows [commit 1], which introduced a way to separately reorder columns on mobile and desktop. This commit replaces the custom mobile order classes with the Bootstrap `.order-x` classes. It also ensures those orders are not used for mass mailing in case the editor composes their email on a small window. The reorder would indeed not have any effect for the end users in such a case. [commit 1]: https://github.com/odoo/odoo/commit/710d000f1872fd99b41d52ec3d6923756bba7cba task-3576046
The customer portal sales pages now display correctly when the reorder option is enabled. This prevents broken sidebars and improves spacing across related sales, delivery, timesheet, account, and website shop views, giving customers a cleaner ordering experience.
Original PR description
This PR solves some layout issues inside Portal, especially the `sale orders` page. If you activate the `reorder` option from the settings, there is an extra button that can appear in the portal layout. This button was not adapted with the portal redesign and would then break the layout. This PR fixes the layout issue while taking care of other small layout adjustments. Master | master-portal-fix-sale-order-layout-chgo :-------------------------:|:-------------------------:  |  task-3572209
Restaurant point of sale now correctly handles ordering the same combo product more than once at the same table. This prevents a second identical combo order from being missed, helping staff process customer orders reliably.
Original PR description
Step to reproduce: - Order a combo product in pos_restaurant - Order the same combo product for the same table - The second order will not be processed Previously the getOrderChanges method was computing the orderline changes based on a key composed of the product id, the full product name and the note. This was done considering the fact that the merge orderline was working. Combo products are not handled by the merge orderline. Because of this, if 2 orderlines of combo product were the same, only the last orderline would be taken into account. To prevent this, this commit changes the key to the uuid wich is a unique identifier to an orderline.
Manufacturing users can once again enter batch or serial numbers for tracked by-products directly from the manufacturing order view. This restores an important traceability step and helps keep production records accurate without extra workarounds.
Original PR description
From the backend manufacturing order view, it was no longer possible to specify batches/serial numbers for by-products. Now it is. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update refreshes Odoo's spreadsheet component with fixes for range selection, exported image sizing, row/header handling, collaboration display, and visual consistency. It also improves performance and adds spreadsheet functions and locale-aware date formatting, making spreadsheets faster and more reliable for daily business use.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/0887d5bb5 [REL] 17.0.1 https://github.com/odoo/o-spreadsheet/commit/88efb7049 [FIX] package: Export template file when…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/0887d5bb5 [REL] 17.0.1 https://github.com/odoo/o-spreadsheet/commit/88efb7049 [FIX] package: Export template file when publishing on npm https://github.com/odoo/o-spreadsheet/commit/0678b7058 [FIX] SelectionInput: Unable to select range after confirm Task: 3493185 https://github.com/odoo/o-spreadsheet/commit/d8d943bb3 [IMP] history: reduce memory allocation https://github.com/odoo/o-spreadsheet/commit/0170f5cad [IMP] range: order only if needed https://github.com/odoo/o-spreadsheet/commit/05da23cbe [IMP] actions: don't create actions at each rending https://github.com/odoo/o-spreadsheet/commit/1ce196dfb [IMP] viewport: find header with binary search https://github.com/odoo/o-spreadsheet/commit/bb668d1d9 [IMP] locale: change date format with locale Task: 3575516 https://github.com/odoo/o-spreadsheet/commit/cc08fcf00 [FIX] XLSX: Exported image dimension Task: / https://github.com/odoo/o-spreadsheet/commit/c0a34c295 [REL] 17.0 https://github.com/odoo/o-spreadsheet/commit/5080bc451 [REM] viewport: remove unused parameter https://github.com/odoo/o-spreadsheet/commit/07999834b [REM] viewport: remove always falsy condition https://github.com/odoo/o-spreadsheet/commit/f4583b226 [FIX] header_size: decouple added row from base row Task: 3510863 https://github.com/odoo/o-spreadsheet/commit/7be4d753f [FIX] evaluation: avoid .shift() https://github.com/odoo/o-spreadsheet/commit/83aba22d4 [FIX] top_bar: force white background https://github.com/odoo/o-spreadsheet/commit/f7fb70ee7 [IMP] headers: add header position UI plugin Task: 3563624 https://github.com/odoo/o-spreadsheet/commit/c58899b26 [IMP] selection: don't dispatch at `START` Task: 3563624 https://github.com/odoo/o-spreadsheet/commit/a4fe61669 [IMP] headers: add `getHeaderSize` getter Task: 3563624 https://github.com/odoo/o-spreadsheet/commit/2dd53005c [IMP] translations: Do not translate template strings Task: / https://github.com/odoo/o-spreadsheet/commit/18a08b1de [REL] 16.5.0-alpha.13 https://github.com/odoo/o-spreadsheet/commit/bb48a4eda [FIX] border_editor, top_bar: dark-mode adaptations Task: 3201038 https://github.com/odoo/o-spreadsheet/commit/5176308f4 [FIX] evaluation: fix evaluateFormula getter typing https://github.com/odoo/o-spreadsheet/commit/612f02623 [IMP] Functions: add SORT, SORTN and RANK Task: 3472980 https://github.com/odoo/o-spreadsheet/commit/ca56b0809 [FIX] Highlight: prevent default `mousedown` behaviour Task: / https://github.com/odoo/o-spreadsheet/commit/10a42a475 [REF] ClientTag: use t-if instead of opacity Task: / https://github.com/odoo/o-spreadsheet/commit/43692a6e5 [REF] tests: dispatch both input and change events https://github.com/odoo/o-spreadsheet/commit/8dae28aed [REF] chart_test: improve test speed/readability https://github.com/odoo/o-spreadsheet/commit/0f3b35682 [FIX] collaborative: display other users name
Point of Sale discounts now remain available when category limits are enabled, even if the discount product is outside the allowed sales categories. This prevents blocked discount actions and helps cashiers apply approved discounts consistently.
Original PR description
Before this fix, when using the limit categories option, if the discount product was not in those specific categories, you couldn't do any discount. With this fix, we load the discount product everytime the option is enabled. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now translate messages they wrote themselves, removing a confusing limitation where the translation option could be missing. Email message translations are also displayed correctly, making multilingual conversations easier to follow.
Original PR description
[FIX] mail: allow translating self authored messages [FIX] mail: show translations for emails
Fixed a technical error that occurred when users tried to group Field Service planning tasks by project. The system was incorrectly including all projects instead of only Field Service projects, causing the application to crash. This fix ensures the grouping feature works smoothly for Field Service users.
Original PR description
Steps: ---------------- - Open Field service - Select planning then by user - Group by project - The trace back is coming Issue: ---------- - when we trying to group by projects the trace back is raised Cause: --------- - By using of |= condition it collecting all the projects Fix: -- - Here by using of '|=' condition this will be collecting the all the projects,But actually we only fsm projects so we can use '&=' condition it will be helpfull for the getting only fsm projects task-3522178
This update fixes three visual and functional issues in the Account Reports carry over feature. The tooltip alignment has been corrected, styling has been added to the view button, and the popover now properly closes when navigating to the carry over details. These improvements enhance the user experience when reviewing financial carry over information.
Original PR description
In this commit, we made a few fixes on the carry over: - the tooltip was not aligned in the middle and was too far to the right. - the button for viewing the carry over lines in the popover had no css classes. - When clicking the button, the popover didn't close and stayed on the new page. task: 3438422 Forward-Port-Of: odoo/enterprise#49918
This fix addresses an issue where total lines in account reports were incorrectly inheriting page break settings from their section headers. When a section was configured to start on a new page, the total line would also start on a new page, which was not the intended behavior. This update separates the page break setting for section headers from total lines, ensuring reports display correctly.
Original PR description
When activating the "Total Below" section feature, the total line will adopt the attributes of the section line. More over, in the report settings we have the option to define a page break attribute for a line. Now if the section's line possesses the page break attribute, this causes the total line to also have it, which is not the desired behavior. This commit aims to separate the "Total Below" sections from the "print_on_new_page" field. task: 3566903 Forward-Port-Of: odoo/enterprise#49544
Fixed an issue where ordering multiple identical combo products in a restaurant would only display one item on the kitchen display instead of all of them. The system now properly tracks each order individually, ensuring kitchen staff see the complete list of items to prepare.
Original PR description
Step to reproduce: - Order two same combo products in pos_restaurent - Only one product will appear on the kitchen display Previously the _get_order_changes method was computing the orderline changes based on a key composed of the product id, the full product name and the note. This was done considering the fact that the merge orderline was working. Combo products are not handled by the merge orderline. Because of this, if 2 orderlines of combo product were the same, only the last orderline would be taken into account. To prevent this, this commit changes the key to the uuid which is a unique identifier to an orderline.
This update fixes how byproducts are handled in manufacturing work orders. Byproducts will now be visible to workers on the Shop Floor display, quality checks for byproducts will work correctly, and byproducts will be automatically marked as completed when a work order is finished—just like raw materials. This ensures better inventory accuracy and visibility for manufacturing operations.
Original PR description
Make quality checks to register byproducts effective. Show them in Shop Floor. Show workorder related byproducts in Shop Floor. Mark them as picked when marking workorder as done (like raw materials).
This fix resolves an issue where the representation fees calculation was trying to access a field that only exists when the Belgian contract salary module is installed. The functionality has been properly reorganized so that representation fees behavior is now correctly handled within the Belgian contract salary module, preventing errors when this module is not active.
Original PR description
Before correction : The function _get_representation_fees_threshold used a field from hr_job. But this field exist only if l10n_be_hr_contract_salary is installed After correction : Put the behaviour of this function linked to this field in l10n_be_hr_contract_salary.
The Aged Payable report was displaying confusing "0" values in the total column for individual transaction lines. This fix removes those misleading zeros and only shows totals for summary rows like partner totals and grand totals, making the report clearer and more accurate.
Original PR description
Current behavior before PR: In the Aged Payable report, the total column display the totals for every line. On move lines, the coluwn shows a "0" which does not make sense. --- Desired behavior after PR is merged: This commit makes it now so that there is no value displayed in that column for moves but only for total lines like partner lines or totals. Forward-Port-Of: odoo/enterprise#49763