Daily updates from Odoo
Thursday, June 25, 2026
5 changes · saas-18.2
Resolved issues and error corrections
Selling a combo in Kenyan PoS no longer triggers an eTIMS registration warning for the combo itself. Only the actual products inside the combo are treated as items to register, so checkout can be completed normally when the combo parent item is not registered.
Original PR description
Steps to reproduce ------------------ 1. Install l10n_ke_edi_oscu_pos. 2. Select the Kenyan company. 3. Enable eTIMS on the PoS. 4. Register the products inside a combo, but not the combo itself. 5.…
Steps to reproduce ------------------ 1. Install l10n_ke_edi_oscu_pos. 2. Select the Kenyan company. 3. Enable eTIMS on the PoS. 4. Register the products inside a combo, but not the combo itself. 5. Sell the combo in the PoS. Observation ----------- We see a warning that the combo must be registered to eTIMS, and the order can't be validated. What's happening ---------------- In the PoS a combo adds a 0 price parent line for the combo product, but the combo is not a real item to send to eTIMS, only the products inside it are, and (as per step 4) the combo is not registered. `checkEtimsFields` sees the combo as not registered, so it raises the warning in `showUnregisteredProductsWarning` and blocks the payment in `validateOrder`. Fix --- In the backend, we skip sending the parent combo line to eTIMS, and on the frontend, we make the combo parent line not need eTIMS registration, so the warning and the block don't apply to it. opw-6253306 Forward-Port-Of: odoo/enterprise#119362
The default account codes used for cash discounts in the German SKR03 setup were incorrect and have been updated. This helps ensure accounting exports and defaults use the right accounts, reducing the risk of misposted transactions.
Original PR description
The default cash discount accounts referenced in the German skr03 template used the wrong account codes. The template has been updated with the right ones. task-4915939 opw-4909059 Forward-Port-Of: odoo/enterprise#121406 Forward-Port-Of: odoo/enterprise#121180
A minor typo in the system's redirection logic for signatures has been corrected. This ensures users are correctly directed to the correct page for managing their signatures, improving the user experience. This fix prevents potential confusion and ensures proper functionality.
Original PR description
There was a typo when forward-porting PR 116949, the redirection should be /my/signatures instead of /my/signature/signatures.
This update resolves an issue where undoing a planning action incorrectly removed allocated hours. The fix creates the necessary planning role directly within the test environment, ensuring the undo operation functions as expected and maintains accurate time tracking. This improves the reliability of the planning module.
Original PR description
Fix by creating the planning role directly within the test, making it self-contained. runbot error-939985 Forward-Port-Of: odoo/enterprise#121111
This update fixes a display inconsistency in Helpdesk ticket views. Previously, list and form views showed the default state label instead of the updated one seen in the Kanban view. The fix removes outdated field references, ensuring all views now accurately reflect the selected state.
Original PR description
Steps to reproduce: ------------------------ 1. Install Helpdesk 2. Go to All Tickets and check the kanban state selection value 3. Go to Settings > Field Selection and search for kanban_state in…
Steps to reproduce:
------------------------
1. Install Helpdesk
2. Go to All Tickets and check the kanban state selection value
3. Go to Settings > Field Selection and search for kanban_state in `helpdesk.ticket` model
4. Change one of the state selection values (e.g., "Ready" to "Testing Ready")
5. Go back and check the state selection value in list and form views
Current behavior:
-----------------------
Kanban view correctly shows the updated label (e.g., "Testing Ready"),
but list and form views still display the old default value (e.g., "Ready").
Root cause:
---------------
The [state_selection](https://github.com/odoo/odoo/blob/c09cefdb0ed68b1b7367b77b18a5ee5d66c94900/addons/web/static/src/views/fields/state_selection/state_selection_field.js#L57-L65) widget uses `legend_${state}` field values when available.
Since list and form views included these legend fields, the widget resolved labels from them
instead of the actual selection values, causing inconsistent display.
Fix:
-----
Remove `legend_normal`, `legend_blocked`, and `legend_done` fields from the list and form views,
So the widget falls back to the real selection labels, consistent with how the kanban view behaves.
Reference commit: https://github.com/odoo/enterprise/commit/65f3b88254e3a66e2c5dcb5142d30f6b1996d999
opw-6238765
Forward-Port-Of: odoo/enterprise#119707