Monday, November 2, 2020
40 changes · master
Enhancements to existing features
The partner commission test setup now uses a unique journal code to align with updated accounting validation rules. This keeps automated checks reliable and helps prevent false failures during ongoing development.
Original PR description
Following the changes introduced by https://github.com/odoo/odoo/pull/59791 for task 2346404. This journal code was already used elsewhere in the tests, so we simply replace it by a unique one.
The module description now clarifies when landed costs can be applied in Mexican electronic invoicing workflows. This helps users understand that landed costs require FIFO or AVCO costing and automated inventory valuation before setup or use.
Original PR description
Landed costs can only be applied to products with a FIFO or AVCO costing methods and an automated inventory valuation.
Resolved issues and error corrections
This fixes an issue where users could not see the link and media buttons in the forum editor. Restoring these controls makes it easier for forum contributors to add richer content without workarounds.
Original PR description
I faced this issue in odoo 13 and this fix is working so I think it will also work in master. Description of the issue/feature this PR addresses: Currently in forum wysiwyg editor, link and media buttons are not visible. Current behavior before PR: In forum wysiwyg editor, link and media buttons are not visible. Desired behavior after PR is merged: In forum wysiwyg editor, link and media buttons will be visible. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
This update simplifies how the website editor applies visual style classes behind the scenes. It should not change how users work with the editor, but it makes the code easier to maintain and includes minor editor library fixes.
Original PR description
This helper is the equivalent of jquery's `toggleClass` with a value for the `force` attribute. I chose to name it `setClass` instead because with that attribute it's technically not toggling: it's setting. Related JW PR: https://github.com/odoo-dev/jabberwock/pull/457 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Public user by default don't have email. So when you try to subscribe to a channel in public user (portal don't receive an email), the email cannot be send and the user see a message: "Unable to post message, please configure the sender's email address. 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:
Original PR description
Public user by default don't have email. So when you try to subscribe to a channel in public user (portal don't receive an email), the email cannot be send and the user see a message: "Unable to post message, please configure the sender's email address. 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#60794
The mail app now avoids starting a second message load while one is already in progress. This helps prevent unnecessary delays, duplicate work, and possible display glitches when users open or refresh conversations.
Original PR description
task-2373952
This update removes unnecessary read-only settings from labels in the Time Off module. It does not change how employees or managers use the system, but it makes the underlying configuration clearer and easier to maintain.
Original PR description
WHY: it's a copy-paste mistake and doesn't have any meaning, while makes code less readable 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
Steps to reproduce the bug: - Create a vendor bill VB1 with one line L1 - Set an analytic account AA on L1 - Post VB1 - Create a new vendor bill VB2 - Set VB1 on the field Auto-complete Bug: The created line L2 on VB2 had no analytic account PS: In 12.0, the analytic account was kept when using Auto-complete field opw:2359432 Forward-Port-Of: odoo/odoo#60497 Forward-Port-Of: odoo/odoo#60433
Original PR description
Steps to reproduce the bug: - Create a vendor bill VB1 with one line L1 - Set an analytic account AA on L1 - Post VB1 - Create a new vendor bill VB2 - Set VB1 on the field Auto-complete Bug: The created line L2 on VB2 had no analytic account PS: In 12.0, the analytic account was kept when using Auto-complete field opw:2359432 Forward-Port-Of: odoo/odoo#60497 Forward-Port-Of: odoo/odoo#60433
WHY: * float_is_zero doesn't work without second argument https://github.com/odoo/odoo/blob/c90427dfba26854cda5d54f813cccc4948685077/addons/web/static/src/js/core/utils.js#L59-L62 * the fixed line of code was introduced in #60642 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#61036 Forwa
Original PR description
WHY: * float_is_zero doesn't work without second argument https://github.com/odoo/odoo/blob/c90427dfba26854cda5d54f813cccc4948685077/addons/web/static/src/js/core/utils.js#L59-L62 * the fixed line of code was introduced in #60642 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#61036 Forward-Port-Of: odoo/odoo#61006
The xpath branding of a node which followed a t-field node which was added by an inheritance view was not correct. E.g. View 1: ```xml <hello> <world id="1"></world> <world t-field="a"/> <world id="2"></world> <world id="3"></world> </hello> ``` View 2 inheriting view 1: ```xml <xpath expr="/hello/world[3]" position="after"> <world t-field="b"/> </xpath> ``` So the result is: ```xml <hello> <world id="1"></world> <world t-field="a"/> <w
Original PR description
The xpath branding of a node which followed a t-field node which was added by an inheritance view was not correct. E.g. View 1: ```xml <hello> <world id="1"></world> <world t-field="a"/> <world…
The xpath branding of a node which followed a t-field node which was
added by an inheritance view was not correct. E.g.
View 1:
```xml
<hello>
<world id="1"></world>
<world t-field="a"/>
<world id="2"></world>
<world id="3"></world>
</hello>
```
View 2 inheriting view 1:
```xml
<xpath expr="/hello/world[3]" position="after">
<world t-field="b"/>
</xpath>
```
So the result is:
```xml
<hello>
<world id="1"></world>
<world t-field="a"/>
<world id="2"></world>
<world t-field="b"/>
<world id="3"></world>
</hello>
```
Now the xpath branding of world id="2" was `/hello[1]/world[3]`, which
is correct.
But the xpath branding of world id="3" was `/hello[1]/world[5]` which is
incorrect as it should be `/hello[1]/world[4]` (as related to the
original view). This was because inherited t-field did not carry any
information they came from inheritance (as "normal" nodes would).
The side effect of this was that the incorrectly marked node was not
possible to edit (and made the editor crash on save).
Closes 51885
Forward-Port-Of: odoo/odoo#60935
Forward-Port-Of: odoo/odoo#60894Update Arxilead CLA Forward-Port-Of: odoo/odoo#60649
Original PR description
Update Arxilead CLA Forward-Port-Of: odoo/odoo#60649
Before this commit, the parameter for user filters was not kept in the url when navigating with the pager. ISSUE 56248 task-2369420 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#60888
Original PR description
Before this commit, the parameter for user filters was not kept in the url when navigating with the pager. ISSUE 56248 task-2369420 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#60888
Description of the issue/feature this PR addresses: 1. Lead to loose the tour: Remove the step of the tour that asks to set an address (the address is auto-completed at free trial based on domain name) 2. Bug: At step 3, it redirects to the invoice settings to select a localization, when you click on "install more packages", you are sent back to the sales app. 3. Bug: Tour blocks at last step "send by email" on quotation. After clicking on "sent" on the pop-up, there should be rainbow
Original PR description
Description of the issue/feature this PR addresses: 1. Lead to loose the tour: Remove the step of the tour that asks to set an address (the address is auto-completed at free trial based on domain name) 2. Bug: At step 3, it redirects to the invoice settings to select a localization, when you click on "install more packages", you are sent back to the sales app. 3. Bug: Tour blocks at last step "send by email" on quotation. After clicking on "sent" on the pop-up, there should be rainbow effect to mark the end of the tour. 4. Bug: Sale order line: fix the blue color on Invoiced Quantity only, instead of the full line 5. Put the "sample product" in active= false (it's necessary for the sample invoice but should not be visible to the user, they should create their own) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54134
Before this commit, link and media buttons of the wysiwyg editor toolbar in the forum were never displayed. It's because we were not using the right option names in the toolbar object. PR 53589 task-2369420 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#60897
Original PR description
Before this commit, link and media buttons of the wysiwyg editor toolbar in the forum were never displayed. It's because we were not using the right option names in the toolbar object. PR 53589 task-2369420 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#60897
Behavior prior to this commit: In a multi-lingual setup, when entering a SO for a customer set in a non-default language with a product that has translation in both languages and is set up to replenish on order, the description in the generated RFQ is duplicated, for example: "Product test Test Product in Dutch" The problem stems from the fact that the description on the generated stock move is set to the translated name of the product. When generating the PO, the stock move class re
Original PR description
Behavior prior to this commit: In a multi-lingual setup, when entering a SO for a customer set in a non-default language with a product that has translation in both languages and is set up to replenish on order, the description in the generated RFQ is duplicated, for example: "Product test Test Product in Dutch" The problem stems from the fact that the description on the generated stock move is set to the translated name of the product. When generating the PO, the stock move class removes the product name to avoid duplicating the description, but it uses the non-translated name in the comparison. Behavior after this commit: The description on the RFQ line is included only once (using the default language for the database) opw-2368562 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61040
The pricelist item model (product.pricelist.item) has a compute_price field, and the necessary fields to be able to compute the price of a product. However, these fields are never used into the model itself; the parent model (product.pricelist) actually makes the computation, embedded into _compute_price_rule. Because of this, it's not possible to inherit pricelist items. It's also a better design, on object principles. Last, it lighten a method that is still 130+ lines long. Additiona
Original PR description
The pricelist item model (product.pricelist.item) has a compute_price field, and the necessary fields to be able to compute the price of a product. However, these fields are never used into the model itself; the parent model (product.pricelist) actually makes the computation, embedded into _compute_price_rule. Because of this, it's not possible to inherit pricelist items. It's also a better design, on object principles. Last, it lighten a method that is still 130+ lines long. Additional splittings of the method have been done in upper versions of Odoo; and forward-port up to master is almost trivial. With this, it will be possible to override the pricelist items to implement more complex pricing strategies (tiered or volume pricing) opw 2368733 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60519
Issue Partner not found if multiple breakline in message. Cause '\n' not replaced by '\n ' globaly. '<br/>' not replaced by '<br/> ' globaly. Fix of this commit : https://github.com/odoo/odoo/commit/902302598e98efab52d61979e85def6d025ff2ab opw-2322577 Forward-Port-Of: odoo/odoo#61119
Original PR description
Issue
Partner not found if multiple breakline in message.
Cause
'\n' not replaced by '\n ' globaly.
'<br/>' not replaced by '<br/> ' globaly.
Fix of this commit : https://github.com/odoo/odoo/commit/902302598e98efab52d61979e85def6d025ff2ab
opw-2322577
Forward-Port-Of: odoo/odoo#61119Issue - Install 'eLearning' module - Go to 'Course' page on website - Open any course and click on 'Review' tab Rating star numbers are 2,4,6,8 & 10. Cause Since this commit https://github.com/odoo/odoo/commit/e4a4ffb974ccde1842e1b2389450718f8576ad5b, odoo use a system of 5 stars instead of 10. opw-2373115 Forward-Port-Of: odoo/odoo#61130
Original PR description
Issue - Install 'eLearning' module - Go to 'Course' page on website - Open any course and click on 'Review' tab Rating star numbers are 2,4,6,8 & 10. Cause Since this commit https://github.com/odoo/odoo/commit/e4a4ffb974ccde1842e1b2389450718f8576ad5b, odoo use a system of 5 stars instead of 10. opw-2373115 Forward-Port-Of: odoo/odoo#61130
Consider some model A that "_inherits" from model B, which itself "_inherits" from model C. Also consider a field F on model C, which is inherited by both models B and A. Now create a record from model A, with a given record for model C, no record for model B, and a default value for field F. This should create a record in A, connected to a new record in B, connected to the given record in C, and the default value should be ignored, as a record from C is given. Before this commit, th
Original PR description
Consider some model A that "_inherits" from model B, which itself "_inherits" from model C. Also consider a field F on model C, which is inherited by both models B and A. Now create a record from model A, with a given record for model C, no record for model B, and a default value for field F. This should create a record in A, connected to a new record in B, connected to the given record in C, and the default value should be ignored, as a record from C is given. Before this commit, the given record in C is modified with the default value for F. The default value is considered because no record is given for B, and that value is used to modify the given record in C. The fix consists in discarding default values by considering potential ancestor records when parent records are not given. This branch is a reworked version of @danielduqma's own proposal https://github.com/odoo/odoo/pull/54413. Forward-Port-Of: odoo/odoo#61128 Forward-Port-Of: odoo/odoo#60898
Steps to reproduce the bug: - Let's consider a company contact C with two children CH1 and CH2 - Create a meeting for CH1 and a meeting for CH2 Bug: The count of meetings in C was displaying 0 instead of 2 PS: set() is used to avoid to count several times the same event for a partner. If for example CH1 and CH2 attend to the same event, only one event must be counted for the parent C opw:2360155 Forward-Port-Of: odoo/odoo#60934
Original PR description
Steps to reproduce the bug: - Let's consider a company contact C with two children CH1 and CH2 - Create a meeting for CH1 and a meeting for CH2 Bug: The count of meetings in C was displaying 0 instead of 2 PS: set() is used to avoid to count several times the same event for a partner. If for example CH1 and CH2 attend to the same event, only one event must be counted for the parent C opw:2360155 Forward-Port-Of: odoo/odoo#60934
Revert "[FIX] sale: correct _get_to_invoice_qty depends" This reverts commit cfc9abe14689db82acf1872fa8d358662fc7e123. While the field is indeed in the list of records, it's a big change of behaviour. Retroactively changing the invoicable lines of sale.order that are closed is dangerous and can lead on unexpected behaviours. Performances can also be bad when changing the product configuration on a database with a lot of sale orders. Changing the product configuration should only appl
Original PR description
Revert "[FIX] sale: correct _get_to_invoice_qty depends" This reverts commit cfc9abe14689db82acf1872fa8d358662fc7e123. While the field is indeed in the list of records, it's a big change of behaviour. Retroactively changing the invoicable lines of sale.order that are closed is dangerous and can lead on unexpected behaviours. Performances can also be bad when changing the product configuration on a database with a lot of sale orders. Changing the product configuration should only apply to future orders, not past. Forward-Port-Of: odoo/odoo#61135
Before this commit, the max height of the off canvas hamburger was the same as the standard navbar-collapse (80vh) but in the case of an off canvas hamburger menu we need a 100vh max-height to display it properly. task-2312878 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#60811
Original PR description
Before this commit, the max height of the off canvas hamburger was the same as the standard navbar-collapse (80vh) but in the case of an off canvas hamburger menu we need a 100vh max-height to display it properly. task-2312878 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#60811
The dashboard "View Statement" action on bank journals was using the `open_action` helper, but it was badly computed for journals with `bank_statements_source` set to `online_sync`. We were directed to the statement lines instead of the statements; and there was no other way to go to the list of statements. 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
Original PR description
The dashboard "View Statement" action on bank journals was using the `open_action` helper, but it was badly computed for journals with `bank_statements_source` set to `online_sync`. We were directed to the statement lines instead of the statements; and there was no other way to go to the list of statements. 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#61121
See https://github.com/odoo/odoo/pull/60083 for original story Forward-Port-Of: odoo/odoo#60906
Original PR description
See https://github.com/odoo/odoo/pull/60083 for original story Forward-Port-Of: odoo/odoo#60906
STEPS: * install hr_leaves * allocate half days leaves * start creating new time off, set [x] Half day checkbox BEFORE: there is label "Duration", but no any fields for it AFTER: hide Duration label WHY: * this bug came after improvements in https://github.com/odoo/odoo/commit/d2238de57630d58c4913ab44746476b83492c72f --- opw-2370907 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I con
Original PR description
STEPS: * install hr_leaves * allocate half days leaves * start creating new time off, set [x] Half day checkbox BEFORE: there is label "Duration", but no any fields for it AFTER: hide Duration label WHY: * this bug came after improvements in https://github.com/odoo/odoo/commit/d2238de57630d58c4913ab44746476b83492c72f --- opw-2370907 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#61088
Open POS Config Enable the option 'Connect Devices' In 'Epson Receipt Printer IP Address' write anything then focus out Enable the 'Cashdrawer' Option Empty 'Epson Receipt Printer IP Address' Disable'Connect Devices' Save Disabling 'Connect Devices' while leaving 'Cashdrawer' enabled will lead to crash during the payment session if the user click on 'Open Cashbox' when using cash as a payment method. After disabling the 'Connect Devices' the 'Cashdrawer' should be disabled automa
Original PR description
Open POS Config Enable the option 'Connect Devices' In 'Epson Receipt Printer IP Address' write anything then focus out Enable the 'Cashdrawer' Option Empty 'Epson Receipt Printer IP Address' Disable'Connect Devices' Save Disabling 'Connect Devices' while leaving 'Cashdrawer' enabled will lead to crash during the payment session if the user click on 'Open Cashbox' when using cash as a payment method. After disabling the 'Connect Devices' the 'Cashdrawer' should be disabled automatically opw-2367498 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#60954
When creating an invoice from an attachment fails, we call super() which creates a new invoice and post the attachment to it without the `no_new_invoice` context key. This triggers an new import of the attachment. 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#61169
Original PR description
When creating an invoice from an attachment fails, we call super() which creates a new invoice and post the attachment to it without the `no_new_invoice` context key. This triggers an new import of the attachment. 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#61169
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61062
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61062
The 'destroy' method (in website form publicWidget) empties form inputs using .val(''). As a result, firefox applies ':-moz-ui-invalid' as soon as it considers the required inputs dirty, and applies by default a style that creates a red "glow" (using the box-shadow property) around items which this pseudo-class applied. The goal of this PR is to override form validation to prevent this behaviour. task-2312878 Forward-Port-Of: odoo/odoo#60455
Original PR description
The 'destroy' method (in website form publicWidget) empties form inputs
using .val(''). As a result, firefox applies ':-moz-ui-invalid' as
soon as it considers the required inputs dirty, and applies by default
a style that creates a red "glow" (using the box-shadow property) around
items which this pseudo-class applied.
The goal of this PR is to override form validation to prevent this behaviour.
task-2312878
Forward-Port-Of: odoo/odoo#60455Before this commit, double clicking on the border or on the padding of a form input generate a traceback. It was because, in this case, this.el was undefined in the close function. There should be a better fix to avoid this.el undefined in this function. task-2312878 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 F
Original PR description
Before this commit, double clicking on the border or on the padding of a form input generate a traceback. It was because, in this case, this.el was undefined in the close function. There should be a better fix to avoid this.el undefined in this function. task-2312878 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#60816
task-2352688 Forward-Port-Of: odoo/odoo#61162 Forward-Port-Of: odoo/odoo#61066
Original PR description
task-2352688 Forward-Port-Of: odoo/odoo#61162 Forward-Port-Of: odoo/odoo#61066
Issue - Use runbot with all modules/duplicate DB-all - Open a sale order randomly and enable every columns on Order Lines - Press "CREATE" button - Add "[E-COM11] Cabinet with Doors" to the products The widget is not visible Cause There are too many columns Solution Increase the width of the widget opw-2342149 Forward-Port-Of: odoo/odoo#61182
Original PR description
Issue
- Use runbot with all modules/duplicate DB-all
- Open a sale order randomly and enable every columns on Order Lines
- Press "CREATE" button
- Add "[E-COM11] Cabinet with Doors" to the products
The widget is not visible
Cause
There are too many columns
Solution
Increase the width of the widget
opw-2342149
Forward-Port-Of: odoo/odoo#61182The element bankAccNr has a maximum length of 35 characters. As the IBAN format allows up to 34 characters, we should use the sanitized account number in order to remove spaces, otherwise the limit is exceeded in some cases. opw-2371608 Forward-Port-Of: odoo/enterprise#14516
Original PR description
The element bankAccNr has a maximum length of 35 characters. As the IBAN format allows up to 34 characters, we should use the sanitized account number in order to remove spaces, otherwise the limit is exceeded in some cases. opw-2371608 Forward-Port-Of: odoo/enterprise#14516
We need to use appropriate comparison to check float equality. [opw-2366930](https://www.odoo.com/web#active_id=2366930&cids=1&id=2366930&model=project.task&menu_id=) Forward-Port-Of: odoo/enterprise#14252
Original PR description
We need to use appropriate comparison to check float equality. [opw-2366930](https://www.odoo.com/web#active_id=2366930&cids=1&id=2366930&model=project.task&menu_id=) Forward-Port-Of: odoo/enterprise#14252
…nced Forward-Port-Of: odoo/enterprise#14420
Original PR description
…nced Forward-Port-Of: odoo/enterprise#14420
Currently, in expense module when we try to open line record it generates traceback. Step to reproduce: -Create an expense and write a description containing multiple line (text fields). -Create a report -Try to open the line record After this commit, we able to display the line record of the expense module. LINKS PR: #14498 Task-Id: 2365369 Forward-Port-Of: odoo/enterprise#14498
Original PR description
Currently, in expense module when we try to open line record it generates traceback. Step to reproduce: -Create an expense and write a description containing multiple line (text fields). -Create a report -Try to open the line record After this commit, we able to display the line record of the expense module. LINKS PR: #14498 Task-Id: 2365369 Forward-Port-Of: odoo/enterprise#14498
"type" field of account_move was renamed "move_type" in commit https://github.com/odoo/odoo/commit/d675dbaa4c7174591e0e7c1a3caf3e76877312ce . Change was not made in l10n_de_reports/datev_export_csv.py Forward-Port-Of: odoo/enterprise#14515
Original PR description
"type" field of account_move was renamed "move_type" in commit https://github.com/odoo/odoo/commit/d675dbaa4c7174591e0e7c1a3caf3e76877312ce . Change was not made in l10n_de_reports/datev_export_csv.py Forward-Port-Of: odoo/enterprise#14515
Current behavior before PR: The timer is not displayed as running when clicking to the play button. Desired behavior after PR is merged: The timer is displayed as running when clicking to the play button. LINKS: PR https://github.com/odoo/enterprise/pull/13789 Task-2345451 Forward-Port-Of: odoo/enterprise#13789
Original PR description
Current behavior before PR: The timer is not displayed as running when clicking to the play button. Desired behavior after PR is merged: The timer is displayed as running when clicking to the play button. LINKS: PR https://github.com/odoo/enterprise/pull/13789 Task-2345451 Forward-Port-Of: odoo/enterprise#13789
- In payslips, the amount should take extra time off into account, the value used is then wage_with_holidays instead of wage - When a contract is created from a contract template, the 'previous contract' button, leading to the template, is now invisible modified: hr_contract_salary.hr_contract.py, hr_contract_salary.hr_contract_views.xml task: 2326391 Forward-Port-Of: odoo/enterprise#13267
Original PR description
- In payslips, the amount should take extra time off into account, the value used is then wage_with_holidays instead of wage - When a contract is created from a contract template, the 'previous contract' button, leading to the template, is now invisible modified: hr_contract_salary.hr_contract.py, hr_contract_salary.hr_contract_views.xml task: 2326391 Forward-Port-Of: odoo/enterprise#13267
By default the reconcile model displays entries that are up to 18 months old. The problem is that the dates are hardcoded for the tour and therefore the entries are no longer shown. The solution has been to remove this date limit for the tour. Forward-Port-Of: odoo/enterprise#14513
Original PR description
By default the reconcile model displays entries that are up to 18 months old. The problem is that the dates are hardcoded for the tour and therefore the entries are no longer shown. The solution has been to remove this date limit for the tour. Forward-Port-Of: odoo/enterprise#14513