Thursday, January 28, 2021
22 changes · master
New functionality added to Odoo
The community documentation now includes guidance for the grid view that was previously only available in the enterprise documentation. This makes it easier for users and implementers to understand grid view options and recent related attributes in one shared documentation source.
Original PR description
task-2271628 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
Graph charts now use the custom label defined in the view for measure fields, instead of always falling back to the generic field name. This keeps chart labels, popovers, and measure dropdowns consistent, reducing confusion for users reading reports.
Original PR description
PURPOSE The graph view fields can have the "string" attribute. Unfortunately, it is not used by in the chart.js instance to update the labels and popover. SPEC When we define a graph view, the string attribute is ignored in the label and popover, use field strings given in view definition on more priority then field definition. TASK 2264636 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update fixes the displayed label for the Warehouse field in Point of Sale settings. It helps users see the correct wording in the configuration screen, reducing confusion when setting up sales locations.
Original PR description
Use correct field label for Warehouse Followup on dd2aaf0b1dc4ff3997ca753ee1feb67920f5cbfa 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
Documentation and clarification updates
This update adds a new email address to the corporate contributor license agreement record for i3 Rendszerház Kft. It helps keep Odoo's contributor legal documentation accurate and up to date.
Original PR description
Add my name i3 Rendszerház Kft. 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
Miscellaneous changes
Behavior prior to this commit: When a PO is generated (via reordering rule, mto rule, or manual replenish), the description on the PO line includes the internal notes. Behavior after this commit: The description on the PO line does not include the internal notes. opw-24222438 (partial) Forward-Port-Of: odoo/odoo#63892
Original PR description
Behavior prior to this commit: When a PO is generated (via reordering rule, mto rule, or manual replenish), the description on the PO line includes the internal notes. Behavior after this commit: The description on the PO line does not include the internal notes. opw-24222438 (partial) Forward-Port-Of: odoo/odoo#63892
Generate a coupon code, print it opw-2444242 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#64961
Original PR description
Generate a coupon code, print it opw-2444242 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#64961
…ght model This is not really a big issue but let us have correctly defined rules. Spotted during Task ID-2300230 Forward-Port-Of: odoo/odoo#65147
Original PR description
…ght model This is not really a big issue but let us have correctly defined rules. Spotted during Task ID-2300230 Forward-Port-Of: odoo/odoo#65147
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#61998
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#61998
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#64912 Forward-Port-Of: odoo/odoo#64362
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#64912 Forward-Port-Of: odoo/odoo#64362
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#65157 Forward-Port-Of: odoo/odoo#65101
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#65157 Forward-Port-Of: odoo/odoo#65101
Steps to reproduce the bug: - Go to Accounting (module)> Accounting (menu) > Journal Entries - Create a new account move M - Remove the default journal Bug: Impossible to set a journal opw:2445553 Forward-Port-Of: odoo/odoo#65144
Original PR description
Steps to reproduce the bug: - Go to Accounting (module)> Accounting (menu) > Journal Entries - Create a new account move M - Remove the default journal Bug: Impossible to set a journal opw:2445553 Forward-Port-Of: odoo/odoo#65144
…ut currency Follow-up of 13a4544707053295565c33580526f6a8a16f556b Where we fixed the portal *list* of opportunities but did not notice that the associated *form* also had the same issue. To recap the issue: When you remove the 'company_id' on a crm.lead, you also remove the computed 'company_currency'. When trying to view this kind of leads in the website_crm_partner_assign portal form page, it would raise an error while trying to display the planned_revenue in the missing curr
Original PR description
…ut currency Follow-up of 13a4544707053295565c33580526f6a8a16f556b Where we fixed the portal *list* of opportunities but did not notice that the associated *form* also had the same issue. To recap…
…ut currency Follow-up of 13a4544707053295565c33580526f6a8a16f556b Where we fixed the portal *list* of opportunities but did not notice that the associated *form* also had the same issue. To recap the issue: When you remove the 'company_id' on a crm.lead, you also remove the computed 'company_currency'. When trying to view this kind of leads in the website_crm_partner_assign portal form page, it would raise an error while trying to display the planned_revenue in the missing currency. Now, we display the number without any currency sign, which is a "best effort" solution, just the same as on the crm.lead form view. So it will look like "9000 at 47%" instead of "$9000 at 47%". Task-2444539 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#65141 Forward-Port-Of: odoo/odoo#64933
When Odoo is started in worker mode with Python 3.8.5, and gevent/greenlet installed from requirements, the following error message is thrown: `RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility` As a gevent developper stated [1] that gevent 1.5 is not compatible with Python 3.8, this commit bumps the version to 20.9.0 (current version for the next Debian and Ubuntu releases [2] [3]) This commit should not impact those who use the Debian/Ubuntu pack
Original PR description
When Odoo is started in worker mode with Python 3.8.5, and gevent/greenlet installed from requirements, the following error message is thrown: `RuntimeWarning: greenlet.greenlet size changed, may…
When Odoo is started in worker mode with Python 3.8.5, and gevent/greenlet installed from requirements, the following error message is thrown: `RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility` As a gevent developper stated [1] that gevent 1.5 is not compatible with Python 3.8, this commit bumps the version to 20.9.0 (current version for the next Debian and Ubuntu releases [2] [3]) This commit should not impact those who use the Debian/Ubuntu packages of gevent and greenlet. The error does not appear with those versions. In Ubuntu Focal, the packaged version is 1.4.0 [4] but the problem was not reported with this version and python 3.8. For reference, it was bumped to 1.5.0 for Python 3.7 in [5]. And greenlet was bumped too for issues with Python 3.8 and 3.9 in [6]. As a result, the requirements for greenlet/gevents gains even more complexity and should be cleaned when python 3.6 support will be dropped. [1] https://github.com/gevent/gevent/issues/1260 [2] https://packages.debian.org/bullseye/python3-gevent [3] https://packages.ubuntu.com/hirsute/python3-gevent [4] https://packages.ubuntu.com/focal/python3-gevent [5] odoo/odoo@bb0b32bd1a3fc0c047d0787b10e8c1c8d696daa5 [6] odoo/odoo@648635deca67df09417ae55c6eb181c98524b74d Fixes #64106 Forward-Port-Of: odoo/odoo#65012
Issue - Install "Contacts" and "Studio" modules - Go to "Contacts" and switch to Studio - Go to "Reports" tab - Create a new report - Select "External" layout Header and footer are missing on report. Cause Header is displayed if 'company' has a value. However, here, we only check if 'company_id' is available in current record fields, not checking if also set. Solution Check that 'company_id' is set on current record, else, fallback on 'res_company'. opw-244
Original PR description
Issue - Install "Contacts" and "Studio" modules - Go to "Contacts" and switch to Studio - Go to "Reports" tab - Create a new report - Select "External" layout Header and footer are missing on report. Cause Header is displayed if 'company' has a value. However, here, we only check if 'company_id' is available in current record fields, not checking if also set. Solution Check that 'company_id' is set on current record, else, fallback on 'res_company'. opw-2443234 Forward-Port-Of: odoo/odoo#65140
Currently, Chrome show a scrollbar when the placeholder is multilined. Overflow hidden will avoid the scrollbar and we place a nowrap on the placeholder text to avoid the multiline. task-2416058 Forward-Port-Of: odoo/odoo#63984
Original PR description
Currently, Chrome show a scrollbar when the placeholder is multilined. Overflow hidden will avoid the scrollbar and we place a nowrap on the placeholder text to avoid the multiline. task-2416058 Forward-Port-Of: odoo/odoo#63984
By making this tree non-editable, clicking on the rows opens the corresponding form, and gives access to more information and better navigation. Forward-Port-Of: odoo/odoo#65206
Original PR description
By making this tree non-editable, clicking on the rows opens the corresponding form, and gives access to more information and better navigation. Forward-Port-Of: odoo/odoo#65206
Office Outlook doesn't take into account the [style] attribute, and it doesn't manage width/height in percent value. This commit set width/heigth attribute in pixels and also always set the width/height in style attribute (keeping them in the original unit and setting them to auto if not present). This is a reintroduction of 2015 commit bdf58adb465b opw-2447756 Forward-Port-Of: odoo/odoo#65150
Original PR description
Office Outlook doesn't take into account the [style] attribute, and it doesn't manage width/height in percent value. This commit set width/heigth attribute in pixels and also always set the width/height in style attribute (keeping them in the original unit and setting them to auto if not present). This is a reintroduction of 2015 commit bdf58adb465b opw-2447756 Forward-Port-Of: odoo/odoo#65150
Create a product with variants attributes that NEVER create variants. Configure Variants to add some extra-prices to some variants. In POS settings activate "Product Configurator" and "Advanced Pricelists", add the public pricelist and one that applies 5% to the product. Open a session and select the product created (say price = 1$) Select the attributes, the extra-price is added to the product (say the total price now is 2$). Change pricelist from public to 5% and the order line will
Original PR description
Create a product with variants attributes that NEVER create variants. Configure Variants to add some extra-prices to some variants. In POS settings activate "Product Configurator" and "Advanced Pricelists", add the public pricelist and one that applies 5% to the product. Open a session and select the product created (say price = 1$) Select the attributes, the extra-price is added to the product (say the total price now is 2$). Change pricelist from public to 5% and the order line will show our product = 0.95, not taking the extra-prices into account (so not 1.9, i.e. 5% of the 2$ that were formerly displayed) opw-2439445 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#64861
Before this commit, dropzones were created around invisible elements (e.g. the snippet popup). So we had 2 dropzones instead of one at some locations. After this commit, we avoid creating dropzones around elements that must not have dropzones. 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-P
Original PR description
Before this commit, dropzones were created around invisible elements (e.g. the snippet popup). So we had 2 dropzones instead of one at some locations. After this commit, we avoid creating dropzones around elements that must not have dropzones. 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#65198
Before this commit, when the purchase order was automatically confirm and send to the partner, the pdf send was the one of the request for quotation. Now, the pdf send is the purchase order. opw-2427046 Forward-Port-Of: odoo/enterprise#15995
Original PR description
Before this commit, when the purchase order was automatically confirm and send to the partner, the pdf send was the one of the request for quotation. Now, the pdf send is the purchase order. opw-2427046 Forward-Port-Of: odoo/enterprise#15995
Allows export of electronic reports in Luxembourg's XML 2.0 format, according to the ecdf rules (cfr. https://ecdf-developer.b2g.etat.lu/ecdf/home). Odoo's interface has been validated by ecdf using this module. Supported reports: * Annual accounts: P&L + Balance Sheet + CoA * VAT declarations: monthly + quarterly + yearly + yearly simplified declarations * VAT IC recapitulative statements: {goods, services} x {monthly, quarterly} + appendix "Tables of acquisitions/amortisable expendit
Original PR description
Allows export of electronic reports in Luxembourg's XML 2.0 format, according to the ecdf rules (cfr. https://ecdf-developer.b2g.etat.lu/ecdf/home).
Odoo's interface has been validated by ecdf using this module.
Supported reports:
* Annual accounts: P&L + Balance Sheet + CoA
* VAT declarations: monthly + quarterly + yearly + yearly simplified declarations
* VAT IC recapitulative statements: {goods, services} x {monthly, quarterly} + appendix "Tables of acquisitions/amortisable expenditures"
Forward-Port-Of: odoo/enterprise#15916
Forward-Port-Of: odoo/enterprise#15460When checking the revenue KPIs, the net revenue is always 0. To reproduce the error: 1. Go to sales, create a SO - Product must be a subscription product 2. Confirm, Create Invoice 3. Post the invoice, Register the payment 4. Go to Subscriptions - You find the subscription you just created in the In-Progress column 5. Reporting > Revenue KPIs 6. Set the date range so your subscription will be included, Update Error: All charts but the Net Revenue are updated. The Net Revenue is
Original PR description
When checking the revenue KPIs, the net revenue is always 0. To reproduce the error: 1. Go to sales, create a SO - Product must be a subscription product 2. Confirm, Create Invoice 3. Post the invoice, Register the payment 4. Go to Subscriptions - You find the subscription you just created in the In-Progress column 5. Reporting > Revenue KPIs 6. Set the date range so your subscription will be included, Update Error: All charts but the Net Revenue are updated. The Net Revenue is still $0. It should at least include the sold and paid subscription (from steps 1-3). The error comes from the SQL request conditions used to compute the net revenue. The SQL result includes the reconciliation lines, therefore the sum is 0. OPW-2431880 Forward-Port-Of: odoo/enterprise#15906