Friday, February 7, 2025
15 changes · 18.0
Resolved issues and error corrections
Users in the Invoicing & Banks role can now access customer statements and partner ledger reports from partner records. This fixes a permissions gap so the new invoicing role can use the expected reporting tools without needing broader accounting access.
Original PR description
With the introduction of Invoicing Enterprise (access to bank recon etc) a new user group was created "Invoicing & Banks" (`group_account_basic`) This group should also be able to access the customer statement / partner ledger (from the partner smart button) Task-4465208
This fix restores behavior that prevents imported accounting lines from unexpectedly changing tax values. It helps businesses avoid incorrect tax handling when importing accounting data, reducing manual corrections and compliance risk.
Original PR description
[IMP] account - imported line shouldn't change tax Foward-port https://github.com/odoo/odoo/pull/193483 messed up and removed important code of https://github.com/odoo/odoo/pull/172787. This commit adds it back. task-4547597 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Changing font size on underlined or strikethrough text now applies the sizing to the full styled text rather than only wrapping the inner characters. This keeps the underline or strikethrough visually aligned with the resized text for a more consistent editor experience.
Original PR description
**Problem**: When `u` or `s` tags are applied, changing the `font-size` wraps the text inside these tags instead of applying it to the tags themselves. For example, `a<u>b</u>c` → `a<u><font>b</font></u>c`, which results in an inconsistent appearance. **Solution**: Ensure that the `span` for font size is applied to the highest non-block ancestor to maintain proper styling. **Steps to Reproduce**: 1. Add text. 2. Apply underline. 3. Increase font size. 4. Observe that the underline remains the original size instead of scaling with the text. opw-3086072 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Point of Sale login flow now correctly returns from the screensaver without treating it as the prior screen. This prevents staff from getting stuck seeing the screensaver during employee login after the terminal has been idle.
Original PR description
Before this commit, when the login screen was left idle using an employee login, the screensaver would appear as expected. However, upon user interaction (e.g., moving the mouse), the system would update the previous screen to the screen saver. This causing issues during login where the screensaver would be displayed. opw-4494087 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Point of Sale order screen now handles offline and slow connections more gracefully. Staff can continue viewing previously loaded orders instead of seeing a blank screen or getting stuck in repeated loading.
Original PR description
This fix prevent blank screen (when offline) & inifinte loop (when in 3G or other low connection) on order screen. - **Offline Mode:** When accessing the order screen offline, now the screen loads previously fetched orders and displays a "Limited Functionality" popup. - **Slow Connection (3G):** Infinite loop (caused by repeated call to `await this.pos.getServerOrders()`) is fixed by ensuring orders load only once, even on slow connections using the flag `loadingOrderState` task-id: 4550978 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 fixes how eligible profit and loss accounts are filtered when configuring cash rounding. It ensures the account choices follow the intended rules consistently, reducing the chance of selecting an incorrect account.
Original PR description
The domain on the view overrides the domain on the model. As both domains are correct, this commit moves the partial domain on the view and adds it to the partial domain on the model. task-4514485 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When Audit Trail is enabled, users who try to delete an incorrect payment now receive a more accurate error message. This avoids suggesting an unavailable archive option and helps users understand why the action is blocked.
Original PR description
**issue:** When "Audit Trail" is activated and a user creates an incorrect payment, deleting the payment is not possible. The error message suggests archiving the payment; however, there is no option to archive it. A more flexible error message should be used instead. opw-4494820
Users in the Invoicing & Banks group can now access customer statements and partner ledger reports from partner records. This fixes missing report access for the newer invoicing role, making day-to-day customer follow-up and account review smoother.
Original PR description
With the introduction of Invoicing Enterprise (access to bank recon etc) a new user group was created "Invoicing & Banks" (`group_account_basic`) This group should also be able to access the customer statement / partner ledger (from the partner smart button) Task-4465208
The commissions report no longer displays a summed Achieved Rate when users group their commission records. This avoids showing an incorrect total for a percentage-based value, making grouped commission views clearer and less misleading.
Original PR description
Steps to reproduce: -Make multiple sales and assign a salesman to it in order to have a commission -Go to My Commissions -Add a Group By -The Achieved Rate column is displaying the sum of the achieved rates instead but it shouldn't display anything Problem: When making a group by on the commissions view and enabling the optional column achieved rate, the result of this group by would be the sum of all the achieved rate for this group, which is not correct. As it was decided that it made no sense, the total would not be displayed anymore. https://github.com/odoo/enterprise/blob/a0215115c13d5e32f1ba3c821f138b188083e76b/sale_commission/report/commission_report.py#L19 Fix: The aggregator parameter was used to prevent the total to be displayed. opw-4512739
This update cleans up an unusual indentation issue in the tax report code. It is a minor maintenance fix that helps keep the reporting module tidy and easier to maintain, with no expected change to business workflows.
Original PR description
The aim of this commit is cleaning a weird indentation introduced by this commit [[1]]. no task id [1]: https://github.com/odoo/enterprise/commit/103369fb171654f4b0457d9b1629224def7465eb
This fixes an issue where old error messages could remain visible after processing Uruguay electronic invoices. Users will see more accurate current status information, reducing confusion when reviewing invoices.
The Kenya payroll accounting demo data now assigns the required payroll journal before confirming demo payslips. This prevents demo installation and automated validation failures, helping test and demonstration environments load reliably.
Original PR description
In odoo 18.0 the `journal_id` on `hr.payroll.structure` [became not required](https://github.com/odoo/enterprise/commit/fb59524a95b0f78112002d1e4d5ad3d6c301de7e#diff-761891fe4e3aa9cb1df74ffca5261004adaf8ac8c3df5857035953e5318be967L16-R16). And in the demo data for this module `action_payslip_done` is called, which [requires](https://github.com/odoo/enterprise/blob/4784d4a48d11c72afb05f2bc7c9062c5644bbf75/hr_payroll_account/models/hr_payslip.py#L53-L54) the payroll structure to have a journal. `hr_payroll_structure_ken_employee_salary` is used as the structure for all the payslips in the demo error in runbot [build](https://runbot.odoo.com/runbot/build/73486292)
Selecting multiple documents with Shift now works correctly in both kanban and list views. This prevents folders from being accidentally selected and aligns document list behavior with other Odoo list views, making bulk actions more reliable.
Original PR description
Before this commit, In kanban view when selecting multiple documents while holding shift as modifier, it could happen that folders were selected too. This was due to the logic which was using document ids as the range value when looping on `root.records` but with the new UI where the folders are now displayed on top of the documents it was buggy. In list view, we would like to keep the same behavior as in other list views. This commit fixes those issues. Task-4532046
Users can now reliably insert views or view links from custom menus into Knowledge articles. This prevents failed insertions and error pages when navigating from custom menu actions, helping teams keep article content connected to the right business views.
Original PR description
Issue ===== The view is not inserted into the article, or the view link results in a traceback error. Steps ====== 1. Create a custom menu with its configuration using the model (Create a Menu). 2. Navigate to the custom menu action via the parent menu's route. 3. Use the actions to navigate to Knowledge > Insert view/link in article, then select an article (either existing or new). Technical ========= Due to a recent change introduced in this [commit](https://github.com/odoo/enterprise/commit/30c71b1fee8c91df5342b2b1ef5f6e888e84571d) the issue arises from the function 'this.actionService.loadAction' requiring either an actionxmlid or actWindow to process the action. Previously, only the actionxmlid was available, which caused the problem. The provided fix resolves this issue by ensuring both identifiers are correctly handled. Task-4437944
The Studio report editor now shows the translation button again when editing a report source. This lets users translate report field labels directly from the editor, restoring expected access for multilingual reports.
Original PR description
Version - 18.0 Problem - The translation button in the studio reports is hidden/ not accessible to the customer Steps to reproduce- Open Sales app > Go to the Studio view > Select Reports from the menu > Open any report among the listed ones On the left hand side - in the studio editor select "Edit Source" On the Edit source file - In the initial version there used to be an EN (Translation button) for them to translate the display field names opw-4417402