Daily updates from Odoo
Navigate
Branch
Wednesday, July 5, 2023
21 changes
New functionality added to Odoo
Users can now insert emojis directly while editing text by typing /emoji, making content creation more expressive and convenient. The emoji picker was also moved into a shared web component so it can be reused beyond messaging.
Original PR description
Purpose: This commit adds Emoji_picker functionality to the web_editor, allowing users to conveniently add emojis to their text and improving the overall user experience. Specifications: Now we can insert emoji in web_editor using /emoji. Task id: 3253958
Enhancements to existing features
Employee and applicant private address details are now stored directly on their HR records instead of separate partner records, reducing access issues and confusion. Salary offer handling is also more stable and traceable, improving control over offer changes and reporting.
Original PR description
- The private addresses have been removed from the "res.partner" model. - The employees' private address information has been moved to the "hr.employee" model, preserving the old records but emptying the private information fields. - The applicant's private address information has been moved to the "hr.applicant" model, following the same approach. - More generally, some efforts have been done to ensure we only create and use the same partner from the application form, to the employee creation and also the user creation. - The salary configurator offer mechanism has been improved to provide stability (no more arguments in URL), traceability (track changes and responsibles) and reporting. TaskID: 3101400
When a project is renamed, its related Documents workspace is now renamed too, as long as that workspace is not shared with other projects. This keeps project files easier to find and avoids confusing outdated workspace names.
Original PR description
Before this PR when we create a project then workspace was set as project/project name but when we rename a project the workspace was not renamed. After this PR if the workspace is not linked with other projects then it will be modified if we modify/rename the project name. task-3330282
This change adjusts internal performance test expectations for the Enterprise Discuss test suite to match the current behavior. It helps keep automated checks reliable without changing how users experience the product.
Original PR description
https://github.com/odoo/odoo/pull/125961
The delete option in Knowledge article actions has been moved to the bottom of the menu. This makes it less likely that users accidentally delete an article when choosing other actions.
Original PR description
When the user wants to perform any action on the article (from the top right corner, there is an action menu), the delete button is between the other buttons. So, sometimes users maybe misclick on the delete button. With this PR, the delete button moved to the bottom of the action buttons. **Task**-3397730
Resolved issues and error corrections
Users can now open planned shifts from a project update and use the Plan Orders button without hitting an error. The fix updates how open tasks are identified and places the logic in the module that has the right project dependencies.
Original PR description
Before this commit, when the user goes to project update of a Project A and click on `Planned` stat button to display the shifts linked to that Project A. Then the user will click on `Plan Orders` button, a traceback will occurs saying `is_closed` field does not exist in `project.task` model.
This commit fixes the issue by changing `('is_closed', '=', False)` in the domain used into `('state', 'not in', ['1_done', 1_canceled])` since `is_closed` has been recently removed. Also, this commit moves that code in sale_project_forecast because `project.task` model does not exist in `sale_planning` module since `project` module is not in the dependencies of that module.This update fixes issues in accounting asset and field service tests caused by changes to form behavior. It helps ensure these areas continue working reliably after related platform updates.
Original PR description
Companion of https://github.com/odoo/odoo/pull/127400
User mentions in chat and related conversations now appear faster by removing an unnecessary delay while still controlling server load when responses are slow. The change also prevents a small crash that could happen when repeatedly starting and deleting a mention.
Original PR description
This reverts https://github.com/odoo/enterprise/pull/43502. Motivation for debounce was to reduce the amount of RPCs, to not put too much load on server. However, this makes showing of mention slower…
This reverts https://github.com/odoo/enterprise/pull/43502.
Motivation for debounce was to reduce the amount of RPCs, to not put too much load on server.
However, this makes showing of mention slower than it should, and the load on server is already adjusted based on duration of ongoing `fetchSuggestion` RPC: if server can reply with mentions immediately, then no need to debounce. If the RPC is slow, then next `fetchSuggestion` waits for current RPC to finish before making a new fetch.
This PR also fixes this small crash when using mentions:
```
TypeError: Cannot read properties of undefined (reading 'toLowerCase')
at cleanTerm (format.js:244:1) (/mail/static/src/utils/format.js:244)
```
Steps to reproduce:
- type `@` then `backspace` then `@` then `backspace`, etc.
This happened because suggestion hook internal state had `term` being undefined when there is no term, but `undefined` is invalid for `cleanTerm`. `""` is a better default for no search term, and since this is a string this works with `cleanTerm`.
https://github.com/odoo/odoo/pull/127399This update makes automated checks for the grid view more reliable by waiting until the screen component is fully ready before validating results. It helps reduce false test failures and supports smoother ongoing maintenance without changing user-facing behavior.
Original PR description
Before this commit, the assert done in 2 tests could failed because the component is not yet fully mounted/re-rendered. This commit adds a next tick to be sure we wait the component be mounted and rendered before doing the asserts.
Documentation and clarification updates
The license labels for the Point of Sale preparation display modules have been corrected from LGPL-3 to OEEL-1. This ensures the modules are classified under the appropriate enterprise license, helping maintain accurate compliance and product packaging information.
Original PR description
before this commit, for the pos_preparation_display and pos_restaurant_preparation_display modules, the license is added as LGPL-3 after this commit, license of both the modules will be updated to OEEL-1.
Miscellaneous changes
In sign, when generating the complete file, there are some errors that can happen if the sign.request has invalid or wrong values. This commit adds some try/catch blocks to inform the user that something is wrong. opw-3272737 opw-3094675 opw-3236508 Co-authored-by: Pedro Manuel Calheiros Lima de Sousa <peso@odoo.com> Forward-Port-Of: odoo/enterprise#43464 Forward-Port-Of: odoo/enterprise#42968
Original PR description
In sign, when generating the complete file, there are some errors that can happen if the sign.request has invalid or wrong values. This commit adds some try/catch blocks to inform the user that something is wrong. opw-3272737 opw-3094675 opw-3236508 Co-authored-by: Pedro Manuel Calheiros Lima de Sousa <peso@odoo.com> Forward-Port-Of: odoo/enterprise#43464 Forward-Port-Of: odoo/enterprise#42968
Steps : - Go to helpdesk module and create a ticket. - give it a long name and save it. - See tickets in portal. - ticket content is being displayed underneath contact info card. Fix : website tickets the content is displayed in the right of the left panel instead of displaying below. task-3183804 Forward-Port-Of: odoo/enterprise#43634 Forward-Port-Of: odoo/enterprise#37462
Original PR description
Steps : - Go to helpdesk module and create a ticket. - give it a long name and save it. - See tickets in portal. - ticket content is being displayed underneath contact info card. Fix : website tickets the content is displayed in the right of the left panel instead of displaying below. task-3183804 Forward-Port-Of: odoo/enterprise#43634 Forward-Port-Of: odoo/enterprise#37462
Steps to reproduce: - Install `Knowledge` module - Create a new article - Add a kanban view to the article - Group by `Article Cover` - Try to quick create a new group (`+ Article Cover`) Issue: Traceback is raised. Cause: `knowledge.cover` model does not have a `_rec_name` attribute, therefore, it is not possible to do a `name_create` on this model. Solution: Override the `name_create` method to raise an error. opw-3179109 Forward-Port-Of: odoo/en
Original PR description
Steps to reproduce: - Install `Knowledge` module - Create a new article - Add a kanban view to the article - Group by `Article Cover` - Try to quick create a new group (`+ Article Cover`) Issue: Traceback is raised. Cause: `knowledge.cover` model does not have a `_rec_name` attribute, therefore, it is not possible to do a `name_create` on this model. Solution: Override the `name_create` method to raise an error. opw-3179109 Forward-Port-Of: odoo/enterprise#40950
This commit changes the toggler button to an actual button element, which allows the icon to be displayed as expected in black or white, depending the actual theme used for Odoo. The alt attribute has been removed, since it is not supported on a <button> element, neither it was on the previously used <a> element. By using an <a> element, the font was colored in cyan instead. Other systray items were already using <button> elements. Forward-Port-Of: odoo/enterprise#43585
Original PR description
This commit changes the toggler button to an actual button element, which allows the icon to be displayed as expected in black or white, depending the actual theme used for Odoo. The alt attribute has been removed, since it is not supported on a <button> element, neither it was on the previously used <a> element. By using an <a> element, the font was colored in cyan instead. Other systray items were already using <button> elements. Forward-Port-Of: odoo/enterprise#43585
The aim of this commit is to fix the credit note wizard for CL after the generic wizard refactor [(see here)](https://github.com/odoo/odoo/pull/117961/files#diff-1bfd24cca21724d67d0b85aaadaec5b89e5d2c17a0766d33cccdb0840d54356d) Previous to this commit: After removal of the refund method field (which had 3 possible values), the cl credit note wizard is not working as intented. Each option triggered specific values for "only text correction" field and "SII Reference Code". Now the option
Original PR description
The aim of this commit is to fix the credit note wizard for CL after the generic wizard refactor [(see…
The aim of this commit is to fix the credit note wizard for CL after the generic wizard refactor [(see here)](https://github.com/odoo/odoo/pull/117961/files#diff-1bfd24cca21724d67d0b85aaadaec5b89e5d2c17a0766d33cccdb0840d54356d) Previous to this commit: After removal of the refund method field (which had 3 possible values), the cl credit note wizard is not working as intented. Each option triggered specific values for "only text correction" field and "SII Reference Code". Now the option have to be triggered differently. After this commit: Case 1: If the the boolean "only text correction" is set as true by the user: -> Display the Fields "Original Text" and "New corrected text" and set the field "SII reference code" to "2. Corrects Referenced Document Text". Case 2: If the user keeps the boolean false, then the SII reference code should be set by default the "1. Cancels Referenced Document Text". Also add the possibility to modify on an invoice the SII Reference Code. task: 3374344 Forward-Port-Of: odoo/enterprise#42805
Steps to reproduce: 1. Install stock_barcode 2. Settings, Inventory, Enable Units of Measure and Storage locations 3. Create product P 4. Update quantity, New: Counted Quantity = 20, Apply 5. Barcode app, Inventory Adjustment, Add product P 6. Change to small viewport Issue: The quantity input is covered by the "/xy Units" button. opw-3256251 Forward-Port-Of: odoo/enterprise#42803
Original PR description
Steps to reproduce: 1. Install stock_barcode 2. Settings, Inventory, Enable Units of Measure and Storage locations 3. Create product P 4. Update quantity, New: Counted Quantity = 20, Apply 5. Barcode app, Inventory Adjustment, Add product P 6. Change to small viewport Issue: The quantity input is covered by the "/xy Units" button. opw-3256251 Forward-Port-Of: odoo/enterprise#42803
This is a forward-port of the test introduced in [1] We check all around midnight to make sure all kinds of recurring appointment slots are handled as expected when the slots are around midnight. [1]: 93c192cfe5d0e50fd1b812d33e812da90b88c6d4 task-3143449 Forward-Port-Of: odoo/enterprise#43548
Original PR description
This is a forward-port of the test introduced in [1] We check all around midnight to make sure all kinds of recurring appointment slots are handled as expected when the slots are around midnight. [1]: 93c192cfe5d0e50fd1b812d33e812da90b88c6d4 task-3143449 Forward-Port-Of: odoo/enterprise#43548
'cash_basis' option key becomes 'report_cash_basis' in 16.0. This was wrongly forward-ported from the original 15.0 fix in https://github.com/odoo/enterprise/commit/f2833e48feefe7be7d0c9f99de9f447bc3b4af97. Putting 'cash_basis' in the options had no effect. The test was only considering one invoice, with a payment made prior to it: in this case, the invoice has to appear at the invoice date ... which is exactly what will happen when not using the cash basis feature. So, in this case, the repo
Original PR description
'cash_basis' option key becomes 'report_cash_basis' in 16.0. This was wrongly forward-ported from the original 15.0 fix in https://github.com/odoo/enterprise/commit/f2833e48feefe7be7d0c9f99de9f447bc3b4af97. Putting 'cash_basis' in the options had no effect. The test was only considering one invoice, with a payment made prior to it: in this case, the invoice has to appear at the invoice date ... which is exactly what will happen when not using the cash basis feature. So, in this case, the report was called without the cash basis, but returned the expected result. We make this more robust by creating a second invoice without any payment at the same date as the existing one: this invoice will not appear in the report when using the cash basis method, ensuring the result of the report will be different with or without the option. Forward-Port-Of: odoo/enterprise#43473 Forward-Port-Of: odoo/enterprise#43443
PR #30564 introduced a viral dialog to 'promote' Odoo Sign to external users, however having a primary button for this can be quite confusing, especially when the redirect feature is used as well. This task aims to fix it by making it still present but less in your face, so that users do not mix up marketing flows with primary flows task-id : 3342905 Forward-Port-Of: odoo/enterprise#43088 Forward-Port-Of: odoo/enterprise#41693
Original PR description
PR #30564 introduced a viral dialog to 'promote' Odoo Sign to external users, however having a primary button for this can be quite confusing, especially when the redirect feature is used as well. This task aims to fix it by making it still present but less in your face, so that users do not mix up marketing flows with primary flows task-id : 3342905 Forward-Port-Of: odoo/enterprise#43088 Forward-Port-Of: odoo/enterprise#41693
Before this commit, all token available were saved on the sale order on confirmation. This caused an issue when the transaction was a partial payment of the invoice. No invoice would be created and therefore the next invoice date would be equal to the start date. The invoicing cron would run and charge the total amount on the token. This commit prevent to save the token in case of partial payments. taskid: 3375151 Forward-Port-Of: odoo/enterprise#43381 Forward-Port-Of: odoo/enterprise
Original PR description
Before this commit, all token available were saved on the sale order on confirmation. This caused an issue when the transaction was a partial payment of the invoice. No invoice would be created and therefore the next invoice date would be equal to the start date. The invoicing cron would run and charge the total amount on the token. This commit prevent to save the token in case of partial payments. taskid: 3375151 Forward-Port-Of: odoo/enterprise#43381 Forward-Port-Of: odoo/enterprise#42530
Steps to reproduce the bug: - Install delivery sendcloud. - Create a new shipping method with "sendcloud" as the provider. - Create a sale order: - Add any storable product. - Click on "add shipping". - Select "sendcloud". - Confirm the sale order. - Go to the linked delivery. - Try to validate it. Problem: A traceback is triggered: "AttributeError: 'sale.order' object has no attribute 'access_point_address'". The field "access_point_address" is defined in the "Website_sale" modu
Original PR description
Steps to reproduce the bug: - Install delivery sendcloud. - Create a new shipping method with "sendcloud" as the provider. - Create a sale order: - Add any storable product. - Click on "add shipping". - Select "sendcloud". - Confirm the sale order. - Go to the linked delivery. - Try to validate it. Problem: A traceback is triggered: "AttributeError: 'sale.order' object has no attribute 'access_point_address'". The field "access_point_address" is defined in the "Website_sale" module, and the "delivery_sendcloud" module does not depend on it: https://github.com/odoo/enterprise/blob/88d28042fde35811bf01ee012bd245ade6289885/delivery_sendcloud/__manifest__.py#L10 Solution: Check if the field is present in the record before using it to ensure that "website_sale" is installed. opw-3389478 Forward-Port-Of: odoo/enterprise#43368