Odoo Changelog — 2021-05-03

Monday, May 3, 2021

37 changes · master

Improvements(8)

Enhancements to existing features

[IMP] web: allow lazy-loading asset bundles' templates

CoremasterwebMedium

The web interface can now load complete groups of templates in one request instead of fetching individual files. This improves efficiency for parts of Odoo that load on demand and ensures template customizations are applied consistently.

Original PR description

Previously, lazy-loading xml templates was only possible by fetching the
xml file directly, this meant that it was impossible to lazy-load an
entire bundle's templates with a single request. Additionally,
requesting the xml files directly meant that no inheritance was applied,
causing the need for a separate inheritance system using t-jquery on the
client-side.

This commit alters the /web/webclient/qweb route so that it now takes an
optional bundle id, meaning that it is now possible to lazy-load the xml
from arbitrary bundles.

task-2497943

#lazy loading#templates#web performance

[IMP] Base: specify placeholder for company partners

PR #68994

Coremasterbase

When an individual contact is linked to a company but has no company image set, the contact card now shows a company-style placeholder instead of a generic camera icon. This makes company-related contacts easier to recognize visually and improves consistency in the contact overview.

Original PR description

taskid: 2491161

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

#contacts#company#placeholder#kanban

[IMP] project: generic improvement for project configuration

PR #69636

CoremasterprojectgamificationMedium

Project configuration screens were made easier to use with clearer labels, better field placement, and updated helper text for stages and tags. These changes help users manage task stages and categorize work more efficiently, while also cleaning up unused styling.

Original PR description

Purpose of the task is to do a generic UX improvement in project Specification: -------------- 1) Stages(project.task.type) * List view: - move the 'folded in kanban' field to the right of the…

Purpose of the task is to do a generic UX improvement in project

Specification:
--------------
1) Stages(project.task.type)

* List view:
  - move the 'folded in kanban' field to the right of the project_ids one
  - remove the description field from the list view
  - make the list view editable in batch
* Form view:
  - rename 'stage name' into 'name'
  - move the sequence field below the 'rating email template' one
  - change the copy of the tooltips to: "At each stage, employees can block tasks or mark them as ready for the next step. You can customize here the labels for each state."
  - the tags should be colored according to the project's color
  - reduce the space in between the icons and the name of the states
  - add some space in between the legend_done field and the description
  - when creating a new mail template, set 'project.task' as model_id of the template
* move the 'Stages' menu into below the 'Projects' one
* add the project_ids field to the kanban view
* search: rename 'Tasks Stages' into 'Name'

2) Tags(project.tags):

- configuration > tags menu: change the helper to: "Tags are perfect for categorizing your tasks."
- add an optional list view -> only the color field should be optional and displayed by default
- new tags should be created at the top of the list

- Also removed some of the unused(deprecated) css which are not applied anywhere in the project.

TaskID: 2508642

[IMP] mail: flag JS "on change" fields as such

PR #70204

CoremastermailMedium

This change improves how Odoo Mail processes automatic field updates so required-field checks happen at the right time. It reduces false validation errors and avoids unnecessary checks on records removed during the same update cycle, making mail-related interactions more reliable.

Original PR description

There is currently a limitation with required fields because an "on change"
compute might trigger the check for "required" before all the actual computes
have been done, leading to the required field check incorrectly failing.

The main goal is to ensure the "on change" computes are done after all the other
computes and after the check for required fields.

A check has also been added to ensure no "real" compute can trigger update cycle
side-effects anymore.

Opportunity is also taken to prevent from checking for required fields on a
record that was deleted as part of the same update cycle.

Somewhat part of task-2278551

#mail#validation#reliability

[IMP] core: speed up registry setup

PR #69924

Coremasteraccountanalyticbase_sparse_fieldcrmhrhr_org_charthr_timesheetproductprojectsale_projectstockwebsitewebsite_livechatbaseMedium

Odoo’s internal registry setup was optimized so servers can start faster, especially when many modules are installed. The change reduces repeated setup work across registries and improves bootstrapping time, while keeping behavior largely unchanged for business users.

