Monday, July 13, 2020
14 changes · master
Enhancements to existing features
Automated tests now avoid starting shared background services that each test already sets up on its own. This reduces test conflicts and unexpected results, helping developers validate changes more reliably without affecting normal user workflows.
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
Resolved issues and error corrections
This fixes a manufacturing work order pop-up so it can close correctly after a user saves or clicks the related button. It removes a small workflow annoyance for teams managing production orders in Odoo.
Original PR description
The workorder opening wizard view need a footer to be closed when clicking on a button. Task : 2278147 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
### Issue - Install Employees & Dashboard - Add employees to kanban - Dashboard - Hover an employee picture There is only the picture visible on the page, the remaining space is white. ### Cause I found several issues. 1. The pictures are not shown on hover in employees But they are on dashboard. 2. $attach = all `.content` and on dashboard there is 2 `.content` so the flyout is append 2 times 3. The move method i
Original PR description
### Issue - Install Employees & Dashboard - Add employees to kanban - Dashboard - Hover an employee picture There is only the picture visible on the page, the remaining space is white. ### Cause I…
### Issue
- Install Employees & Dashboard
- Add employees to kanban
- Dashboard
- Hover an employee picture
There is only the picture visible
on the page, the remaining space is white.
### Cause
I found several issues.
1. The pictures are not shown on hover in employees
But they are on dashboard.
2. $attach = all `.content` and on dashboard there is
2 `.content` so the flyout is append 2 times
3. The move method is trigerred on hover too, it hides
the flyout if we are not in it. But with attachToTarget
we are not in it so it's hidden all time.
4. If everything above is solved, the image is shown but
not at the correct position because the flyout base
position is not top 0, left 0
### Solution
1. Reduce the minimum required size to 128px
2. use closest instead of parents
3. Don't hide if we have the option attachToTarget
4. Calculate the flyout offset and replace it correctly
**OPW-2291493**
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#54312
Forward-Port-Of: odoo/odoo#54273Support for the "allow exports" group was implemented by checking the group in init(), which is sync. Move that check over to willStart instead. Forward-Port-Of: odoo/odoo#54238 Forward-Port-Of: odoo/odoo#54114
Original PR description
Support for the "allow exports" group was implemented by checking the group in init(), which is sync. Move that check over to willStart instead. Forward-Port-Of: odoo/odoo#54238 Forward-Port-Of: odoo/odoo#54114
Go to Payments view Select multiple confirmed payments, click on Actions>Send receipt by email Only for the first payment will be sent an email. This occur because in composition mode 'comment' (the default) mail composer sens the mail to a single record opw-2278971 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53918 Forward-Port-Of: odoo/odoo#53725
Original PR description
Go to Payments view Select multiple confirmed payments, click on Actions>Send receipt by email Only for the first payment will be sent an email. This occur because in composition mode 'comment' (the default) mail composer sens the mail to a single record opw-2278971 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53918 Forward-Port-Of: odoo/odoo#53725
Go to eshop with public user Add items in cart Checkout, reach shipping and billing address page Fill the form Add a coupon Page will refresh and added content will be lost This will prevent user from adding a coupon when a form needs to be filled opw-2287428 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54205 Forward-Port-Of: odoo/odoo#54101
Original PR description
Go to eshop with public user Add items in cart Checkout, reach shipping and billing address page Fill the form Add a coupon Page will refresh and added content will be lost This will prevent user from adding a coupon when a form needs to be filled opw-2287428 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54205 Forward-Port-Of: odoo/odoo#54101
**Description of the issue/feature this PR addresses:** `description` for tax templates in `account_tax_data.xml` is not showing a "friendly" customer description for several taxes. This PR improves that description and makes it easier to understand. It's common to be requested for changes and being forced to help customers to replace the current tax label by understandable descriptions. **Current behavior before PR:** Tax labels are shown in documents. These labels are not "customer
Original PR description
**Description of the issue/feature this PR addresses:** `description` for tax templates in `account_tax_data.xml` is not showing a "friendly" customer description for several taxes. This PR improves that description and makes it easier to understand. It's common to be requested for changes and being forced to help customers to replace the current tax label by understandable descriptions. **Current behavior before PR:** Tax labels are shown in documents. These labels are not "customer friendly". **Desired behavior after PR is merged:** Make tax description easy to understand in documents. @pedrobaeza @acysos -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53965 Forward-Port-Of: odoo/odoo#51550
Create four promotion programs: if the order > 1500 than 10% discount if the order > 1750 than 15% discount if the order > 2000 than 20% discount if the order > 2500 than 25% discount Take a product with a price of $300 and add 5 to cart > the 10% discount is correctly applied. Add 1 more product (6) > it should now qualify for 15% discount, but it stays at 10% Add 1 more product (7) > it (correctly) gets the 20% discount The 25% discount does not get applied until 11 of the produc
Original PR description
Create four promotion programs: if the order > 1500 than 10% discount if the order > 1750 than 15% discount if the order > 2000 than 20% discount if the order > 2500 than 25% discount Take a product…
Create four promotion programs: if the order > 1500 than 10% discount if the order > 1750 than 15% discount if the order > 2000 than 20% discount if the order > 2500 than 25% discount Take a product with a price of $300 and add 5 to cart > the 10% discount is correctly applied. Add 1 more product (6) > it should now qualify for 15% discount, but it stays at 10% Add 1 more product (7) > it (correctly) gets the 20% discount The 25% discount does not get applied until 11 of the product is in the cart, even though it should qualify at 9 If you then decrease the quantity, the right discount will sometimes display. This occur because when the order amount change and the new total is used to match the right promo the previously applied discount is not removed from the amount. This occur as side effect of 1d59785 in which the amount has to be kept in order to avoid discount line removal on cart update. opw-2285656 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#54131 Forward-Port-Of: odoo/odoo#54034
…0dc5c 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#54401
Original PR description
…0dc5c 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#54401
Issue - Install "Accounting" and "Account Analytic Defaults". - Create an Analytic Tag and use the distribution (eg.: 60/40) - Create an Analytic Defaults for a specific partner. with the Analytc tag just created. - Create a bill, select the the same partner as the Analytic Defaults and add a new Invoice Line with a price (eg.: 1000). The tag is applied to the payable account, which is wrong and it leads to an analytic inconsistency. Cause In odoo 13 we are using s
Original PR description
Issue - Install "Accounting" and "Account Analytic Defaults". - Create an Analytic Tag and use the distribution (eg.: 60/40) - Create an Analytic Defaults for a specific partner. with the Analytc tag just created. - Create a bill, select the the same partner as the Analytic Defaults and add a new Invoice Line with a price (eg.: 1000). The tag is applied to the payable account, which is wrong and it leads to an analytic inconsistency. Cause In odoo 13 we are using single model for both the invoice and for journal entries. Solution Apply analytic tags only on move lines not excluded from invoice tab. opw-2269757 Forward-Port-Of: odoo/odoo#54392 Forward-Port-Of: odoo/odoo#54137
Forward-Port-Of: odoo/enterprise#11801
Original PR description
Forward-Port-Of: odoo/enterprise#11801
Issue - Install "Inventory" and "Barcode" apps - Go to "Inventory" an create a transfer with product A - Archive product A - Go to "Barcode" app and try to open the transfer created Traceback Cause Trying to fetch products with 'search_read' method who do not search for archived products. Solution Update domain to fetch product archived or not. opw-2284836 Forward-Port-Of: odoo/enterprise#11805
Original PR description
Issue
- Install "Inventory" and "Barcode" apps
- Go to "Inventory" an create a transfer with product A
- Archive product A
- Go to "Barcode" app and try to open the transfer created
Traceback
Cause
Trying to fetch products with 'search_read' method who do not
search for archived products.
Solution
Update domain to fetch product archived or not.
opw-2284836
Forward-Port-Of: odoo/enterprise#11805- Install Accounting & Contacts - Go to Contacts - Create a Company contact (with an Email) - Add an Invoice Address to the created contact (with an Email) - Go to Accounting > Customers > Invoices and create a new Invoice: * Select created Invoice Address as Customer * Select Invoice Date and Payment Terms in a way that the invoice would be overdue - Post the invoice and send it - Go to Accounting > Customers > Follow-up Reports - Search for the created Company contact and open it
Original PR description
- Install Accounting & Contacts - Go to Contacts - Create a Company contact (with an Email) - Add an Invoice Address to the created contact (with an Email) - Go to Accounting > Customers > Invoices and create a new Invoice: * Select created Invoice Address as Customer * Select Invoice Date and Payment Terms in a way that the invoice would be overdue - Post the invoice and send it - Go to Accounting > Customers > Follow-up Reports - Search for the created Company contact and open it - The displayed email address is the one from the Invoice Address - Click on "SEND BY EMAIL" button The email is sent to the email address of the Company and not to the Invoice address. opw-2288119 Forward-Port-Of: odoo/enterprise#11796
When module l10n_mx_reports_closing is installed and Mexican Trial Balance is asked what is presented in the html view is not the same as the reports fetched in xlsx, pdf or txt. When there are Closing Journal Entries. It is necessary to set the context properly otherwise methods such as `get_pdf`, `get_xlsx` and `get_txt` won't receive context sent by l10n_mx_reports_closing module at `_query_get` method. opw-2294684 Forward-Port-Of: odoo/enterprise#11779
Original PR description
When module l10n_mx_reports_closing is installed and Mexican Trial Balance is asked what is presented in the html view is not the same as the reports fetched in xlsx, pdf or txt. When there are Closing Journal Entries. It is necessary to set the context properly otherwise methods such as `get_pdf`, `get_xlsx` and `get_txt` won't receive context sent by l10n_mx_reports_closing module at `_query_get` method. opw-2294684 Forward-Port-Of: odoo/enterprise#11779