Thursday, December 21, 2023
10 changes · 17.0
Resolved issues and error corrections
Fixed an issue that prevented users from saving general settings after all Point of Sale records were archived. This removes an unnecessary error and keeps configuration changes available even when no active PoS is set up.
Original PR description
Current behavior: The pos_self_ordering_mode field was not interpreted as invisible when no PoS existed. Because this is a required field you were not able to do any changes in the settings if you had no PoS. Steps to reproduce: - Archive all PoS - Go to Settings, and change any settings you want - Save the settings - You get an error "Invalid field 'pos_self_ordering_mode'" opw-3649784 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects the security/support documentation to reflect that Odoo 14.0 is no longer supported after the 17.0 release. It helps customers and partners understand which versions remain eligible for support and security guidance.
Original PR description
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 an unreliable automated test around bus reconnection when a device changes network state. The change helps reduce false failures in the validation pipeline, making releases and maintenance more dependable without changing user-facing behavior.
Original PR description
Before this PR, the "can reconnect after late close event" test was relying on the `nextTick` helper to check which bus events were received when the device switches from online to offline. This test was non deterministic since a tick might not be enough to receive the related events: the bus service communicates with a shared worker through the MessagePort API, the worker uses a Websocket which dispatch events upon connection/reconnection. This commit replaces the use of the `nextTick` helper by the dedicated `waitForBusEvent` helper which resolves once the event is received. fixed runbot-45695
Live chat conversations now appear in the correct order based on their latest activity, including cases where activity dates are missing. This helps agents see the most relevant customer chats first and restores the reliability of related automated checks.
Original PR description
Since [1], the test that ensures live chat threads are sorted according to their last interrest date is broken. Indeed, the sort was moved from `im_livechat` to `website_livechat`. This is incorrect. This PR moves back the call to the sort function to the `im_livechat` module. [1]: https://github.com/odoo/odoo/pull/143382 fixes runbot-47784 enterprise: https://github.com/odoo/enterprise/pull/53065
The spacing between the Log note and Activities buttons has been adjusted to match the spacing between other nearby buttons. This makes the message area look more consistent after the WhatsApp button was added.
Original PR description
The margin between the `Log note`/`Activities` is more than `Send message`/`Log note` buttons. Which looks weird after the `WhatsApp` button is added. So, we update the margin between `Log note`/`Activities` to be the same as `Send message`/`Log note` buttons. task-[3497496](https://www.odoo.com/web#id=3497496&cids=2&model=project.task&view_type=form) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The spreadsheet dashboard multi-record selector now takes only the space it needs instead of stretching across a full line. This makes dashboard filters look cleaner and preserves space for other controls, while still wrapping when space is very limited.
Original PR description
### Before: Previously, the multi-record selector dropdown occupied an entire line. ### After: This PR addresses this issue by applying the `flex: 1 0 1rem;` property to the auto-complete dropdown. This adjustment confines the dropdown to the necessary space. If the space available is less than 1rem, it will wrap to a new line. Task ID: [3607067](https://www.odoo.com/web#id=3607067&cids=2&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The gross margin button on analytic accounts now opens the correct list of related items instead of showing an empty result. This helps users review margin details without confusion or manual workarounds.
Original PR description
To reproduce: - Create a new plan with an account - Add an analytic item with this account - Go to the view of this account - Gross Margin Button has a value - Click on it => List is empty The reason being that the view should not include account_id, but auto_account_id 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
Cohort report action buttons now stay visible even when filters or measure choices return no records. This helps users recover from empty report results without losing access to key view controls.
Original PR description
This commit fixes an issue with the cohort view buttons which are not accessible when there is no data to display. This is annoying because it may happen when one changes the measures of the cohort view to one that won't display any data. This case will become quite common after https://github.com/odoo/enterprise/commit/684754430bc7062d7b69ea5b37e8aadc808c225c due to the fact that rows of null values will no longer be sent by the python to be displayed in the cohort. The fix here is therefore to move the cohort view buttons from the renderer to the controller so that they can be displayed above the no content helper and are therefore always visible even when the renderer is not present due to empty data. Steps to reproduce: - go to any cohort view (ex: Helpdesk -> Reporting -> Tickets Analysis) - filter records with a giberish filter task-3626278
This update corrects report calculation expressions used during upgrades for the Turkish localization. It helps ensure upgraded systems keep accurate localized financial reporting with minimal user-facing disruption.
The multi-record selector dropdown in spreadsheets was taking up too much space on the screen. This fix adjusts the dropdown styling so it only uses the space it needs, allowing other content to fit better on the same line. If space is limited, the dropdown will wrap to the next line instead of forcing everything to expand.
Original PR description
### Before: Previously, the multi-record selector dropdown occupied an entire line. ### After: This PR addresses this issue by applying the `flex: 1 0 1rem;` property to the auto-complete dropdown. This adjustment confines the dropdown to the necessary space. If the space available is less than 1rem, it will wrap to a new line. Task ID: [3607067](https://www.odoo.com/web#id=3607067&cids=2&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)