[IMP] mail: add update command and use it on thread viewer

PR #70251

Coremastermail

The mail app now handles thread viewer updates through each related model rather than relying on many shared dependencies. This makes the thread viewing experience easier to maintain and adapt across different areas of Odoo, with minimal direct impact on end users.

Original PR description

Instead of thread viewer having many dependencies, this allows models "having
the thread viewer feature" to keep their own logic for themselves.

The "create or update" part has to be done manually in this case (as opposed to
using "insert") because thread viewer has no clear identifying data, since it
would depend on which model is using it in the first place.

#mail#thread viewer#maintainability

[IMP] core: speed up registry setup

PR #17963

Enterprisemasteraccount_assetmarketing_automationsocial

This update supports faster setup of core system components by making some internal field behavior explicit. It helps improve reliability during system startup and module loading, with no expected day-to-day workflow changes for users.

Original PR description

Companion of https://github.com/odoo/odoo/pull/69924.

#performance#registry#setup#reliability

[IMP] helpdesk: improve the helpdesk stages form view

PR #17865

Enterprisemasterhelpdesk

The Helpdesk stage form now aligns its legend fields more consistently, matching the layout used in project stages. This makes the configuration screen cleaner and easier for users to read without changing any underlying helpdesk behavior.

Original PR description

Currently, in the helpdesk stages legend_* fields are not properly aligned.

so in this commit, align the legend fields on helpdesk stage same as aligned in the project stages.

TaskID: 2508642

#helpdesk#user interface#stage configuration

Bug Fixes(4)

Resolved issues and error corrections

[FIX] Calendar: fix avatar preview on hover

PR #69139

Coremasterweb

Fixed an issue in the Calendar view where hovering over a responsible person could show a default camera image instead of the correct avatar. This restores the expected visual preview and helps users quickly identify people in the calendar sidebar.

Original PR description

delete redundant '}' added by another developer by accident

taskid: 2504659

#calendar#avatars#hover#user interface

[FIX] project : onboarding tour message name

PR #70219

Other(25)

Miscellaneous changes

[FIX] web: js_transpiler accepts object exports containing comments

PR #69407

Coremasterweb

Documents a known limitation in Odoo's web JavaScript tooling around exported objects that contain comments. This helps developers avoid patterns that can cause generated code to be incorrect, reducing troubleshooting time for web customizations.

Original PR description

Before this commit, the js_transpiler did not convert object exports containing a comment. This commit will modify the regex EXPORT_OBJECT_RE and EXPORT_FROM_RE so that they match all characters…

Before this commit, the js_transpiler did not convert object exports
containing a comment.

This commit will modify the regex EXPORT_OBJECT_RE and EXPORT_FROM_RE
so that they match all characters between { and }.

Example:
```js
export {
    a // this is a comment
}

export {
    a // this is a comment
}
```

Output before this commit (no modification is applied)
```js
export {
    a // this is a comment
}

export {
    a // this is a comment
} from "@addon/path"
```

Output after this commit

```js
Object.assign(__exports, {
        a // this is a comment
        })

{const {
        a // this is a comment
        } = require("@addon/path");Object.assign(__exports, {
        a // this is a comment
        })};
```

Limitation:
It is still impossible to have a comment containing `}` inside
an exported object. The js_tranpiler will generate wrong code
if this happens.

Example:
```js
export {
    a // this is a comment with }
}
```

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

Previously, lazy-loading xml templates was only possible by fetching the xml file directly, this meant that it was impossible to lazy-load an entire bundle's templates with a single request. Additionally, requesting the xml files directly meant that no inheritance was applied, causing the need for a separate inheritance system using t-jquery on the client-side. This commit alters the /web/webclient/qweb route so that it now takes an optional bundle id, meaning that it is now possible to lazy-load the xml from arbitrary bundles. task-2497943

taskid: 2491161 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

