Wednesday, November 18, 2020
32 changes · master
Enhancements to existing features
Kanban progress bar filters now show only the records that match the selected status, making filtered views clearer and more reliable. The "Load more" count also updates correctly, so users have a more accurate view of remaining records.
Original PR description
Taskid: 2196661 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 converts many existing Odoo email templates from the older Jinja format to QWeb, Odoo’s standard template rendering approach. It helps keep email generation more consistent across apps such as accounting, CRM, calendar, HR, events, and mail, with limited direct change expected for end users.
The analytic account search filter for “doesn’t contain” now checks both the account name and code. This makes filtering results more predictable and consistent with the existing “contains” filter behavior.
Original PR description
From now on, it is possible to use the analytic account's code field in the "doesn't contain" filter. Until now, only the name of the analytic account was processed when using this filter. When using the "Contains" filter, both the name and the code of the analytic account were taken into account, which was inconsistent with how the "Doesn't contain" filter worked. Ticket #2368695 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Barcode picking screens are easier to use, with clearer product information, quantity controls kept visible, and edit actions placed closer to the quantities they affect. Warehouse users can also scan a product to quickly see its available locations and quantities, helping them work faster and with fewer mistakes.
Resolved issues and error corrections
The web editor now shows a live preview when users hover over text or background color options. This makes it easier for content editors to choose the right color before applying it, reducing trial and error.
Original PR description
Description of the issue/feature this PR addresses: The web editor offered in-content preview when hovering over a color to change text or background color. Current behavior before PR: There's no preview when hovering over a color. Desired behavior after PR is merged: This commit implements this behavior with Jabberwocky, for both background and text. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
The Expense app form is clearer by showing the right fields based on the selected product and removing an unused amount field. Employees can now submit expenses in one currency while reimbursement is handled in the company currency, with automatic conversion and the exchange rate shown for transparency.
Original PR description
[REF] Improve experience of Expense app After the changes the field untaxed_amount has not been used any more, so it was removed. In order to make the expense form more intuitive, it was necessary to distinguish between whether the product with non-zero-cost was selected on not. According to the latter, different field should be shown. Now the expense can be submitted in different currency and it can be reimbursed in company’s currency. In case the latter two currencies differ from each other, the conversion is done automatically and the rate is also displayed. Task - 2366775
Miscellaneous changes
When displaying a QR-code on the account.payment form view, we now pass its communication as both structured and unstructured communication, letting the QR-code generator parse it needed. This allows supporting QR-IBANs and QRR communications for Swiss QR-codes. Forward-Port-Of: odoo/odoo#61877
Original PR description
When displaying a QR-code on the account.payment form view, we now pass its communication as both structured and unstructured communication, letting the QR-code generator parse it needed. This allows supporting QR-IBANs and QRR communications for Swiss QR-codes. Forward-Port-Of: odoo/odoo#61877
Original PR description
Task: https://www.odoo.com/web?#id=27033&view_type=form&model=project.task&action=327&menu_id=4720 Pad: https://pad.odoo.com/p/r.8d2749de4844861078fc36312e573e48 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
The accounting expense settings now point to the correct fleet-related module after the previous module name was replaced. This prevents configuration issues caused by referencing a module that no longer exists.
Original PR description
The module fleet_account has been replaced by account_disallowed_expenses_fleet in https://github.com/odoo/odoo/commit/db9da432b7aedcd1bc944e23e59459c9c92801b7 opw:2382169
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#57098
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 Forward-Port-Of: odoo/odoo#57098
Inside project module view file in drive spreedsheet icon was broken in portal In project_portal_templates.xml this file i changed xml code to show proper icon and show icon in proper provided space task-id:2337684 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60368
Original PR description
Inside project module view file in drive spreedsheet icon was broken in portal In project_portal_templates.xml this file i changed xml code to show proper icon and show icon in proper provided space task-id:2337684 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60368
Currently, when go to calendar > list view > action > send sms to attendees, it will generate the the traceback because default composition_mode is comment while when you process through the list then sms_composition mode should be 'mass'. So in this commit, pass the sms_composition_mode as 'guess' so it will automatically check the record and take the correct composition mode and also pass the active_ids as res_ids. TaskID: 2344284 -- I confirm I have signed the CLA and read the
Original PR description
Currently, when go to calendar > list view > action > send sms to attendees, it will generate the the traceback because default composition_mode is comment while when you process through the list then sms_composition mode should be 'mass'. So in this commit, pass the sms_composition_mode as 'guess' so it will automatically check the record and take the correct composition mode and also pass the active_ids as res_ids. TaskID: 2344284 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60330
Currently, When try to open "every one" menu from time off and add "timezone" , it show traceback. So in this commit, fix the issue of when try to open "every one" menu from time off and add "timezone". Task ID: 2334866 Closes: 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#57597
Original PR description
Currently, When try to open "every one" menu from time off and add "timezone" , it show traceback. So in this commit, fix the issue of when try to open "every one" menu from time off and add "timezone". Task ID: 2334866 Closes: 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#57597
Removed all the settings related to billable projects in the quick create dialog. There were too many settings which slowed down the quick creation of a project. TaskID: 2376401 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#61568
Original PR description
Removed all the settings related to billable projects in the quick create dialog. There were too many settings which slowed down the quick creation of a project. TaskID: 2376401 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#61568
Before this fix, the prefix was detected as `045-0` and the year as `1` instead of no year with prefix `045-001`. [opw-2381351](https://www.odoo.com/web#action=3530&cids=1&id=2381351&menu_id=4720&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#61882
Original PR description
Before this fix, the prefix was detected as `045-0` and the year as `1` instead of no year with prefix `045-001`. [opw-2381351](https://www.odoo.com/web#action=3530&cids=1&id=2381351&menu_id=4720&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#61882
Some projects may not need the tags, while others use the state heavily. This makes both fields available and optional. 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#61924
Original PR description
Some projects may not need the tags, while others use the state heavily. This makes both fields available and optional. 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#61924
When a session is created and due to bad config, they cannot create pos orders. You should be able to close it. 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#61933
Original PR description
When a session is created and due to bad config, they cannot create pos orders. You should be able to close it. 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#61933
Steps to reproduce the bug: - Delete the current website - Go to homepage Bug: An error 500 was displayrd opw:2381929 Forward-Port-Of: odoo/odoo#61849 Forward-Port-Of: odoo/odoo#61767
Original PR description
Steps to reproduce the bug: - Delete the current website - Go to homepage Bug: An error 500 was displayrd opw:2381929 Forward-Port-Of: odoo/odoo#61849 Forward-Port-Of: odoo/odoo#61767
This change highlighted issues with the async behavior of `useUpdate`, which was no longer necessary and therefore reverted. This in turn highlighted issue with animation of chat window unfolding, making restoring of scroll position not work as intended due to the message list not having its whole height available during some time after render. This animation being minor (and even annoying in some cases) it was decided to remove it. task-2387729 Forward-Port-Of: odoo/odoo#61881
Original PR description
This change highlighted issues with the async behavior of `useUpdate`, which was no longer necessary and therefore reverted. This in turn highlighted issue with animation of chat window unfolding, making restoring of scroll position not work as intended due to the message list not having its whole height available during some time after render. This animation being minor (and even annoying in some cases) it was decided to remove it. task-2387729 Forward-Port-Of: odoo/odoo#61881
In previous versions of Odoo, in the New message box, tying a few letters of the name of your recipient and pressing Enter would automatically select the conversation with this contact. Since 14.0, it is required to select the first result with the Down key. This commit restores the previous behavior by using the [`autofocus`](https://api.jqueryui.com/autocomplete/#option-autoFocus) option. Forward-Port-Of: odoo/odoo#61886
Original PR description
In previous versions of Odoo, in the New message box, tying a few letters of the name of your recipient and pressing Enter would automatically select the conversation with this contact. Since 14.0, it is required to select the first result with the Down key. This commit restores the previous behavior by using the [`autofocus`](https://api.jqueryui.com/autocomplete/#option-autoFocus) option. Forward-Port-Of: odoo/odoo#61886
Task-2388565 Forward-Port-Of: odoo/odoo#61951
Original PR description
Task-2388565 Forward-Port-Of: odoo/odoo#61951
The module does not contain the new intrastat codes (year 2020). This commit adds them to the appropriate file. OPW-2381152 Forward-Port-Of: odoo/enterprise#14834
Original PR description
The module does not contain the new intrastat codes (year 2020). This commit adds them to the appropriate file. OPW-2381152 Forward-Port-Of: odoo/enterprise#14834
…ange Forward-Port-Of: odoo/enterprise#14833
Original PR description
…ange Forward-Port-Of: odoo/enterprise#14833
[FIX] editable prefilled values by employee in sign In contract the form values which the employee provided in the salary configurator were set as pre-filled fields for the employee contract, which were editable. In this commit those pre-filled values of the employee contract are made non-editable. **TaskID**: 2365544 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#14581
Original PR description
[FIX] editable prefilled values by employee in sign
In contract the form values which the employee provided in the salary configurator were set as pre-filled fields for the employee contract, which were editable.
In this commit those pre-filled values of the employee contract are made non-editable.
**TaskID**: 2365544
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/enterprise#14581WHY: the value is not used when payment_mode == 'success_payment': https://github.com/odoo/enterprise/blob/57a848c8137d8d78c4c8f3685d1911cb36d07cdc/sale_subscription/models/sale_subscription.py#L940-L952 https://github.com/odoo/enterprise/blob/57a848c8137d8d78c4c8f3685d1911cb36d07cdc/sale_subscription/models/sale_subscription.py#L818-L819 https://github.com/odoo/enterprise/blob/57a848c8137d8d78c4c8f3685d1911cb36d07cdc/sale_subscription/models/sale_subscription.py#L901-L902 --- opw
Original PR description
WHY: the value is not used when payment_mode == 'success_payment': https://github.com/odoo/enterprise/blob/57a848c8137d8d78c4c8f3685d1911cb36d07cdc/sale_subscription/models/sale_subscription.py#L940-L952 https://github.com/odoo/enterprise/blob/57a848c8137d8d78c4c8f3685d1911cb36d07cdc/sale_subscription/models/sale_subscription.py#L818-L819 https://github.com/odoo/enterprise/blob/57a848c8137d8d78c4c8f3685d1911cb36d07cdc/sale_subscription/models/sale_subscription.py#L901-L902 --- opw-2372015 Forward-Port-Of: odoo/enterprise#14756
When the user clicks on a {date|datetime} field in the mobile app, the native datepicker should be presented instead of the JS Tempusdominus datepicker. Before this commit both are shown (the JS one partially hidden behind the native one). This commit fixes this by properly overriding the method `_onInputClicked` when the native datepicker is available to prevent from calling the `$.datetimepicker()` plugin. Note: to introduce appropriate tests for the FieldDate and FieldDateTime
Original PR description
When the user clicks on a {date|datetime} field in the mobile app, the
native datepicker should be presented instead of the JS Tempusdominus
datepicker.
Before this commit both are shown (the JS one partially hidden behind
the native one).
This commit fixes this by properly overriding the method
`_onInputClicked` when the native datepicker is available to prevent
from calling the `$.datetimepicker()` plugin.
Note: to introduce appropriate tests for the FieldDate and FieldDateTime
fields in the mobile application, the check for the native datepicker
availability have to be performed at run time instead of load time ; this
allows to mock it in the tests.
Forward-Port-Of: odoo/enterprise#14783
Forward-Port-Of: odoo/enterprise#14746**PURPOSE** Provide Better UI for employee contract form view. **SPECIFICATION** Set 'contract_template' group inside group tag to provide better UI **LINKS** PR https://github.com/odoo/enterprise/pull/12686 Task-2325593 Forward-Port-Of: odoo/enterprise#12686
Original PR description
**PURPOSE** Provide Better UI for employee contract form view. **SPECIFICATION** Set 'contract_template' group inside group tag to provide better UI **LINKS** PR https://github.com/odoo/enterprise/pull/12686 Task-2325593 Forward-Port-Of: odoo/enterprise#12686
…op computation hr_work_entry_contract overrides _inverse_duration to do stuff, and calls super but method has been removed from hr_work_entry. hr_work_entry._inverse_duration was removed and its body, or something equivalent, was moved to a new method hr_work_entry._compute_date_stop, this commit replaces hr_work_entry_contract._inverse_duration with an override of the _compute_date_stop method, the call to super is preserved but now the parent method exists. task: 2285889 related: o
Original PR description
…op computation hr_work_entry_contract overrides _inverse_duration to do stuff, and calls super but method has been removed from hr_work_entry. hr_work_entry._inverse_duration was removed and its body, or something equivalent, was moved to a new method hr_work_entry._compute_date_stop, this commit replaces hr_work_entry_contract._inverse_duration with an override of the _compute_date_stop method, the call to super is preserved but now the parent method exists. task: 2285889 related: odoo/odoo/commit/3bd345597fa932abdaf780f72bacf331690f549b Forward-Port-Of: odoo/enterprise#14203
When you apply an action having as create_model "Create signature request" or "Sign directly", the name of the document is changed. Removed this issue. Task-2356951 Forward-Port-Of: odoo/enterprise#14819
Original PR description
When you apply an action having as create_model "Create signature request" or "Sign directly", the name of the document is changed. Removed this issue. Task-2356951 Forward-Port-Of: odoo/enterprise#14819
Current behavior before PR: When Role Color was not defined, the progress bar was not displayed. Because the default color is 0 and it has no color that's why we can't see any difference in the progress bar. Desired behavior after PR is merged: When Role Color was not defined, the progress bar is displayed. LINKS PR https://github.com/odoo/enterprise/pull/14392 Task-2359038 Forward-Port-Of: odoo/enterprise#14392
Original PR description
Current behavior before PR: When Role Color was not defined, the progress bar was not displayed. Because the default color is 0 and it has no color that's why we can't see any difference in the progress bar. Desired behavior after PR is merged: When Role Color was not defined, the progress bar is displayed. LINKS PR https://github.com/odoo/enterprise/pull/14392 Task-2359038 Forward-Port-Of: odoo/enterprise#14392
Current behavior before PR: The signed template with an "Activity Logs" name. Desired behavior after PR is merged: The signed template with a "Certificate of completion" name. LINKS PR https://github.com/odoo/enterprise/pull/14464 Task-2350005 Forward-Port-Of: odoo/enterprise#14464
Original PR description
Current behavior before PR: The signed template with an "Activity Logs" name. Desired behavior after PR is merged: The signed template with a "Certificate of completion" name. LINKS PR https://github.com/odoo/enterprise/pull/14464 Task-2350005 Forward-Port-Of: odoo/enterprise#14464
https://github.com/odoo/enterprise/commit/419f7f801717827aa8d51aeb781080cf4511b066 reverted the taxes on the sale_subscription and reccuring_total has been removed from the list views. This commit renable display of the recurring_total. taskid: 2344456 Forward-Port-Of: odoo/enterprise#13552
Original PR description
https://github.com/odoo/enterprise/commit/419f7f801717827aa8d51aeb781080cf4511b066 reverted the taxes on the sale_subscription and reccuring_total has been removed from the list views. This commit renable display of the recurring_total. taskid: 2344456 Forward-Port-Of: odoo/enterprise#13552
When confirming a SO with a subscription product, if there are several companies, the system uses the subscription product configuration of each company to compute the tax of the product. To reproduce the error: 1. Have two companies C1 and C2 2. Create one sale tax per company (taxe_C1 and taxe_C2) Both taxes must be included in price 3. With C1, configure a product - Must be a subscription product - Add the taxe_C1 to the customer taxes field 4. With C2, reconfigure this produ
Original PR description
When confirming a SO with a subscription product, if there are several companies, the system uses the subscription product configuration of each company to compute the tax of the product. To…
When confirming a SO with a subscription product, if there are several companies, the system uses the subscription product configuration of each company to compute the tax of the product. To reproduce the error: 1. Have two companies C1 and C2 2. Create one sale tax per company (taxe_C1 and taxe_C2) Both taxes must be included in price 3. With C1, configure a product - Must be a subscription product - Add the taxe_C1 to the customer taxes field 4. With C2, reconfigure this product - Set the taxe_C2 to the customer taxes field 5. Create a quotation and add the product (The system will automatically add the correct tax, as configured) 6. Save & Confirm 7. Look at the subtotal of the product, then open the generated subscription and check the subtotal of the product => The subtotals are different: in the subscription form, the system used the taxes of both companies to compute the product price This fix forces the system to compute the price using the correct company's taxe OPW-2375779 Forward-Port-Of: odoo/enterprise#14796 Forward-Port-Of: odoo/enterprise#14724