Tuesday, January 13, 2026
34 changes · saas-19.1
Enhancements to existing features
This update makes the HR Applicant model accessible to other Odoo modules. Previously, this model was isolated, limiting its functionality. This change allows for greater integration and data sharing across the Odoo system, improving overall HR workflow efficiency.
Original PR description
Export HrApplicant model so that it can be used in other modules Task-[5461729](https://www.odoo.com/odoo/5778/tasks/5461729) Enterprise PR odoo/enterprise#103402 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures Odoo documents fully comply with PDF/A-3A standards, a crucial requirement for certain business processes and regulatory compliance. Previously, issues with different PDF libraries caused validation failures. This change includes fixes to decoding problems and additions to meet the stricter PDF/A-3A specifications.
Original PR description
This commit upgrades our PDF/A compliance from 3B to 3A, and fixes a few issues previously undetected due to the different PyPDF libraries we're currently supporting that made the previous PDF fails…
This commit upgrades our PDF/A compliance from 3B to 3A, and fixes a few issues previously undetected due to the different PyPDF libraries we're currently supporting that made the previous PDF fails even the 3B validation. Improvement 1: PDFA validators were previously detecting our file as 3B. Hence we update the metadata content `conformance` to `A`. Issue 2: When using `._pypdf` library, we failed the 6.1.2-2 and 6.8-1 rule even though we have implemented them on the previous version. It seems that this is caused by the `if SUBMOD...` check only ensuring it's not equal to `_pypdf2_2` (which makes it trigger for the new `_pypdf`). Hence, we reclarify the comments and fix the IF check. Issue 3: After implementing issue 2, it seems that a traceback occurs every time we're using `._pypdf` and calling the pdf write method. This is because the added characters on the header can't be decoded with `UTF-8`. Hence we change it to other greater-than-127-bytes characters that can still be decoded with `UTF-8`. (The actual character used here doesn't matter). Improvement 4: To be compliant with the new 3A rules (additional rules not there in 3B when we first implemented them), we add a minimal mark info dictionary and document structure on the PDF catalog object (`_root_object`). task-None Forward-Port-Of: odoo/odoo#243171 Forward-Port-Of: odoo/odoo#234960
This update ensures our Odoo system complies with the latest Brazilian tax regulations regarding NCM (National Commerce) codes. The changes include adding a 'DEPRECATED' marker to expiring codes and introducing new codes to accurately reflect current tax requirements. This update is crucial for accurate tax calculations and reporting in Brazil.
Original PR description
This **PR** updates the NCM code list as per latest requirement. It appends `DEPRECATED` at the end of expires codes. Also it introduces a few new codes. **task**-5381617 Forward-Port-Of: odoo/enterprise#104091 Forward-Port-Of: odoo/enterprise#102009
Resolved issues and error corrections
This update resolves a technical issue preventing users from accessing the standard demo job position within the payroll demo data. Previously, the demo job was linked to the main company, causing access errors when using multi-company setups. This change ensures all companies can utilize the demo data correctly.
Original PR description
## Steps to reproduce: - install l10n_in_hr_payroll with demo data - go to employee - open payroll tab - select default contract template from Load a Template - click on load button ## Issue: - General demo job position used in many places in demo data has company_id set to main company by default. It creates access error of multi company issue. ## Fix: - The standard job in demos should not be linked to the main company by default. It should be visible and accessible for all companies. backport of https://github.com/odoo/odoo/pull/234477 Task-5440650 Forward-Port-Of: odoo/odoo#241590
This update corrects a technical issue where the product name was appearing twice in the descriptions of delivery orders and related PDF reports. The fix addresses a logic error in how Odoo builds these descriptions, ensuring consistent and accurate reporting. This improves the clarity and professionalism of our order fulfillment documentation.
Original PR description
**Steps to reproduce:** * Install the **stock** and **sale_management** modules. * Go to *Inventory > Configuration > Attributes* and create a new attribute. * Set *Variant Creation Mode* to *Never*.…
**Steps to reproduce:**
* Install the **stock** and **sale_management** modules.
* Go to *Inventory > Configuration > Attributes* and create a new
attribute.
* Set *Variant Creation Mode* to *Never*.
* Add a single attribute value and enable *Free text* on it.
* Create a product using this attribute and select the value for which
*free text* is enabled.
* Create a Sale Order for this product.
* Open the sale order line pop-up and enter custom text in the *Text* field.
* Confirm the sale order.
* Open the generated Delivery Order.
**Observed behavior:**
The product name appears **twice** in the stock move description.
The same duplication appears in the **Delivery Slip** PDF report.
**Cause:**
https://github.com/odoo/odoo/blob/452800a9fd56539c04bed5dcf4525afb9b8ad28e/addons/sale_stock/models/stock.py#L31-L32
In `_compute_description_picking`, the description is built as description + variant description.
Since Odoo already uses the product name as the base description and avoids rendering
it twice only when the name equals the description, concatenating the variant description
breaks this logic and results in the product name being repeated.
---
<details>
<summary>Click here to see the results:</summary>
Before:
<img src="https://github.com/user-attachments/assets/2f76fcc9-c71d-4c3d-a80a-06391e5d863c" />
After:
<img src="https://github.com/user-attachments/assets/78eb7905-8ce6-42b9-aed3-ac1452b74dc1"/>
</details>
---
opw-5382353
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#239843This update ensures that eTIMS configuration warnings are only displayed for companies operating in Kenya. Previously, these warnings were shown for all companies, causing confusion. This change streamlines validation and ensures warnings are relevant to users in the correct location.
Original PR description
Before: In multi-company setups, the eTIMS configuration warning was shown even when working in companies that are not based in Kenya. This resulted in confusing and irrelevant warnings for users using other localizations. After: The eTIMS configuration warning is now limited to Kenyan companies only. Non-Kenyan companies are no longer impacted, keeping the validation relevant while preserving the intended eTIMS behavior. task-5462334 Forward-Port-Of: odoo/enterprise#103291
This update resolves an issue where the fullscreen button in the Odoo interface was hidden by a temporary overlay. The change adjusts the layout to prevent overlapping controls, ensuring users can easily access and utilize the fullscreen mode. This improves the overall user experience.
Original PR description
**Purpose of this PR:** When the call control overlay is floating, it overlaps the fullscreen button, making it difficult to enter fullscreen mode. for reference: <img width="711" height="257" alt="image" src="https://github.com/user-attachments/assets/4a7a7448-4988-4cf6-bcfb-6a91491be80d" /> This commit ensures the fullscreen action remains accessible by adjusting the layout layering so controls no longer overlap each other. Task-[5240896](https://www.odoo.com/odoo/project/1519/tasks/5240896) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#241747
This update corrects a display issue where archived recurring plans continued to show up as pricing options on the website. The fix ensures that archived plans are no longer considered during the pricing selection process, improving the user experience and preventing outdated information from being presented. This ensures accurate pricing is displayed to customers.
Original PR description
**Steps to produce:** - Install `sale_subscription,website_sale` module. - `Subscription > Configuration > Recurring Plans`. - `Archive` the `Monthly` plan. - Go to website > Shop > Open product `Car…
**Steps to produce:** - Install `sale_subscription,website_sale` module. - `Subscription > Configuration > Recurring Plans`. - `Archive` the `Monthly` plan. - Go to website > Shop > Open product `Car Leasing (SUB)`. **Issue:** - Even after archiving the Monthly recurring plan, its pricing still appears on the website product page. **Root cause:** - At [1], when searching for a suitable recurring price, the system does not filter out pricing records belonging to archived recurring plans. - As a result, inactive plans are still considered during pricing selection. **Solution:** - In this fix, we ensure that recurring plan pricing is included only if the related plan is active. - Archived plans are now ignored, preventing them from appearing on the website. [1]: https://github.com/odoo/enterprise/blob/25edaac85f8fd1699bb78163b01efb966e7fb680/sale_subscription/models/sale_subscription_pricing.py#L78-L79 before <img width="340" height="184" alt="recurring_plan_before" src="https://github.com/user-attachments/assets/abac39fb-5765-4bc4-aec3-87eef7135a18" /> after <img width="337" height="168" alt="recurring_plan_after" src="https://github.com/user-attachments/assets/35ee92e8-e66b-4612-add3-58b277560ea5" /> **opw-5266333** Forward-Port-Of: odoo/enterprise#103473 Forward-Port-Of: odoo/enterprise#100587
This update fixes a potential issue where tour interactions with the Clipboard API weren't reliably mocked, particularly in headless environments. By delaying cleanup until the API call is complete, the system now correctly simulates Clipboard API behavior, preventing browser delays or permission errors. This ensures tours function smoothly across different Chrome versions.
Original PR description
Reliably mocking Clipboard API calls in tours should be done in two steps: - the step that will actually do the call should do the patching, followed by the actual action. - the cleanup should only be done in the following step to ensure the action's listener has actually finished. This commit applies this principle to avoid the "cleanup" to be executed before the action's listener has actually reached the call to the Clipboard API (because of slower processing, slower network...), which would defeat the mocking purpose (and either get the browser to indefinitely wait for the user's clipboard usage approval or a permission error depending on the browser's default behavior). Note: this was mainly brought to light by the new Chrome 143+ default policy which revoke all permissions in headless mode. Forward-Port-Of: odoo/odoo#243280
This update fixes a potential issue with how Odoo tours mock the Clipboard API, particularly in headless environments like Chrome. By delaying cleanup until the API call is complete, the system avoids delays or permission errors, ensuring tours function reliably. This resolves a compatibility problem highlighted by a recent Chrome update.
Original PR description
Reliably mocking Clipboard API calls in tours should be done in two steps: - the step that will actually do the call should do the patching, followed by the actual action. - the cleanup should only be done in the following step to ensure the action's listener has actually finished. This commit applies this principle to avoid the "cleanup" to be executed before the action's listener has actually reached the call to the Clipboard API (because of slower processing, slower network...), which would defeat the mocking purpose (and either get the browser to indefinitely wait for the user's clipboard usage approval or a permission error depending on the browser's default behavior). Note: this was mainly brought to light by the new Chrome 143+ default policy which revoke all permissions in headless mode. Forward-Port-Of: odoo/enterprise#103971
This update ensures that thumbnails on public documents are automatically reflected in their associated shortcuts. Previously, public users couldn't update shortcuts even when the document itself was updated. This change corrects a permission issue that prevented thumbnail propagation, ensuring a consistent experience for all users.
Original PR description
Bug === 1. Create a request 2. Create a shortcut to that request 3. Share it to public 4. Public upload => The thumbnail is updated on the document, but not on the request. The reason is that the public user has `user_permission = none`, because he has only access with the token, and so we skip the thumbnail propagation. This has no sense, because if we don't have access on the document, we loose the access on the shortcut (even if we are the owner). Task-5485511 Forward-Port-Of: odoo/enterprise#102888
This update fixes a visual issue on the eating location page where a single preset option was left-aligned. Now, when only one preset is available, it's automatically centered for a cleaner and more user-friendly experience. This ensures consistent presentation of options for self-ordering.
Original PR description
On the eating location page, when there is only one preset, we would like to center it. Before, when there is only one preset available, it was aligned on the left. This occurs when there is two presets for a pos config and the default one is not available in self o task:5478651 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243012
This update ensures that when importing electronic invoices, the system correctly identifies and uses existing bank accounts linked to the same supplier, regardless of the company where the invoice is being created. Previously, the import would fail due to a constraint issue, even if the bank account already existed. This improves the efficiency of invoice processing.
Original PR description
Description of the issue/feature this PR addresses: Imagine a situation where a vendor is defined on a parent company and its bank account already exists. When importing an electronic invoice for…
Description of the issue/feature this PR addresses: Imagine a situation where a vendor is defined on a parent company and its bank account already exists. When importing an electronic invoice for that vendor on a child company, the search for a bank account linked to the same company would not find that pre-existing bank account on the parent company. When later trying to create it, the unicity constraint on (sanitized_acc_number, partner_id) would trigger, failing the import. Current behavior before PR: The electronic invoice cannot be imported if the same IBAN account already exists on the partner but on another company than the invoice being created, even though we are going to create the invoice for a partner linked to that other company. Desired behavior after PR is merged: Banks account already linked to the partner are found irrespective of the company, provided the partner (account holder) is the same. This should be correct since the res.partner.bank company_id is a related on res.partner. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#242365
This update resolves a minor issue that caused tests for embedded actions to sometimes fail unpredictably. By adding a necessary wait for the browser's update cycle, the tests are now more reliable and consistent. This ensures the continued stability of our web application.
Original PR description
In this commit, we add a missing await for an animation frame in an embedded action test. This ensures that the test waits for the DOM to update properly before proceeding, preventing potential flakiness in the test execution. runbot error~237752 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243240
This update resolves a validation error in Odoo Studio related to customizing contact fields. The issue stemmed from a missing 'help' attribute in the field definitions, preventing proper validation of changes made through the Studio interface. This ensures that customizations to contact lists are now correctly validated.
Original PR description
Steps to reproduce ================== - Install web_studio,contacts - Go to Contacts - Open the list view - Click on a field - Set a "Help tooltip" => Validation Error Invalid view Odoo Studio: res.partner.tree customization Cause of the issue ================== The help attribute is missing from the field definition opw-5379357 Forward-Port-Of: odoo/odoo#240261
This update fixes an issue where the 'Preview on Portal' button appeared in vendor bill emails, causing problems with the portal payment process. The change now ensures vendor bills include the original vendor PDF, and a minor visual adjustment has been made to improve the visibility of the input field in email notifications. This ensures a smoother experience for vendors.
Original PR description
Vendor bill emails are meant to include the vendor’s original PDF rather than an Odoo-generated invoice. The "Preview on Portal" button was hidden to avoid facing errors in the portal payment page. Additionally, remove the CopyClipboardChar widget from the "incoming_einvoice_notification_email" field to make the input placeholder visible. task-5438315 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#242850
This update resolves a bug where creating a new employee version with a date later than an existing version's contract end date resulted in duplicate contract creation. The fix ensures that contracts are only created for the active employee version, streamlining the payroll process and preventing unnecessary contract generation.
Original PR description
To reproduce: install hr_payroll open an employee form view > payroll make sure the employee_version you are on doesn't have a contract end date set the end date to X and without saving create a new employee version from the plus sign with date greater than X The Bug: when following the above flow a contract will be created for both employee versions it shouldn't be the case for the second version as version date is greater than contract end date opw-5427769 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243153 Forward-Port-Of: odoo/odoo#240681
This update resolves a test failure in the Odoo ecommerce module. The previous code included unnecessary elements that weren't relevant to the test, causing errors. The changes removed these elements to ensure the tests run correctly and accurately reflect the ecommerce functionality.
Original PR description
The code of the payment provider is not relevant to the test_ecommerce_paid_order_is_hidden_in_pos test, and pos_sale doesn't have payment_custom in the dependencies. It caused tests to fail so I removed it. Runbot Build Error-233461 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#232638
This update corrects minor errors in the Danish local reports (balance sheet and profit & loss) for 2026. These were unintentional oversights during development and ensure accurate financial reporting for our Danish customers. No new functionality was added.
Original PR description
In this commit: https://github.com/odoo/enterprise/commit/0d431fe2cc6556a040888ecc5d6a71be4a435447 we introduce a new balance sheet report for 2026 but there was a mistake in the sign of a formula and in the text of a line. Same for the profit and loss, some errors in sign of accounts and naming. The errors don't come from a ticket but more of a logical fix, those errors were probably an oversight during development. no task id Forward-Port-Of: odoo/enterprise#103830
The website image tests were intermittently failing due to the unpredictable nature of image loading times. This update uses a more robust method to ensure the UI is fully updated before tests run, resolving these intermittent failures. This improves the reliability of our website testing process.
Original PR description
The image_size tests were failing in a nondeterministic way. Image-related options can take an indeterminate amount of time to complete, so waiting for a single animation frame is not always sufficient. Use `waitSidebarUpdated`` to ensure there are no pending actions and that the UI is fully updated before asserting. Error-237539 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 corrects a recent change to the account online synchronization access rights, ensuring it's correctly linked to Invoicing & Banks. The previous change missed a critical step, preventing proper synchronization of duplicate transactions. This fix ensures data accuracy and reliability for financial processes.
Original PR description
In this commit: https://github.com/odoo/enterprise/commit/6edc057a9c0459af2b6d625415b700daf6280520 we changed the access rights of the account online sync to Invoicing & Banks but forgot to add the duplicate transactions no task id Forward-Port-Of: odoo/enterprise#104008
This update resolves a problem where the 'copy link' button in the salary calculator was generating a 404 error. The fix ensures the offer is properly saved before creating the link, preventing errors and allowing users to correctly copy salary details. This improves the usability of a key payroll function.
Original PR description
Steps to reproduce: 1- Open salary calculator 2- Do not edit any fields 3- Click on copy link button 4- Open the link Issue: When you open the link you'll see a 404 page. Cause: The salary calculator essentially creates an offer. When no fields are modified in the form, the offer isn't created yet. When a link is created for that offer, the offer id part of the link is NewId_xxx. Fix: Modify the widget that copies the link to clipboard to first save the offer before generating the link. Task-5441297 Forward-Port-Of: odoo/enterprise#102900
This update resolves an issue where the AI module's exception handling wasn't functioning correctly, specifically when a request cursor closed. By using the local environment within the generator, this fix ensures more reliable exception management and prevents potential errors, improving the overall stability of the AI features.
Original PR description
self.env is invalid inside generator after request cursor closes
This update resolves a problem where call duration wasn't consistently appearing in chatter messages. The previous fix modified the message content, leading to unreliable matching and failures. This change ensures call duration is accurately reflected in chatter messages.
Original PR description
After 5751f93c53d3cf37ae8cb627fb8d10a81b7b8833, call duration will be added to chatter message. This change is done by modifing the original message, which results in a non-deterministic failure when selector trying to match the original message. Change the selector to match a stable attribute.
This update fixes a previous issue where the messaging menu incorrectly added channel needaction counters to the inbox count. Now, the inbox counter accurately reflects the number of unread channels requiring attention, providing a more precise view of communication needs. This ensures users have a reliable understanding of their messaging workload.
Original PR description
This commit corrects a regression intoduced in [1]: the messaging menu now subtracts the channels needaction counter from the inbox counter, rather than adding it [1] https://github.com/odoo/odoo/pull/229751 Forward-Port-Of: odoo/odoo#243318
Website image editing tests were intermittently failing due to delays in updating the builder sidebar. This update ensures the sidebar is fully loaded before tests run, resolving these intermittent errors and improving the reliability of our website builder tests. This prevents disruptions to the website builder experience.
Original PR description
Image edit tests using the builder sidebar were failing intermittently because image elements rely on async actions with non-deterministic timing, causing the sidebar options to be unavailable sometimes. Use `waitSidebarUpdated` to ensure the sidebar is fully updated before asserting on its content. Here is an example of an error: error-234951 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#243135 Forward-Port-Of: odoo/odoo#243008
This update fixes an issue where users without write access couldn't star messages in threads. The fix adds a necessary permission adjustment to ensure all users can star messages they can read, improving usability and preventing errors. This change ensures consistent functionality for all users.
Original PR description
Before this commit, starring a message in a thread without write access would result in an access error. This happens because since [1] a message is marked as starred by writing on the `starred_partner_ids` field of mail.message instead of the `starred_message_ids` field of res.partner. This results in an access error when the uses does not have write access. This commit fixes the issue by adding a sudo call to the write of `starred_partner_ids`, which is acceptable because a user should always be able to star a message they can read. [1] https://github.com/odoo/odoo/pull/219282 task-5481662 Forward-Port-Of: odoo/odoo#243130
This update streamlines the process of assigning barcodes to product packaging. Previously, users faced a confusing, multi-step process leading to duplicate UoM creation. Now, the barcode field is integrated directly into the packaging creation flow, providing a simpler and more efficient experience.
Original PR description
Before this commit: ------------------------- - In the product form view, when creating new packaging, a pop-up form opens to Create a new Unit of Measure (UoM), and if the user tries to assign a…
Before this commit: ------------------------- - In the product form view, when creating new packaging, a pop-up form opens to Create a new Unit of Measure (UoM), and if the user tries to assign a barcode Within that form, a second pop-up opens instead of assigning the barcode directly. - In the second pop-up, if the user creates the same UoM again, it causes data duplication; the same UoM gets created in 'Units and Packagings' with a default quantity of 1 without reference unit. This incorrect behavior leads to confusion when selecting the UoM later. Steps to reproduce: ------------------------- 1. Install the 'sale_stock' module. 2. Enable Units of Measure & Packagings in stock. 3. Create or open any product. 4. Go to the Sales tab. 5. Create new packaging (e.g., Pack of 5), set the quantity and reference unit, and try to create a barcode. 6. A second pop-up form opens to again create a new UoM and assign the barcode. 7. It causes data duplication; the same UoM gets created in 'Units and Packagings' with a default quantity of 1 without reference unit. Cause of the issue ------------------------- When assigning a new barcode to a UoM, the field could not fetch the corresponding UoM(In uom.uom) record because it did not yet exist in the database. As a result, the system opened another pop-up to create the same UoM(In product.uom) again and assign a barcode to it. After this commit: ----------------------- - The barcode field is hidden until the UoM is created. - Once the packaging is saved, users can edit it to assign a barcode to the specific UoM of the product. - This improves the flow by preventing duplicate UoM creation and ensuring a clear, single-step process for assigning barcodes to product packaging. Task ID:5023229 Forward-Port-Of: odoo/odoo#230474
This update resolves a visual issue where the zoom level in document signing would rapidly change, causing a distracting flicker. The fix removes the automatic zoom adjustments, defaulting to 'Automatic zoom' for a smoother and more stable signing experience. This improves user satisfaction and professionalism.
Original PR description
Before this commit, when signing a document the zoom would load with 'Automatic zoom' then less than one second later change to another zoom by the code, e.g. '100%', causing a flickering issue. After this commit, the zoom is not flickering anymore as we remove the code of changing the zoom and make the default the 'Automatic zoom'. task-5461663 Forward-Port-Of: odoo/enterprise#103532
This update removes the use of the Gemini 1.5 model within the AI features of Odoo Enterprise. The change provides a clear error message when attempting to use the model, preventing unexpected behavior. This ensures a more stable and reliable AI experience for users.
Original PR description
This PR deprecates the Gemini 1.5 models. Specifically, it gives a proper non-technical error when the model is used. The error occurs either when the user tries to set the model on an agent or if the model is already on the agent, it will raise the error upon usage of the agent. task-5129790 Forward-Port-Of: odoo/enterprise#102761
This update corrects a minor issue in the Sendcloud integration, ensuring accurate product data is retrieved. The previous method of accessing product information was unreliable due to changes in the system's data structure. This fix guarantees consistent and correct product selection within the Sendcloud workflow.
Original PR description
Same fix as d4fae97, the id was retrieved by doing `[0]` but the proxy object has changed so we need to use the `id` key to get the value instead. ----- Ticket: opw-5433254 Forward-Port-Of: odoo/enterprise#103706
This update resolves an issue where the full composer window unexpectedly opened when users edited messages within tasks. The fix prevents this behavior, ensuring a smoother editing experience and avoiding potential user confusion. This change improves the stability and usability of the messaging system.
Original PR description
Steps to reproduce: =================== 1- Go to a project task & log any note. 2- Edit & Click the additional "+" and click "Open Full Composer" 3- Click on Save. -> traceback. Cause: ====== When entering edit mode, the composer was created without a thread reference, causing "Cannot read properties of undefined (`this.props.composer.thread is undefined`)" errors in `onClickFullComposer`. Solution: ========= We shouldn't have "open-full-composer" action in editing messages opw-5443985 Forward-Port-Of: odoo/odoo#242002
This update resolves an issue where applications weren't accurately counted and matched within a multi-company Odoo environment. The change removes a specific filtering condition, streamlining the process and ensuring accurate application counts are calculated across all companies. This improves the reliability of reporting and analysis for multi-company businesses.
Original PR description
This commit fixes the issue where applications are not matched are not mathced with thier count among companies in a multi-company environment. The domain on company was removed from `_get_similar_applicants_domain` since there is no domain on company in `_compute_application_count`. task-5375876 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243154 Forward-Port-Of: odoo/odoo#238386
This update corrects a technical error that prevented public channels in Odoo from functioning correctly. The change sets the correct `group_public_id` to `None`, ensuring channels are properly designated as public. This resolves a previous bug impacting channel visibility.
Original PR description
Since #206619, the fixed test has used a wrong value for `group_public_id`, as if it's not set, the default is `Internal User`. This change sets it to `None` to make the channel public. Forward-Port-Of: odoo/odoo#243354 Forward-Port-Of: odoo/odoo#243237