Purpose of the task is to do a generic UX improvement in project Specification: -------------- 1) Stages(project.task.type) * List view: - move the 'folded in kanban' field to the right of the project_ids one - remove the description field from the list view - make the list view editable in batch * Form view: - rename 'stage name' into 'name' - move the sequence field below the 'rating email template' one - change the copy of the tooltips to: "At each stage, employees can block tasks or mark them as ready for the next step. You can customize here the labels for each state." - the tags should be colored according to the project's color - reduce the space in between the icons and the name of the states - add some space in between the legend_done field and the description - when creating a new mail template, set 'project.task' as model_id of the template * move the 'Stages' menu into below the 'Projects' one * add the project_ids field to the kanban view * search: rename 'Tasks Stages' into 'Name' 2) Tags(project.tags): - configuration > tags menu: change the helper to: "Tags are perfect for categorizing your tasks." - add an optional list view -> only the color field should be optional and displayed by default - new tags should be created at the top of the list - Also removed some of the unused(deprecated) css which are not applied anywhere in the project. TaskID: 2508642

There is currently a limitation with required fields because an "on change" compute might trigger the check for "required" before all the actual computes have been done, leading to the required field check incorrectly failing. The main goal is to ensure the "on change" computes are done after all the other computes and after the check for required fields. A check has also been added to ensure no "real" compute can trigger update cycle side-effects anymore. Opportunity is also taken to prevent from checking for required fields on a record that was deleted as part of the same update cycle. Somewhat part of task-2278551

Instead of thread viewer having many dependencies, this allows models "having the thread viewer feature" to keep their own logic for themselves. The "create or update" part has to be done manually in this case (as opposed to using "insert") because thread viewer has no clear identifying data, since it would depend on which model is using it in the first place.

Before this commit, the js_transpiler did not convert object exports containing a comment. This commit will modify the regex EXPORT_OBJECT_RE and EXPORT_FROM_RE so that they match all characters between { and }. Example: ```js export { a // this is a comment } export { a // this is a comment } ``` Output before this commit (no modification is applied) ```js export { a // this is a comment } export { a // this is a comment } from "@addon/path" ``` Output after this commit ```js Object.assign(__exports, { a // this is a comment }) {const { a // this is a comment } = require("@addon/path");Object.assign(__exports, { a // this is a comment })}; ``` Limitation: It is still impossible to have a comment containing `}` inside an exported object. The js_tranpiler will generate wrong code if this happens. Example: ```js export { a // this is a comment with } } ``` 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

Previously, when toggling on background shapes, they always had the default colours. In 1e30bce81eb8deb732747f8964ebd7fcd78c802c we made it so that when you toggle on a shape on a section, it would automatically reuse the colors of the surrounding shapes if any. Unfortunately, when the "implicit" colors were also the default colors, they were still marked on the shape, and it got an explicit background image that would no longer react to changes in the palette. This was caused by the fact that the call to _getDefaultColors returns an empty object when the section doesn't already have a shape-container, this was not a problem before since we were not passing in any colors when creating the initial shape previously, the the aforementioned change made it so that we did. This commit fixes the issue by creating the shape-container before calling the method that will set the colors on the shape, this way getDefaultColors works as expected, and the colors are not marked on the section when they are the default ones, restoring the ability of the shape colors to adapt to the palette task-2500607 Co-authored-by: Tom De Caluwé <tdc@odoo.com> Forward-Port-Of: odoo/odoo#68893

