Monday, October 19, 2020
39 changes · master
New functionality added to Odoo
This adds a new WeChat Pay payment option for Odoo online sales. Businesses selling in China can offer customers a familiar local payment method after installing the new payment_wechatpay module.
Original PR description
Description of the issue/feature this PR addresses: Wechatpay is another popular online payment in china. This PR add wechat pay support. Current behavior before PR: at present, odoo has no module work for wechat app. Desired behavior after PR is merged: when PR merged, people can use wechat pay in online selling after installing payment_wechatpay. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
Resolved issues and error corrections
This fixes small visual issues in the website editor toolbar so buttons keep the expected appearance when color previews are not shown. It helps editors see clearer, more consistent controls while formatting website content.
Original PR description
For the JW toolbars without color previews, we don't want to change the background color of the button. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
The method _to_action_data needs to retrieve the action as sudo to be able to read it's content. Before this commit, an access right error was raised when a user clicked on the "Overview" button on the project kanban, when trying to read the content of the project.action_view_task record Forward-Port-Of: odoo/odoo#59892
Original PR description
The method _to_action_data needs to retrieve the action as sudo to be able to read it's content. Before this commit, an access right error was raised when a user clicked on the "Overview" button on the project kanban, when trying to read the content of the project.action_view_task record Forward-Port-Of: odoo/odoo#59892
This update strengthens automated checks so duplicate functions, classes, or methods are caught before they can cause issues. Several affected areas were cleaned up to meet the new check, reducing the chance of hidden mistakes reaching users.
Original PR description
With this commit, pylint will now point out when the same function/class/method is defined more than once in the same scope which is a recurring mistake Linked to https://github.com/odoo/enterprise/pull/14090 Prevents errors such as https://github.com/odoo/odoo/issues/59683 (and many others) from even happening
The stock module now prevents creating multiple reordering rules for the same product at the same location. This avoids duplicate replenishment actions that could lead to unnecessary purchases or stock moves.
Original PR description
This commit adds a constraint on model stock.warehouse.orderpoint (reordering rule) to ensure two orderpoint are not set on the same product and on the same location. This is an issue as the replenishment will be done multiple times in case of duplicated rules. Task : 1939567 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
Mailings and their tracking sources now receive clearer automatically generated names when users do not enter one. Duplicate names are handled with a simple counter, making campaigns easier to identify and reducing confusing or unnecessary demo translation entries.
Original PR description
PURPOSE
=======
This commit improves the auto generated name of the mailings and of the UTM source.
Currently, this name is auto generated but is not very user-friendly.
SPECIFICATIONS
=======
We want to have a unique mailing/source name.
When no name is given, we automatically generate one with the following format
"<subject> (Mailing created on <date>)".
If the name is duplicated, we add a counter after it ("<name> [X]").
Update the demo data to not auto-generate the name and to avoid creating unnecessary
i18n lines.
LINKS
=======
Task 2245823The Project portal now shows the creation date with the label "Created On" instead of the generic "Date". This reduces confusion by matching the field's meaning more clearly for users viewing project information.
Original PR description
Before this commit, Label for `create_date` was `Date` which was confusing for the user since there is no field with label `Date` in the backend. Now we use `Created On:` as the label. 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 removes duplicate code definitions across several Odoo Enterprise apps so automated quality checks pass reliably. It also adjusts one Studio test without changing the business behavior being tested, reducing maintenance risk for future updates.
Original PR description
This commit adapts the business code in which class/module/function/method redefinition took place so that it no longer happens and the pylint test passes. Linked to https://github.com/odoo/odoo/pull/60044
This fixes a missed automated test adjustment so the dashboard waits for the Measures menu to be ready before checking it. It helps keep dashboard testing reliable after recent internal rendering changes, with no expected impact on day-to-day users.
The test fails when running tests with a non-standard http_port (which is necessary to run tests in multiple Odoo instances concurrently) because the http port is hard-coded. Soft-code it properly. Forward-Port-Of: odoo/odoo#60182
Original PR description
The test fails when running tests with a non-standard http_port (which is necessary to run tests in multiple Odoo instances concurrently) because the http port is hard-coded. Soft-code it properly. Forward-Port-Of: odoo/odoo#60182
Before this commit, `journal_id` field was not required on model/view, Creating record without `journal_id` is not allowed since it is required on `account.move`. Now field is required. 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#60133
Original PR description
Before this commit, `journal_id` field was not required on model/view, Creating record without `journal_id` is not allowed since it is required on `account.move`. Now field is required. 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#60133
Before this commit, Documents were referenced for the 13.0 version instead of the current one. In this commit, the references are corrected. 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#59554
Original PR description
Before this commit, Documents were referenced for the 13.0 version instead of the current one. In this commit, the references are corrected. 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#59554
Issue - Install "Project" module - Active "Sub Task" feature in settings - Create a new project `X` - Go to settings of project `X` and activate "sub task" feature - Add a Task `A` in project `X` - Add a subtask `B` to task `A` - In menu, click on `Tasks` to list all tasks - Edit view and add `subtask_count` field then save Wrong value in `subtask_count` field. Cause Retrieving childs of self instead of "current" task (`for task in self:`). Solution Use "curre
Original PR description
Issue - Install "Project" module - Active "Sub Task" feature in settings - Create a new project `X` - Go to settings of project `X` and activate "sub task" feature - Add a Task `A` in project `X` - Add a subtask `B` to task `A` - In menu, click on `Tasks` to list all tasks - Edit view and add `subtask_count` field then save Wrong value in `subtask_count` field. Cause Retrieving childs of self instead of "current" task (`for task in self:`). Solution Use "current" task instead of self. opw-2361013 Forward-Port-Of: odoo/odoo#60184
Before this commit, It was referring to non-existing decimal precision "Product UoS" which doesn't exists since odoo 9. Followup on d152106b1b8ee8294000bbca7d2ccc9c80a8d05e 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#60217
Original PR description
Before this commit, It was referring to non-existing decimal precision "Product UoS" which doesn't exists since odoo 9. Followup on d152106b1b8ee8294000bbca7d2ccc9c80a8d05e 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#60217
[FIX] stock: fix warehouse target forecasted In the compute of forecasted information of `stock.move`, instead of using the warehouse of the picking type, use the warehouse of the source location (if there is). [FIX] stock: disabled forecasted button new line In One2many tree of stock.move, the forecasted button trigger a traceback in case of new line because there isn't a target record. Also, don't show forecasted information when the state of the move is 'cancel'. [FIX] stock:
Original PR description
[FIX] stock: fix warehouse target forecasted In the compute of forecasted information of `stock.move`, instead of using the warehouse of the picking type, use the warehouse of the source location (if there is). [FIX] stock: disabled forecasted button new line In One2many tree of stock.move, the forecasted button trigger a traceback in case of new line because there isn't a target record. Also, don't show forecasted information when the state of the move is 'cancel'. [FIX] stock: fix `products_availability` compute the deadline of picking is not required, then add condition to avoid compare False to datetime. Forward-Port-Of: odoo/odoo#60118
Introduced at 2f67881d4517b78 Taken an event with `start_date: 2020-10-01` `stop_date: 2020-10-02` `allday: True` The date was displayed as `01/10 - 03/10 (2 days)` instead of `01/10 - 02/10 (2 days)` Fixes odoo/odoo#38750 Forward-Port-Of: odoo/odoo#60062 Forward-Port-Of: odoo/odoo#58972
Original PR description
Introduced at 2f67881d4517b78 Taken an event with `start_date: 2020-10-01` `stop_date: 2020-10-02` `allday: True` The date was displayed as `01/10 - 03/10 (2 days)` instead of `01/10 - 02/10 (2 days)` Fixes odoo/odoo#38750 Forward-Port-Of: odoo/odoo#60062 Forward-Port-Of: odoo/odoo#58972
**Description of the issue/feature this PR addresses:** Currently the onchange is setting the price_unit to the price_subtotal to work out the proper price unit related to the tax, but does not have a different line quantity in mind, so we simply help to normalize and provide the proper balance in the end again. **Current behavior before PR:** Calling the onchange method with a line.quantity greater than one and a fiscal position set will fail and raise a user error that the balance is inco
Original PR description
**Description of the issue/feature this PR addresses:** Currently the onchange is setting the price_unit to the price_subtotal to work out the proper price unit related to the tax, but does not have a different line quantity in mind, so we simply help to normalize and provide the proper balance in the end again. **Current behavior before PR:** Calling the onchange method with a line.quantity greater than one and a fiscal position set will fail and raise a user error that the balance is incorrect **Desired behavior after PR is merged:** As we take care that the balance is properly calculated it also works for invoice lines with a quantity greater than one Info: @wt-io-it -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60172 Forward-Port-Of: odoo/odoo#60059
Use case: website_event_track(_online) ====================================== On sponsor model, image_128 field is defined in website_event_track module as computed stored Image field. It means that when this binary field is set, an attachment is created in ir.attachment model -> attachment is set to True. In website_event_track_online module this field is modified. It is set as a related (resized) version of image_512 and not stored anymore. However attachments still exist in ir.at
Original PR description
Use case: website_event_track(_online) ====================================== On sponsor model, image_128 field is defined in website_event_track module as computed stored Image field. It means that…
Use case: website_event_track(_online) ====================================== On sponsor model, image_128 field is defined in website_event_track module as computed stored Image field. It means that when this binary field is set, an attachment is created in ir.attachment model -> attachment is set to True. In website_event_track_online module this field is modified. It is set as a related (resized) version of image_512 and not stored anymore. However attachments still exist in ir.attachment table for sponsor records. This is not an issue when trying to access the image_128 field using the ORM as the compute (or related) is correctly called. However '/web/image' does checks if the field has an attachment and loads it. In our case old attachments still in database are therefore displayed instead of the new related image. Fix === When checking for an existing attachment in _binary_record_content we also check that the field is not a related. This fixes the current issue. It also makes _binary_record_content work as the ORM, aka using the computed value and not any stored information. DB Cleaning =========== In 14.0 a script will be added to clean existing attachments for sponsor model. Indeed there is no need to keep unused attachments. Especially in 14 website_event_track_online has been merged in website_event_track, meaning only existing db have to be cleaned. New DBs will never have this attachment issue as the field is always computed. Task ID: 2341108 Forward-Port-Of: odoo/odoo#57854
When a user can edit it's employee, the field expense_manager_id is editable but any value is ignored, and the previous manager is forced. Forward-Port-Of: odoo/odoo#60185
Original PR description
When a user can edit it's employee, the field expense_manager_id is editable but any value is ignored, and the previous manager is forced. Forward-Port-Of: odoo/odoo#60185
The problem comes from how a language handle things like "Last week, last month, last year". For example, in Vietnamese, the "last" comes after the "week"/"month"/"year" instead of doing before like what is in English. We say "Tuần trước", where "Tuần" means "week", not "last". Before this commit, there is no way for the right translation into Vietnamese for the clause that was combined by `Sales Since Last <t t-esc="widget.date_range"></t>` -- I confirm I have signed the CLA and rea
Original PR description
The problem comes from how a language handle things like "Last week, last month, last year". For example, in Vietnamese, the "last" comes after the "week"/"month"/"year" instead of doing before like what is in English. We say "Tuần trước", where "Tuần" means "week", not "last". Before this commit, there is no way for the right translation into Vietnamese for the clause that was combined by `Sales Since Last <t t-esc="widget.date_range"></t>` -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#26067
Any non `<span/>` element which was transformed into an icon thanks to the media dialog was transform into a `<span/>` then processed by summernote. In some cases, this processing breaks the DOM... for no reason as the DOM should not have been transformed into a `<span/>` in the first place: `<i/>` elements inside a `<span/>` for example should stay `<i/>` elements after edition. Forward-Port-Of: odoo/odoo#60194
Original PR description
Any non `<span/>` element which was transformed into an icon thanks to the media dialog was transform into a `<span/>` then processed by summernote. In some cases, this processing breaks the DOM... for no reason as the DOM should not have been transformed into a `<span/>` in the first place: `<i/>` elements inside a `<span/>` for example should stay `<i/>` elements after edition. Forward-Port-Of: odoo/odoo#60194
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60046 Forward-Port-Of: odoo/odoo#59749
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#60046 Forward-Port-Of: odoo/odoo#59749
Steps to reproduce the bug: - Install web_studio, contacts - Activate language English (UK) - Switch all users' language to UK - Deactivate language English (US) - Via Studio, add a related field to a contact: Self > Language Bug: Traceback: contacts still have en_US as language and it's deactivated. opw:2350362 Forward-Port-Of: odoo/odoo#60266 Forward-Port-Of: odoo/odoo#60188
Original PR description
Steps to reproduce the bug: - Install web_studio, contacts - Activate language English (UK) - Switch all users' language to UK - Deactivate language English (US) - Via Studio, add a related field to a contact: Self > Language Bug: Traceback: contacts still have en_US as language and it's deactivated. opw:2350362 Forward-Port-Of: odoo/odoo#60266 Forward-Port-Of: odoo/odoo#60188
Create a Server Action with the following code: `raise Warning("")`, when the SA is executed it opens the crash manager with a traceback instead of the user error modal. The `odooExceptionTitleMap` data structure lists all Odoo exceptions that descend from UserError, this structure is used within the `rpc_error` function to filter pure Python exceptions from custom Odoo ones. opw-2365689 Forward-Port-Of: odoo/odoo#60248
Original PR description
Create a Server Action with the following code: `raise Warning("")`,
when the SA is executed it opens the crash manager with a traceback
instead of the user error modal.
The `odooExceptionTitleMap` data structure lists all Odoo exceptions
that descend from UserError, this structure is used within the
`rpc_error` function to filter pure Python exceptions from custom Odoo
ones.
opw-2365689
Forward-Port-Of: odoo/odoo#60248It wasn't possible before that, as the report_id field did not receive its default value before being checked (as it is required), so it was always detected as missing. Forward-Port-Of: odoo/odoo#60274
Original PR description
It wasn't possible before that, as the report_id field did not receive its default value before being checked (as it is required), so it was always detected as missing. Forward-Port-Of: odoo/odoo#60274
In a database with over 2k `sale.coupon.program`, the live computation of promotions on the website is very slow. Cart updates easily take more than 3 seconds (even for basic sale orders). This PR provides a bunch of performance improvements and some fixes, reducing the time by `~50%`. The remaining time is mainly due to the `_inherits` intrinsic slowness. It is recommended to upgrade to newer versions to enjoy newest performance improvements at the ORM level. This PR extends and improv
Original PR description
In a database with over 2k `sale.coupon.program`, the live computation of promotions on the website is very slow. Cart updates easily take more than 3 seconds (even for basic sale orders). This PR provides a bunch of performance improvements and some fixes, reducing the time by `~50%`. The remaining time is mainly due to the `_inherits` intrinsic slowness. It is recommended to upgrade to newer versions to enjoy newest performance improvements at the ORM level. This PR extends and improve the work done in #59011 opw-2323599 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60247 Forward-Port-Of: odoo/odoo#59467
Before this commit: - it was asking for the opt out contact when user selects the mailing contact - so, raising error when try to open mailing with contact as mailing model After this commit: - default opt_out domain is removed for mailing.contact model - opt_out field will not be shown in field selector dialog Task: https://www.odoo.com/web#id=2300427&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelin
Original PR description
Before this commit: - it was asking for the opt out contact when user selects the mailing contact - so, raising error when try to open mailing with contact as mailing model After this commit: - default opt_out domain is removed for mailing.contact model - opt_out field will not be shown in field selector dialog Task: https://www.odoo.com/web#id=2300427&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#57310
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#60195 Forward-Port-Of: odoo/odoo#59510
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#60195 Forward-Port-Of: odoo/odoo#59510
When you hava a fiscal position that that map one tax included into the price to another, the new amount is wrong. I we have a fiscal position that map a tax of 10% included to 20% included, and a product at 110$ having 10% included. When we map the tax from 10% to 20%, the new price is 100$ but should be 120$. This is because for now, the price is fixed to get the amount without tax, which perfectly works when destination tax is tax excluded. But when you call compute_all from a pric
Original PR description
When you hava a fiscal position that that map one tax included into the price to another, the new amount is wrong. I we have a fiscal position that map a tax of 10% included to 20% included, and a…
When you hava a fiscal position that that map one tax included into the price to another, the new amount is wrong. I we have a fiscal position that map a tax of 10% included to 20% included, and a product at 110$ having 10% included. When we map the tax from 10% to 20%, the new price is 100$ but should be 120$. This is because for now, the price is fixed to get the amount without tax, which perfectly works when destination tax is tax excluded. But when you call compute_all from a price with a tax included (20%) it keep the price and compute the tax amount out of this price. So to fix this issue, whent the origin tax and destination tax are included, we are computing the base amount (like before) and then we compute the new tax amount wihtout trying to find the tax amount out of the price. This will lead to have the same behavior between accounting and POS -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60237 Forward-Port-Of: odoo/odoo#60111
Task: https://www.odoo.com/web?#id=2300427&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720 Forward-Port-Of: odoo/enterprise#14065
Original PR description
Task: https://www.odoo.com/web?#id=2300427&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720 Forward-Port-Of: odoo/enterprise#14065
Commit [1] changed the design of the HTML field to not hack the default style. It is now decided that the hack is worth it. [1]: https://github.com/odoo/enterprise/commit/6b3643d8789d246095876d8da9a706ce9c5dd137 Forward-Port-Of: odoo/enterprise#14196
Original PR description
Commit [1] changed the design of the HTML field to not hack the default style. It is now decided that the hack is worth it. [1]: https://github.com/odoo/enterprise/commit/6b3643d8789d246095876d8da9a706ce9c5dd137 Forward-Port-Of: odoo/enterprise#14196
When a company made transactions in multiple currencies, on the general ledger when selecting a journal, the amount currency of the journal items are shown. Totals for the journal items are also calculated : total of debit, total of credit, the final balance and total of amount currency. The problem with the total of amount currency, is that the company can make transactions in multiple currencies, and sum this amounts in multiple currencies don't have much sense, its like adding apples
Original PR description
When a company made transactions in multiple currencies, on the general ledger when selecting a journal, the amount currency of the journal items are shown. Totals for the journal items are also calculated : total of debit, total of credit, the final balance and total of amount currency. The problem with the total of amount currency, is that the company can make transactions in multiple currencies, and sum this amounts in multiple currencies don't have much sense, its like adding apples and oranges. Also, the currency symbol of this total is the one of the currency of the account, which, as explained before, can be different from the amount currency of the journal items. opw-2346057 Forward-Port-Of: odoo/enterprise#14051 Forward-Port-Of: odoo/enterprise#14013
Add of currency in the list view for more clarity with multicurrencies Forward-Port-Of: odoo/enterprise#14184
Original PR description
Add of currency in the list view for more clarity with multicurrencies Forward-Port-Of: odoo/enterprise#14184
Issue - Install 'Subscriptions' - Enable 'Multi-currency' - Create two subscriptions with two different currency - Go to 'Reporting/Revenues KPI' - Try to select 'This Month' filter Cause The 'company_current_id' doesnt exist in currencies_mapped because there are just currency_id Solution Create new 'company_currencies_mapped' that contain company_current_id opw-2359506 Forward-Port-Of: odoo/enterprise#14173
Original PR description
Issue
- Install 'Subscriptions'
- Enable 'Multi-currency'
- Create two subscriptions with two different currency
- Go to 'Reporting/Revenues KPI'
- Try to select 'This Month' filter
Cause
The 'company_current_id' doesnt exist in currencies_mapped because there are just currency_id
Solution
Create new 'company_currencies_mapped' that contain company_current_id
opw-2359506
Forward-Port-Of: odoo/enterprise#14173The field origin_doc_number of l10n_cl.account.invoice.reference is used to populate the element FolioRef in DTE XML file. According to XSD, the structure of this element is of type string and can contain other characters than only integers. Moreover, we can have a ValueError when casting some values (e.g. 8335/20/09). opw-2346885 Forward-Port-Of: odoo/enterprise#14179
Original PR description
The field origin_doc_number of l10n_cl.account.invoice.reference is used to populate the element FolioRef in DTE XML file. According to XSD, the structure of this element is of type string and can contain other characters than only integers. Moreover, we can have a ValueError when casting some values (e.g. 8335/20/09). opw-2346885 Forward-Port-Of: odoo/enterprise#14179
The schedule is a SQL view, its fields should be computed in sudo mode. Otherwise, the user would receive an AccessError if he doesn't have access to some other models (e.g. some of the sale orders displayed). NB: the bug can be reproduced by accessing the scheduling view from a rented rentable storable product (e.g. the printer of the demo data) with the demo user.  Finetuning
Original PR description
The schedule is a SQL view, its fields should be computed in sudo mode. Otherwise, the user would receive an AccessError if he doesn't have access to some other models (e.g. some of the sale orders displayed). NB: the bug can be reproduced by accessing the scheduling view from a rented rentable storable product (e.g. the printer of the demo data) with the demo user.  Finetuning of #9459. Forward-Port-Of: odoo/enterprise#14034
The domain of the section `[07] Nº de perceptores` is incorrect: it is supposed to count the number of partners having [09] or [08], not both. opw-2362447 Forward-Port-Of: odoo/enterprise#14158 Forward-Port-Of: odoo/enterprise#14151
Original PR description
The domain of the section `[07] Nº de perceptores` is incorrect: it is supposed to count the number of partners having [09] or [08], not both. opw-2362447 Forward-Port-Of: odoo/enterprise#14158 Forward-Port-Of: odoo/enterprise#14151
… type Open Quality > Quality Control > Control Points > Create Operations: Receipts Control Type: Periodically (or Random 10%) Control Frequency: Any Open Purchase > Create a PO > Confirm and Receive. Every receipt of the product triggers the QC. This is not following the Odoo documentation (at the writing date) https://www.odoo.com/documentation/user/13.0/quality/control/control_points.html opw-2352683 Forward-Port-Of: odoo/enterprise#14011
Original PR description
… type Open Quality > Quality Control > Control Points > Create Operations: Receipts Control Type: Periodically (or Random 10%) Control Frequency: Any Open Purchase > Create a PO > Confirm and Receive. Every receipt of the product triggers the QC. This is not following the Odoo documentation (at the writing date) https://www.odoo.com/documentation/user/13.0/quality/control/control_points.html opw-2352683 Forward-Port-Of: odoo/enterprise#14011
Steps to reproduce the bug: - Let's consider a company C in $ - Let's consider a salary structure SS with a journal J in € - Create a payslip P with SS and compute the sheet of P - Create the journal entry of P Bug: All the posted journal entries were not converted in € opw:2341609 Forward-Port-Of: odoo/enterprise#13635 Forward-Port-Of: odoo/enterprise#13573
Original PR description
Steps to reproduce the bug: - Let's consider a company C in $ - Let's consider a salary structure SS with a journal J in € - Create a payslip P with SS and compute the sheet of P - Create the journal entry of P Bug: All the posted journal entries were not converted in € opw:2341609 Forward-Port-Of: odoo/enterprise#13635 Forward-Port-Of: odoo/enterprise#13573