Tuesday, November 26, 2019
33 changes · master
New functionality added to Odoo
Weekly digest emails now include a Live Chat section showing how many visitor conversations were handled, customer rating performance, and response times. This gives teams an easy way to monitor live chat activity and service quality without manually checking reports.
Original PR description
Description of the issue/feature this PR addresses: - To make a summary of livechat from which user get the information - Related task : https://www.odoo.com/web?#id=1883428&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 - Pad: https://pad.odoo.com/p/r.4bdc2c8043f94f2ef5c3d476e430e1cb Current behavior before PR: - User doesn't get any information/summary about how many visitors handled during a particular time. Desired behavior after PR is merged: - Now User will get a weekly digest emails and get to know about the summary that how many visitors handled and their ratings and time response for conversations done with them. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Logging records can now include extra location information when they are created while loading static resources such as files. This gives teams better context for investigating issues, while keeping the change internal and low risk for everyday users.
Original PR description
@rco-odoo @Xavier-Do what I was thinking for the improved location data in logs.
Enhancements to existing features
The accounting reversal wizard is updated to more reliably track the selected entries or invoices and avoid relying on hidden context data. Users also get clearer guidance that reversing invoices or bills will create refunds, reducing confusion during accounting operations.
Original PR description
Task [2085023](https://www.odoo.com/web#id=2085023&action=333&active_id=967&model=project.task&view_type=form&menu_id=4720) * Add a field that replaces the context to get the ids of the entries/invoices * Add text to explain invioces/bills will create refunds 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
`res.users` have two company fields `company_id` & `company_ids`. Adapt the default domain set on fields whose check_company is set to True to consider `res_users` relational fields and company_dependent fields. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40724
Original PR description
`res.users` have two company fields `company_id` & `company_ids`. Adapt the default domain set on fields whose check_company is set to True to consider `res_users` relational fields and company_dependent fields. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40724
The default logging setup now applies logging levels more consistently across the system, reducing the chance that unwanted messages appear despite stricter settings. The partner merge process also now uses the correct Odoo logging structure, making its messages easier to manage and monitor.
Original PR description
* the logger of the partner merge wizard should be rooted in the "odoo" logger not "base" * improve the default logging configuration so standard levels setup (e.g. `--log-level=warn`) is applied to the root logger, not separately to the intermediate "odoo" and "werkzeug" ones (thereby ensuring loggers will fall through the cracks and appear at INFO despite e.g. currently logging as ERROR)
This update lets website customization hide a specific technical suffix from view names. It makes the customization interface cleaner and easier to understand for users managing website views.
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
Odoo's import tool can now handle Excel files with multiple sheets by letting users choose which sheet to import. This reduces manual preparation work when spreadsheets contain several tables, while still selecting the first sheet by default.
Original PR description
Excel can store data in multiple tables, each is called a sheet. Odoo was only importing the first sheet making the process to import a file containing multiple sheets cumbersome. It is now possible to select the sheet in the import options. Task: 2043768
Adds the GST101A tax return report to the New Zealand localization, making it easier for businesses to prepare GST reporting in Odoo. This improves compliance support for New Zealand companies by aligning tax report data with local filing needs.
The automated action forms were made clearer and easier to use with better labels, safer selection controls, and more helpful defaults. This should reduce confusion when configuring automations, SMS actions, and related templates.
Original PR description
Task : https://www.odoo.com/web#id=2082503&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.30015b26b76505fcbdf24f23372a1eb5 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Helpdesk accounting now uses the updated way of linking multiple accounting entries when reversing moves. This keeps refund and reversal workflows compatible with recent accounting changes and helps avoid errors during customer support billing operations.
Original PR description
Task [2085023](https://www.odoo.com/web#id=2085023&action=333&active_id=967&model=project.task&view_type=form&menu_id=4720) The field move_id doesn't exist anymore as move_ids has been introduced. Community PR https://github.com/odoo/odoo/pull/38857
Odoo Studio was updated to use the renamed automated action field, keeping it aligned with the core automation model. This helps ensure Studio exports and automation-related behavior continue to work after the underlying field name change.
Original PR description
Task : https://www.odoo.com/web#id=2082503&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.30015b26b76505fcbdf24f23372a1eb5
When clicking on stat button "Meetings" on a partner, highlight the partner meetings as is done for similar stat button instead of having a domain that hides other event (so when creating meeting, we can take into account other existing meetings). opw-2131494 Forward-Port-Of: odoo/odoo#40812
Original PR description
When clicking on stat button "Meetings" on a partner, highlight the partner meetings as is done for similar stat button instead of having a domain that hides other event (so when creating meeting, we can take into account other existing meetings). opw-2131494 Forward-Port-Of: odoo/odoo#40812
Signing the CLA -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40851
Original PR description
Signing the CLA -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40851
Description of the issue/feature this PR addresses: Fix the widget typo Current behavior before PR: The widget on the form view has a typo, causing it to not show as the real widget. Desired behavior after PR is merged: The widget is applied well and shown on the form view. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40754
Original PR description
Description of the issue/feature this PR addresses: Fix the widget typo Current behavior before PR: The widget on the form view has a typo, causing it to not show as the real widget. Desired behavior after PR is merged: The widget is applied well and shown on the form view. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40754
Description of the issue/feature this PR addresses: URL to article on Promises has changed Current behavior before PR: Current URL not working Desired behavior after PR is merged: URL should work -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40405
Original PR description
Description of the issue/feature this PR addresses: URL to article on Promises has changed Current behavior before PR: Current URL not working Desired behavior after PR is merged: URL should work -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40405
…reference - Create a vendor bill for partner A with reference 'AAAAA' - Create another vendor bill for partner A with the same reference: => Constraint is triggered. - Create another vendor bill without partner with the same reference. - Edit the vendor bill and set a partner: => Constraint not triggered. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40849
Original PR description
…reference - Create a vendor bill for partner A with reference 'AAAAA' - Create another vendor bill for partner A with the same reference: => Constraint is triggered. - Create another vendor bill without partner with the same reference. - Edit the vendor bill and set a partner: => Constraint not triggered. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40849
Restore newsletter subscribe notification Forward-Port-Of: odoo/odoo#40864
Original PR description
Restore newsletter subscribe notification Forward-Port-Of: odoo/odoo#40864
im_livechat main controller was referring to website.visitor but this module is not depending on website. The usage of website visitor's name should have been done in website_livechat module. This commit fix this issue. Task ID: 2116715 Forward-Port-Of: odoo/odoo#40732
Original PR description
im_livechat main controller was referring to website.visitor but this module is not depending on website. The usage of website visitor's name should have been done in website_livechat module. This commit fix this issue. Task ID: 2116715 Forward-Port-Of: odoo/odoo#40732
The slide.slide "_compute_slides_statistics" method is missing the 'slide_ids' trigger. It should be specified for cases when one of the slide_ids changes category. This can cause some CacheMiss and seem related to nondeterministic errors on the runbot. Task#2123711 Runbot build error ID 247 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 a
Original PR description
The slide.slide "_compute_slides_statistics" method is missing the 'slide_ids' trigger. It should be specified for cases when one of the slide_ids changes category. This can cause some CacheMiss and seem related to nondeterministic errors on the runbot. Task#2123711 Runbot build error ID 247 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#40705
Task:https://www.odoo.com/web#id=2063293&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.c134d9b0d8ea08eb773491d23bb96507 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40626 Forward-Port-Of: odoo/odoo#40467
Original PR description
Task:https://www.odoo.com/web#id=2063293&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.c134d9b0d8ea08eb773491d23bb96507 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40626 Forward-Port-Of: odoo/odoo#40467
Before this commit, the computation of KPI for last week, last 30 days and previous the period comparison was wrong due to the cache. it was going to get cache value instead of recomputing each time while start_date and end_date will be different in context each time and computation should be based on that date so we need to recompute each time. so invalidate cache after each computes to recompute the value again based on context start_date and end_date. Task: https://www.odoo.com/we
Original PR description
Before this commit, the computation of KPI for last week, last 30 days and previous the period comparison was wrong due to the cache. it was going to get cache value instead of recomputing each time while start_date and end_date will be different in context each time and computation should be based on that date so we need to recompute each time. so invalidate cache after each computes to recompute the value again based on context start_date and end_date. Task: https://www.odoo.com/web?#id=1883428&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.4bdc2c8043f94f2ef5c3d476e430e1cb -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40834
previous behavior: fixed_price is a monetary field when setting up a fixed price for a pricelist, it takes into account the decimal accuracy from the current currency current behavior: fixed_price is a float field when setting up a fixed price for a pricelist, it takes into account the proper decimal accuracy setting ("Product Price") opw-2121964 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --
Original PR description
previous behavior:
fixed_price is a monetary field
when setting up a fixed price for a pricelist, it takes into account
the decimal accuracy from the current currency
current behavior:
fixed_price is a float field
when setting up a fixed price for a pricelist, it takes into account
the proper decimal accuracy setting ("Product Price")
opw-2121964
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#40777Task:https://www.odoo.com/web#id=2063293&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.c134d9b0d8ea08eb773491d23bb96507 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40466
Original PR description
Task:https://www.odoo.com/web#id=2063293&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.c134d9b0d8ea08eb773491d23bb96507 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40466
- Group the SO list view by Analytic Account - Go to a SO - Click on the stat button 'Timesheets' Traceback because the field `analytic_account_id` is not on Timesheets. opw-2124539 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#40518 Forward-Port-Of: odoo/odoo#40494
Original PR description
- Group the SO list view by Analytic Account - Go to a SO - Click on the stat button 'Timesheets' Traceback because the field `analytic_account_id` is not on Timesheets. opw-2124539 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#40518 Forward-Port-Of: odoo/odoo#40494
When you create a pos order, it is possible that the request timeout or the client loose the connection with the server, that will lead to not have the server_id of the order sent to the server. So when the client will try to synchronize the order again, it'll not send the server_id to the server, and the server will create a new order which is a duplicate of the one created when the client lost the connection. To avoid this duplication, we are using the pos_reference to find if there i
Original PR description
When you create a pos order, it is possible that the request timeout or the client loose the connection with the server, that will lead to not have the server_id of the order sent to the server. So when the client will try to synchronize the order again, it'll not send the server_id to the server, and the server will create a new order which is a duplicate of the one created when the client lost the connection. To avoid this duplication, we are using the pos_reference to find if there is an existing order like in 12.0 to avoid duplication. TASK-ID: 2127656 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#40600
Steps to reproduce the bug: - Let's consider Today = 21/11/2019 and Employee E - Create a new hr.leave.type LT and set a validity from 01/01/2020 to 31/12/2020 - Set mode = Free Allocation Request and Validation = No Validation - Try to create leave allocations for LT Bug: It was impossible to create a leave allocation for LT because Today < 01/01/2020 So it was impossible to allocate future leave. We had to wait the 01/01/2020 to make the allocation of LT leaves opw:2126300 Fo
Original PR description
Steps to reproduce the bug: - Let's consider Today = 21/11/2019 and Employee E - Create a new hr.leave.type LT and set a validity from 01/01/2020 to 31/12/2020 - Set mode = Free Allocation Request and Validation = No Validation - Try to create leave allocations for LT Bug: It was impossible to create a leave allocation for LT because Today < 01/01/2020 So it was impossible to allocate future leave. We had to wait the 01/01/2020 to make the allocation of LT leaves opw:2126300 Forward-Port-Of: odoo/odoo#40629
Forward-Port-Of: odoo/odoo#40512
Original PR description
Forward-Port-Of: odoo/odoo#40512
- Create a product tracked by lot - Create a delivery picking You are allowed to create a new lot for the product although the picking type doesn't allow it. This is because of the missing context key `active_picking_id` on which `_check_create` relies: https://github.com/odoo/odoo/blob/e5ee5e5b65f85d66c8d59594ead9eece172c4282/addons/stock/models/stock_production_lot.py#L50 opw-2128497 Description of the issue/feature this PR addresses: Current behavior before PR: Desired
Original PR description
- Create a product tracked by lot - Create a delivery picking You are allowed to create a new lot for the product although the picking type doesn't allow it. This is because of the missing context key `active_picking_id` on which `_check_create` relies: https://github.com/odoo/odoo/blob/e5ee5e5b65f85d66c8d59594ead9eece172c4282/addons/stock/models/stock_production_lot.py#L50 opw-2128497 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#40793
Reproduce the issue: - Install eCommerce app - Publish a product to your website - Add the product in your cart - Unpublish/make unsellable/archive the product The product is still in the cart and the checkout process can be done. Cause: There is no check for invalid products before displaying the cart This commit remove the invalid products while loading the cart. OPW-2092541 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavio
Original PR description
Reproduce the issue: - Install eCommerce app - Publish a product to your website - Add the product in your cart - Unpublish/make unsellable/archive the product The product is still in the cart and the checkout process can be done. Cause: There is no check for invalid products before displaying the cart This commit remove the invalid products while loading the cart. OPW-2092541 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#40168 Forward-Port-Of: odoo/odoo#39931
Task:https://www.odoo.com/web#id=1943829&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad:https://pad.odoo.com/p/r.8b01716aff9194fc2ffc735bd1c1cb67 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#32438
Original PR description
Task:https://www.odoo.com/web#id=1943829&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad:https://pad.odoo.com/p/r.8b01716aff9194fc2ffc735bd1c1cb67 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#32438
Task:https://www.odoo.com/web?debug=1#id=2071587&action=333&active_id=1520&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.f2abb48af6a8fc4f48d7ba86d3e22799 Forward-Port-Of: odoo/enterprise#6837 Forward-Port-Of: odoo/enterprise#5981
Original PR description
Task:https://www.odoo.com/web?debug=1#id=2071587&action=333&active_id=1520&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.f2abb48af6a8fc4f48d7ba86d3e22799 Forward-Port-Of: odoo/enterprise#6837 Forward-Port-Of: odoo/enterprise#5981
get_bic_and_iban returns a bic and a acc number. The bic is assumed to always be a string later in the code. The code now returns "" when there is no bic Forward-Port-Of: odoo/enterprise#6868
Original PR description
get_bic_and_iban returns a bic and a acc number. The bic is assumed to always be a string later in the code. The code now returns "" when there is no bic Forward-Port-Of: odoo/enterprise#6868
Task:https://www.odoo.com/web#id=2075173&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.a931b66dfa0ee2e9fbb26b374297db73 Forward-Port-Of: odoo/enterprise#6811
Original PR description
Task:https://www.odoo.com/web#id=2075173&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.a931b66dfa0ee2e9fbb26b374297db73 Forward-Port-Of: odoo/enterprise#6811