When changing the product price precision, this can lead to incorrect stock valuations. To reproduce the error: (Enable debug mode) 1. Go to Settings > Technical > Database Strucutre > Decimal Accuracy 2. Edit Product Price: - Digits: 4 3. Create a Product Category PC: - Costing Method: FIFO 4. Create a Product P: - Product Type: Storable Product - Product Category: PC 5. Create a RfQ with product P: - Quantity: 1000 - Unit Price: 0.035 6. Confirm Order, Receive Products, Validate 7. Click on Valuation Error: The total value is equal to $40 instead of $35. The calculation was done after rounding the unit price: $0.035 becomes $0.04, then 1000*0.04=$40. When confirming the RfQ, a stock move is created. To do so, the method `_get_stock_move_price_unit` is called. When validating the delivery, it recomputes the unit price thanks to method `_get_price_unit`. In both situation, and if the line has taxes, the method `compute_all` is called like this: ```python price_unit = line.taxes_id.with_context(round=False).compute_all(price_unit, currency=line.order_id.currency_id, quantity=1.0)['total_void'] ``` But here is the problem. In this method, total amount is computed with this line: ```python base = currency.round(price_unit * quantity) ``` However, `quantity` is equal to 1 and the multiplication is rounded using the currency precision. As a result, `base` is equal to $0.04. Then, all computations will use this value and will be incorrect. This fix applies the real quantity so `base` will have the correct value: ``` base = currency.round(price_unit * quantity) = currency.round(0.035 * 1000) = 35 ``` OPW-2472192 Forward-Port-Of: odoo/odoo#70080 Forward-Port-Of: odoo/odoo#69297

Improvements(8)

[IMP] web: allow lazy-loading asset bundles' templates

[IMP] Base: specify placeholder for company partners

[IMP] project: generic improvement for project configuration

[IMP] mail: flag JS "on change" fields as such

[IMP] core: speed up registry setup

[IMP] mail: add update command and use it on thread viewer

[IMP] core: speed up registry setup

[IMP] helpdesk: improve the helpdesk stages form view

Bug Fixes(4)

[FIX] Calendar: fix avatar preview on hover

[FIX] project : onboarding tour message name

Other(25)

[FIX] web: js_transpiler accepts object exports containing comments

Improvements(8)

[IMP] web: allow lazy-loading asset bundles' templates

[IMP] Base: specify placeholder for company partners

[IMP] project: generic improvement for project configuration

[IMP] mail: flag JS "on change" fields as such

[IMP] core: speed up registry setup

[IMP] mail: add update command and use it on thread viewer

[IMP] core: speed up registry setup

[IMP] helpdesk: improve the helpdesk stages form view

Bug Fixes(4)

[FIX] Calendar: fix avatar preview on hover

[FIX] project : onboarding tour message name

Other(25)

[FIX] web: js_transpiler accepts object exports containing comments

[MERGE] helpdesk_sale_timesheet: code cleaning

[FIX] hide optionalColumnsDropdown for signer_ids

[FW][FIX] l10n_in: Set automatically GST Treatment on invoice creation

[FW][FIX] web_editor, note: autofocus the editor on load note form view edit

[FW][FIX]repair: fix invoice deletion

[FW][FIX] stock: allow destination address change in transfer

[FW][FIX] sale_margin: avoid purchase price reset on order confirm

[FW][FIX] l10n_fr: assets update on account.account.template.csv

[FW][FIX] mrp: suggest the qty to produce instead of 0 in workorders

[FW][FIX] web_editor: update toolbar position on scroll

[FW][FIX] web_editor: fix default shapes not reacting to palette changes

[FW][FIX] stock : wrong float_compare

[FW][FIX] mrp: allow to select product w/o bom

[FW][FIX] stock_landed_costs: use the correct split method landed cost

[FW][FIX] point_of_sale: use lot's location for SML's location source

[FW][IMP] website: change some wordings in configurator features screen

[FW][FIX] crm: display right partner and action when convert lead

[FW][FIX] web_editor, *: remove some post new editor dead code

[FW][FIX] website: hide the cookie bar when entering edit mode

[FW][FIX] purchase_stock: consider product unit price precision

[FW][FIX] l10n_cl_edi: change dte template to include withholding taxes

[FW][FIX] account_reports: Traceback Trial Balance + Filter Hierarchy

[FW][FIX] mrp_workorder: pre-fill the qty to produce instead of 0

[FW]14.0 frupdate jco

[FW][FIX] delivery_dhl: make use of partner shipping address

[FW][FIX] industry_fsm_sale: compute bad amount in so when task mark as done