Monday, January 5, 2026
48 changes · master
New functionality added to Odoo
This update simplifies asset management for Odoo users in Hong Kong by automatically creating asset models. Each fixed asset is now linked to an expense and depreciation account, streamlining accounting processes. The update avoids incorporating Hong Kong's TVA tax system due to its unique accounting practices.
Original PR description
As odoo wants to simplify the using of its app for users in Hong Kong, the assets models for each asset was added so that the users don't have to register the model manually each time. Also, each fixed asset was linked to an expense account and its corresponding depreciation account. Taxes were not added because I found that Hong Kong doesn't have the concept of TVA in its accounting system. task-5246719 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds a button to the softphone interface, allowing users to mute incoming calls while they are ringing. This improves the user experience by giving users more control over incoming calls and reducing unwanted noise.
Original PR description
Added a button to mute ringtone when having incoming call
Enhancements to existing features
This update changes the survey question type from 'datetime' to 'time', providing users with a more accurate way to record time-based responses. This improves the data collected in surveys and aligns with user expectations for time input. This change is related to a previous enterprise update.
Original PR description
Change datetime question type to time question type. related PR: https://github.com/odoo/enterprise/pull/91524 Task-4896317 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update enhances how users manage members within WhatsApp channels. Specifically, the system now correctly associates a user with a channel, ensuring accurate tracking and reporting. This change improves the overall reliability and functionality of the WhatsApp module.
Original PR description
PR community https://github.com/odoo/odoo/pull/234512
Features or functions removed from Odoo
This update removes the 'joint category' functionality from the Odoo Enterprise l10n_be_hr_payroll module. This change aligns with updated Belgian tax regulations, simplifying payroll processing for businesses using this module. The removal ensures compliance and reduces complexity for users.
Original PR description
Task-5443297
Code cleanup and technical improvements
This update enhances the display of avatars within channels in Odoo. The change moves avatar URLs to the channel itself, improving performance and ensuring consistent avatar rendering across the platform. This results in a smoother user experience when viewing channel conversations.
Documentation and clarification updates
This pull request confirms that the developer has signed a Contributor License Agreement (CLA) for their changes to the Odoo codebase. The changes themselves are a standard CLA signature process, ensuring compliance with Odoo's licensing terms. This update doesn't introduce new functionality but is a necessary step for contributions.
Original PR description
@pedrobaeza --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#241227 Forward-Port-Of: odoo/odoo#241134
This update refines how time answers are displayed in Odoo survey spreadsheets. It aligns with a recent change to use a time question type instead of a datetime type, ensuring more accurate and consistent reporting of time-based responses. This improves the usability and reliability of survey data within spreadsheets.
Original PR description
Following the related PR, the datetime question type has been updated to a time question type. Adapt the display of time answers on spreadsheets. related PR: odoo/odoo#221421 Task-4896317
This update simplifies the AadharSign integration within Odoo Enterprise. Previously, AadharSign was automatically enabled and visible globally, but now it's disabled by default and only appears for companies in India. This change aligns the system with regional requirements and reduces unnecessary complexity.
Original PR description
Before this PR, the emsigner was installed by default for all apps and shown in every country. Now, the AadharSign setting is disabled by default and only visible when the company’s country is India, since it’s only needed for Indian companies. task-5175955
This update enhances the Odoo Enterprise IoT Box debug mode by displaying the correct operating system icon (Windows or Linux) based on whether the IoT Box is running virtually or physically. This provides a clearer visual representation of the IoT Box's environment for support and troubleshooting.
Original PR description
In debug mode, we now display a Windows or Linux icon depending on the OS of the IoT Box (Virtual/Physical).
This update enhances the VoIP system tray icon's behavior, ensuring it correctly identifies whether the user is in the main application tab. This improves the user experience by providing consistent functionality across different devices and operating systems. The change is considered an improvement to the existing VoIP system.
This update adjusts the spacing around text in Odoo's multiline tooltips. Following a previous change, this ensures a cleaner and more professional look for tooltips, improving the overall user experience. This is a minor visual improvement.
Original PR description
After https://github.com/odoo/odoo/pull/239198, we need to adjust the padding of multiline tooltips to avoid having too much space around the text. No task ID
This update streamlines the way Odoo templates generate data, making the code simpler and more efficient. By using 'range' instead of array keys, the system avoids unnecessary complexity and improves performance, particularly when generating static data. This change impacts multiple modules, enhancing overall system responsiveness.
Original PR description
\* = account, base_import, hr_attendance, hr_holidays, html_editor, l10n_dk, point_of_sale, portal, pos_loyalty, pos_self_order_event, spreadsheet, spreadsheet_dashboard, website, website_sale The code is simpler when using range. Note 1: in templates Owl already provides the keys as `_index` so explicitly using `keys()` or `range()` is not necessary. Note 2: when filling the result with a static value (no following `map()`), using `Array(n).fill(x)` is more efficient. task-4822140 https://github.com/odoo/enterprise/pull/86408 Note: `range` also appears to be more efficient firefox <img width="306" height="98" alt="image" src="https://github.com/user-attachments/assets/e8441c89-8863-4e75-990c-2d30869301df" /> chrome <img width="315" height="96" alt="image" src="https://github.com/user-attachments/assets/ab0c5be8-deee-4a45-892f-009b6de84dc7" />
This update enhances the partner search interface within Point of Sale. Specifically, the 'no customer' placeholder is now centered for better visibility, and a top margin has been added to the dialog to prevent the 'Create' button from overlapping the header. These changes improve the user experience and make it easier to find customers.
Original PR description
In this commit: --- - Center the “no customer” placeholder for better visibility. - Add top margin to the dialog to avoid the Create button sticking to the header line. task-5428846 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where users were encountering an error when setting default values for contact fields. Specifically, attempting to set an integer value for a date field caused a system error. The fix ensures that users cannot input invalid data types as defaults, improving data integrity and preventing unexpected errors during contact creation.
Original PR description
Steps:
- Create a user defined defaults value
- Model: res.partner
- Field: date
- Value: 1
- Create a new contact
Actual result:
- invalid field type
- 'int' object is not subscriptable (depends of field type)
Expected result:
- No error
- User is not able to put an invalid value as a default
task-3729963
Forward-Port-Of: odoo/odoo#238539
Forward-Port-Of: odoo/odoo#225991This update fixes a visual issue with the SelectMenu component, ensuring selected items are clearly displayed and readable across different frontend implementations. The change improves the overall user experience by standardizing the component's appearance and removing unnecessary customizations.
Original PR description
*: website_slides This commit fixes the 'selected' display of the SelectMenu component in some frontend implementations. Previously, the visual style would be broken since the 'active' class was set…
*: website_slides This commit fixes the 'selected' display of the SelectMenu component in some frontend implementations. Previously, the visual style would be broken since the 'active' class was set on the element, having a blank text and background on selected items. The right 'selected' class is now used, to avoid difficulties to read the value, while still having some frontend specific styles working as expected. Also, the form-control and form-select classes are set using the togglerClass props. In future versions, we might be able to remove extension of the component in other modules (e.g. hr_contract_salary), ensuring the same style and behaviors accross all places. Before: <img width="1566" height="1115" alt="image" src="https://github.com/user-attachments/assets/6265c615-bd7a-47f6-9353-c503dd934fed" /> After: <img width="791" height="350" alt="image" src="https://github.com/user-attachments/assets/939b7109-a32f-4991-a169-13f501f29eb4" /> Forward-Port-Of: odoo/odoo#240576
This update clarifies an error that occurred when deleting custom fields inherited from parent models in Odoo. Specifically, it addresses an issue related to deleting child fields on `ir.model.fields` when a model is inherited. The change ensures a clearer error message is displayed, preventing unexpected behavior during field deletions.
Original PR description
task-4829991 []# modified: odoo/addons/test_orm/tests/test_fields.py 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 fixes an issue where custom reports were displaying incorrectly formatted lines due to a flawed calculation of domain complexity. The change ensures that report formatting is accurate, especially when using advanced grouping criteria, and was tested with the recent EC Sales report.
Original PR description
When a custom groupby defined a domain with more than one element in it (typically, conditions on multiple fields, possibly with '|' or '&' operations), if groupby lines needed to be generated for subsequent groupby, the generated groupby lines had a too high level, and ended up being over-indented.
This was because the groupby expansion computed the number of higher-level groupby lines as the length of the domain needed to restrict their content. This was too naïve, and won't work well with custom groupbys, which can define longer (or even empty) domains.
This was spotted in master (19.1), with the refactored EC Sales list, which now uses a custom engine and a specific custom groupby map.
Forward-Port-Of: odoo/enterprise#102240This update resolves an issue where the 'Show Value' option wasn't functioning correctly within Odoo charts. The fix ensures the chart show value plugin receives the correct chart type information, allowing it to accurately display values for various chart types like bar and line charts. This improves chart visualization accuracy for users.
Original PR description
Since the introduction of calendar charts, the chart show value plugin takes the type of the chart as argument. But for odoo charts, we gave it the odoo chart type (eg: odoo_bar, odoo_line, etc) instead of the base chart type (bar, line, etc), which made the show value plugin not work. Task: [5421194](https://www.odoo.com/web#id=5421194&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) 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 Forward-Port-Of: odoo/odoo#240226
A visual issue was resolved where a checkbox in the chart side panel for Odoo charts did not function correctly. This update ensures that users can now properly enable the 'Use compact format' option, improving the presentation of charts. This change enhances the user experience and allows for more efficient chart viewing.
Original PR description
The checkbox to toggle the `Use compact format` option in the chart side panel was present for odoo charts, but did nothing. Task: [5405064](https://www.odoo.com/web#id=5405064&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) 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 Forward-Port-Of: odoo/odoo#240251
A technical issue preventing the 'Use compact format' option from working in Odoo charts has been resolved. This update ensures that users can now correctly apply the compact format for charts, improving visual clarity and data presentation. This fix was part of a larger task to improve chart functionality.
Original PR description
The checkbox to toggle the `Use compact format` option in the chart side panel was present for odoo charts, but did nothing. Task: [5405064](https://www.odoo.com/web#id=5405064&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#102263
This update fixes an issue where the product selection pane in the point-of-sale system was sometimes rendered too small, making it difficult to read. The fix ensures the pane maintains its intended width, improving the user experience. The problem was intermittent and related to how the layout elements interacted.
Original PR description
In some scenarios, although not fully deterministic, the left pane is being pushed by its right pane sibling (i.e. the products grid), making it go below its specified with of `left-pane-width`, and…
In some scenarios, although not fully deterministic, the left pane is being pushed by its right pane sibling (i.e. the products grid), making it go below its specified with of `left-pane-width`, and making text non readable. By setting `flex-shrink: 0` on this element, we tell the browser to respect the specified width, and not allow its siblings to shrink it. We could have also set `min-width: $left-pane-width;`, but it's less descriptive. The problem happens because we are in a flex container, hencer we use `flex-shrink: 0`. ### Notes: This issue only happened from time to time for the client, and it seems non deterministic. If we disable showing the product images, the issue stops happening. The below before vs after screenshots are taken on MacBook Pro 14 inches. ### Before: <img width="1493" height="868" alt="image" src="https://github.com/user-attachments/assets/70bc5a70-34a6-48c9-a60a-ab1de1fa0b9b" /> <img width="1496" height="867" alt="image" src="https://github.com/user-attachments/assets/e8ae9b25-3525-439b-93dd-18dc825613c7" /> ### After: <img width="1495" height="866" alt="Capture d’écran 2025-12-31 à 11 28 38" src="https://github.com/user-attachments/assets/23585d3d-b0bf-4316-8749-b39a56fc8cda" /> <img width="1497" height="866" alt="image" src="https://github.com/user-attachments/assets/f5654163-1dd3-4ff9-bb12-d8cd8fbc497b" /> opw-5392359 Forward-Port-Of: odoo/odoo#241941 Forward-Port-Of: odoo/odoo#241731
This update fixes a problem where the 'Position' column in German Sale Order reports was blank. The issue stemmed from an incorrect calculation of line numbers in the report template. Now, the report accurately displays sequential position numbers, ensuring correct reporting for sales transactions.
Original PR description
Before this commit, when printing a Sale Order using the German localization, the "Position" column in the PDF report was empty. Additionally, the table formatting was broken due to this missing data. This issue occurred because the index variable used to calculate the line number in the report template (QWeb) was incorrect. This commit fixes the index logic in the report template. Now, the "Position" column correctly displays sequential numbers (1, 2, etc.), and the table formatting renders correctly. ticket-5225647 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 Forward-Port-Of: odoo/odoo#240714 Forward-Port-Of: odoo/odoo#240243
This update resolves an issue where the Odoo command-line interface (CLI) was incorrectly handling the number of arguments passed to it. This change ensures the CLI functions reliably, preventing potential errors and improving the overall user experience. It's a technical update focused on internal stability.
Original PR description
Fine-tunning of b86c060c9d5ba03ac13e8ad59cf55731fa50ed59 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 Forward-Port-Of: odoo/odoo#240395
This update resolves an issue where renaming inherited custom fields in Odoo didn't properly remove associated database fields. The fix ensures that these generated fields are removed from the database first, preventing data inconsistencies and errors. This improves the reliability of custom field management.
Original PR description
When renaming a custom field that is inherited, first remove the generated inherited fields from the database. task-5172546 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes unnecessary configuration overrides within the Odoo mail system. This simplifies the system and improves performance, leading to a more stable and efficient email sending process. The change is a routine maintenance update.
This update corrects a previous issue where the initial company created via SQL sequence lacked a sequence number. Now, all companies, regardless of creation method, will have a consistent sequence number, preventing filtering problems based on this data. This improves data integrity and reliability.
Original PR description
For the first company, created from sql sequence is not added to it. And for the rest, case companies created via the model default sequence are already provided. This will avoid the issue when companies are filtered based on sequence number. The Intention is to add the sequence to first company is because in the model we are providing the sequence in order so it should be consistent everywhere. Ent:- https://github.com/odoo/enterprise/pull/102317
This update resolves an issue in the Odoo Enterprise testing environment by adding a sequence number to the test company. This ensures that the company data is correctly ordered within the tests, improving the reliability of the project holiday functionality. This is a minor fix to enhance test accuracy.
Original PR description
This commit adds the sequence number to test case company, to be make sure the company are is correct order. See the com :- https://github.com/odoo/odoo/pull/240329
This update resolves a rare error that could occur when users attempted to open a parent channel after a related thread had been deleted. This change enhances the overall stability and reliability of the Odoo platform, preventing potential disruptions for users. It’s a routine maintenance update focused on a technical detail.
Original PR description
This commit fixes a rare traceback that could occur when opening a parent channel from a thread that has been deleted. task-5355205 Forward-Port-Of: odoo/odoo#241309 Forward-Port-Of: odoo/odoo#241266
This update removes a redundant link in the TDS/TCS warning that allowed users to manually check invoice journal items. This simplification was driven by changes in tax regulations – the wizard now correctly suggests the appropriate tax section, and a key tax code (206C(1H)) has been removed. This streamlines the user experience and reduces potential errors.
Original PR description
The "View Journal Item(s)" link was originally added to help users Manually check invoice journal items before choosing a TDS/TCS section. For TDS, the wizard already suggests the correct tax section, so this extra review step is no longer useful. For TCS, the most commonly used section (206C(1H)) has been removed by law from 01-Apr-2025, making the button unnecessary. Before: A link appeared in the TDS/TCS warning allowing users to open the invoice’s journal items for manual verification. After: The link and its supporting logic have been removed to keep the flow simple and avoid unnecessary actions. Task - 5315061 Upgrade PR - https://github.com/odoo/upgrade/pull/9015
This update enhances the Odoo HTML editor's ability to correctly identify and process HTML tags. Specifically, it clarifies how XML-only tags are treated, preventing misinterpretation as void elements. This ensures more accurate and reliable HTML editing within Odoo.
Original PR description
Description of the issue this PR addresses: This PR refines the `selfClosingElements` list by introducing `selfClosingHtmlTags` and `selfClosingXmlTags`, which together form `selfClosingElements`. `selfClosingHtmlTags` is used in contexts where XML-only tags must not be treated as HTML void elements. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes a misleading and unnecessary warning that appeared when setting up pricelists for event products. The warning was disruptive to the user experience and didn't provide any useful information. This change improves the overall usability of the event product pricing feature.
Original PR description
* Remove the warning shown when creating pricelist rules for event products. * The warning is noisy, not well localized, and appears for every rule, resulting in a poor user experience with little practical value for most users opw-5441138 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#241287
This update clarifies warnings displayed on employee profiles when an employee is missing from a pay run. Previously, the system flagged off-cycle payslips, but now it only shows a warning if the employee has no payslip at all for the period. The message is also more user-friendly, guiding users to add payslips.
Original PR description
A warning appears on the Employee profile if an active employee is missing from an open Pay Run. **Before:** - The system checks if the employee payslip is explicitly linked to the open Pay Run. - If…
A warning appears on the Employee profile if an active employee is missing from an open Pay Run.
**Before:**
- The system checks if the employee payslip is explicitly linked to the open Pay Run.
- If they are not linked, it raises a warning ("The pay run is missing this employee"), even if the employee already has an off-cycle payslip for that specific period.
- The system treats this as an issue and prompts the user to add the off-cycle payslip to the run.
**After:**
- The logic now also considers Off-Cycle payslips. If the employee has any
off-cycle payslip covering the pay-period dates, no warning is shown.
- An issue is shown only when the employee has no payslip at all for the period.
- When showing the issue:
If multiple pay runs exist for the period:
Display a single message: "The employee is not currently in any pay run." with an action to view available pay runs.
- If only one pay run exists for the period:
Display a contextual message: "The pay run [payrun name] is missing this employee." with an action "Add payslip to Pay Run".
- If the employee is present in any pay run or has an off-cycle payslip for the
period: No message is displayed.
Task-5387310This update resolves a visual issue that occasionally appeared when using the cookies bar with a Bootstrap modal open. The fix prevents a glitch caused by Bootstrap's automatic class removal, ensuring a smooth and consistent user experience. This improves the overall appearance and functionality of the cookies consent banner.
Original PR description
When pressing `Escape` with a Bootstrap modal open, even if the config key `keyboard` is set to `false` (preventing escape from closing the modal), Bootstrap sets a class `modal-static` on the modal element and removes it shortly after. This causes a UI glitch in the case of the cookies bar. Stopping the event propagation prevents it from happening. task-5421993 Forward-Port-Of: odoo/odoo#241215 Forward-Port-Of: odoo/odoo#240269
This update corrects a technical issue where installing the 'quality_iot' module caused a JavaScript error due to a missing dependency. The fix moves a component to ensure proper module loading and functionality, preventing the error from occurring.
Original PR description
### Issue: The QualityCheck component is defined in the `mrp_workorder` module:…
### Issue: The QualityCheck component is defined in the `mrp_workorder` module: https://github.com/odoo/enterprise/blob/7c64908258d5a0fb9adecd6dd2760e255e46314b/mrp_workorder/static/src/mrp_display/mrp_record_line/quality_check.js#L7 which is not a dependency (even indirectly) of the `quality_iot` module. Hence, if you install the `quality_iot` and enable debug mode, you will raise a JS [error](https://github.com/odoo/odoo/blob/a1583d0564552007a3d5f12d967c2c0036e05e44/addons/web/static/src/module_loader.js#L164-L169) because of missing dependencies: > The following modules are needed by other modules but have not been defined, they may not be present in the correct asset bundle. This happens because commit a13e38006d3cba6cab4565de2b014d294d2c0af3 added a patch of the QualityCheck component in the `quality_iot` https://github.com/odoo/enterprise/blob/eda93203ec8da207768357ae91132a49881a2978/quality_iot/static/src/mrp_display/quality_check.js#L4 https://github.com/odoo/enterprise/blob/eda93203ec8da207768357ae91132a49881a2978/quality_iot/static/src/mrp_display/quality_check.js#L17 opw-5353986 Forward-Port-Of: odoo/enterprise#100899
This update corrects an issue with the padding within Gantt chart popovers, ensuring a more visually consistent and professional appearance. The change was necessary to address a design flaw identified in a previous development cycle, improving the overall user experience.
Original PR description
This commit fixes wrong padding inside gantt popovers body introduced in #101482. task-5166940 Forward-Port-Of: odoo/enterprise#103210
This update ensures the 'Reset to Draft' button is consistently displayed for customer invoices, regardless of whether the sales journal is hashed. Previously, invoices with a lock date were hidden from this button. This change improves usability by allowing users to easily revert invoices that don't meet hashing requirements.
Original PR description
Previously, the `Reset to Draft` button was hidden for all invoices in hashed journals, even if the invoice itself was not hashed. Now, the button is visible for invoices that are not hashed. Steps to reproduce: - Create and post a customer invoice dated Feb 2, 2023. - Set the Sales Lock Date to Feb 28, 2023. - Enable the hash setting on the Sales journal. - The 2023 invoice is not hashed due to the lock date. - Create and post a second invoice in 2025 (this one is hashed). - Remove the Sales Lock Date. - Open the 2023 invoice. Before: `Reset to Draft` button was not visible for the 2023 invoice. After: `Reset to Draft` button is now visible for the 2023 invoice. task-4911601 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where Studio could incorrectly load POS views due to sequence priority. Now, modules can override the view selection process, ensuring the correct default views are loaded regardless of sequence. This improves Studio's reliability and prevents unexpected view behavior.
Original PR description
Task: [#5191154](https://www.odoo.com/odoo/project/1737/tasks/5191154) --- When activating some views with Studio, we could end up loading a POS view because it has a lower sequence. As a result, Studio selects this view. However, these POS views may not be loaded in the backend bundle (`web.assets_backend`), and thus are missing at runtime. Example: "Cannot find key 'pos_kanban' in the 'views' registry". This commit creates a hook to get the domain used to fetch default views (`_get_default_view_domain()`). This way, modules can override the domain of `_get_default_view_domain()` method in order to exclude some views from being selected as default ones no matter the sequence. Forward-Port-Of: odoo/odoo#237122
This update resolves a problem where Studio was incorrectly loading POS views as default, leading to errors. The change prevents POS views from being selected as default, ensuring the backend operates with the intended views and improving stability. This ensures consistent view behavior across the Odoo Enterprise platform.
Original PR description
..., appointment, l10n_ke_edi_oscu_pos Task: [#5191154](https://www.odoo.com/odoo/project/1737/tasks/5191154) --- When activating some views with Studio, we could end up loading a POS view because it has a lower sequence. As a result, Studio selects this view. However, these POS views may not be loaded in the backend bundle (`web.assets_backend`), and thus are missing at runtime. Example: "Cannot find key 'pos_kanban' in the 'views' registry". This commit edit the domain of `_get_default_view_domain()` method in order to exclude these POS views from being selected as default ones. Forward-Port-Of: odoo/enterprise#98764
This update adds a subtle hover effect to the 'Picture-in-picture' and 'Fullscreen' buttons within Odoo's discuss calls. Previously, these buttons lacked visual feedback on mouse hover, making them difficult to click reliably. This change improves user experience by making the buttons easier to identify and interact with.
Original PR description
Before this commit, when in a discuss call, the buttons "Picture-in-picture" and "Fullscreen" in the bottom right had no mouse hover effect. As these buttons are visually just icons, the lack of hover effect makes it hard to tell which button is hovered thus making the click harder than it should. This commit reduces slightly the opacity of items, so that on mouse hover the opacity is removed. This acts as a small hover effect that makes it easier to click on these buttons reliably.  Forward-Port-Of: odoo/odoo#241920 Forward-Port-Of: odoo/odoo#241873
This update streamlines chat channel organization by consolidating leave channels within the main channel structure. Previously, leave channels were handled separately, creating complexity. Now, all channels are managed together, simplifying user experience and improving channel management efficiency.
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 update centralizes the display name for channels within the Odoo messaging system. Previously, display names were inconsistently managed, leading to potential confusion for users. This change ensures a more consistent and user-friendly experience when viewing and interacting with channels.
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 update refactors how Odoo handles unread messages within channels. Specifically, the logic for retrieving the first unread message has been moved to the channel model itself, streamlining the process and improving efficiency. This change ensures more consistent and reliable channel message updates.
This pull request refactors the internal handling of correspondents within the Odoo Discuss module. The change improves the underlying code structure without impacting user-facing functionality. This is a routine maintenance update to ensure the Discuss module continues to operate smoothly.
Original PR description
PR community: https://github.com/odoo/odoo/pull/235992
This update streamlines how Odoo accesses channel member information. Previously, access was through threads, but now the code directly accesses channel member IDs, aligning with the channel's data structure. This improves efficiency and accuracy when managing channel members.
Original PR description
PR enterprise: https://github.com/odoo/enterprise/pull/98888
This update refactors the way channel membership is handled within Odoo's messaging system. Specifically, it moves a key piece of data related to channel names, improving the system's efficiency and stability. This change ensures smoother channel operations and reduces potential issues.
This update ensures that the 'Correspondent Country' field is correctly associated with discussion channels. The change follows a previous update to improve channel configuration and data consistency. This ensures accurate reporting and management of channel participants.
Original PR description
Ovverride have already moved, this field should follow.
This update refactors how unread message banners are displayed within channels in Odoo. The change moves the logic for showing unread banners to the channel model itself, streamlining the system and improving its efficiency. This ensures that unread message information is consistently and accurately presented to users within channel discussions.