Monday, February 24, 2020
46 changes
Enhancements to existing features
Updates made while editing a new record now apply consistently to related parent records in inherited data models. This reduces unexpected behavior during form changes and helps keep linked business data in sync before saving.
Original PR description
This makes the behavior of `onchange()` consistent in the case of inherited models (with `_inherits`).
New employee records now start with the gender field left blank instead of automatically selecting male. This avoids incorrect assumptions in HR data entry and helps ensure employee information is completed intentionally.
Original PR description
Pad:https://pad.odoo.com/p/r.a01ab56e8346d56713e51055c151f84d Task:https://www.odoo.com/web#id=2165484&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720
Saving a new time off request from the dashboard pop-up now closes the dialog immediately. This removes an extra click for employees and makes the request process smoother.
Original PR description
Purpose When you create a new "time off" request from the pop-up window, no need to click twice to close the dialog. Specifications close the dialog when the first time that we click on save button. Task-id: 2183096 PR: #45137
The help tooltip explaining automatic email deletion has been clarified across email-related screens. This makes it easier for users to understand what the setting does before enabling or disabling it.
Original PR description
PURPOSE The message for help tooltip of auto_delete field is not sufficiently clear for user to understand. SPECIFICATIONS Improving message for help tooltip by adding some extra details in it so user can easily understand about it for models mail.mail, mail.template and wizard mail_compose_message. LINKS PR https://github.com/odoo/odoo/pull/45063 Task-2055702 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
Access rights screens now let users group record rules by the related business object, matching the grouping already available for model access rights. This makes it easier for administrators to review and organize security rules when managing permissions.
Original PR description
Before this commit, There was no option to Group Record rules by Object. 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 an issue where employee expense analytics information could be erased when no default analytic account was found. It keeps expense entries more reliable and prevents related expense tests from failing when the analytic default integration is installed.
Original PR description
_onchange_product_id used to set hr_expense analytic_account_id & analytic_tag_ids to False if it could not find a default analytic account. Installing account_analytic_default_hr_expense made odoo/addons/hr_expense/tests/test_expenses.py tests fail - changed function name (no need to be a _onchange_product_id override) - removed super() & return - check if account_get() returns something Related to task 2182900
Miscellaneous changes
This commit set an index on column `picking_id` of table `stock_move_line`. Many sql requests on stock_move_line have picking_id in their where-clause. On a database filled with 1M pickings, reading a picking of 10 stock_move_lines is 60 times faster. 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
This commit set an index on column `picking_id` of table `stock_move_line`. Many sql requests on stock_move_line have picking_id in their where-clause. On a database filled with 1M pickings, reading a picking of 10 stock_move_lines is 60 times faster. 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#46131
If IoT Box is in access point mode and a server is configured the box try to reach the server. But in access point mode all requests are redirected to the box So now before return `True` in function `get_odoo_server_url` we verify if the service `hostapd` is inactive 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
If IoT Box is in access point mode and a server is configured the box try to reach the server. But in access point mode all requests are redirected to the box So now before return `True` in function `get_odoo_server_url` we verify if the service `hostapd` is inactive 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#46105
- The form view on `res.users` displays information about how many record rules, ACL and groups are applied to the users. In some cases the current users may not have the required access rights to compute those values. To fix this issue, the computed fields are now computed in `compute_sudo` mode -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46098 Forward-Port-Of: odoo/odoo#45634
Original PR description
- The form view on `res.users` displays information about
how many record rules, ACL and groups are applied to the users.
In some cases the current users may not have the required
access rights to compute those values.
To fix this issue, the computed fields are now computed
in `compute_sudo` mode
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#46098
Forward-Port-Of: odoo/odoo#45634Update the blackbox from v11 in v13. We had to make a new driver to be able to use the blackbox with the iotbox. We also had to make the new features compatible with the blackbox. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45961 Forward-Port-Of: odoo/odoo#39833
Original PR description
Update the blackbox from v11 in v13. We had to make a new driver to be able to use the blackbox with the iotbox. We also had to make the new features compatible with the blackbox. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45961 Forward-Port-Of: odoo/odoo#39833
Before this commit: When logged in and navigating on a frontend page, the accessible `ir.ui.menu` would be loaded in qcontext. Loading those menus performs alot of SQL request, up to ~2.000 requests on big databases such as Odoo.com for an user with a lot of access rights. Note that this qcontext computation in frontend was pointless in enterprise as the applications menu in frontend redirect to the backend without using it. This commit removes that computation from the qcontext. The
Original PR description
Before this commit: When logged in and navigating on a frontend page, the accessible `ir.ui.menu` would be loaded in qcontext. Loading those menus performs alot of SQL request, up to ~2.000 requests on big databases such as Odoo.com for an user with a lot of access rights. Note that this qcontext computation in frontend was pointless in enterprise as the applications menu in frontend redirect to the backend without using it. This commit removes that computation from the qcontext. The menus will be computed and loaded only when the user really needs it, when he is about to open the application menu. Forward-Port-Of: odoo/odoo#46044 Forward-Port-Of: odoo/odoo#45839
Every records created from frontend should have the website_id set to the current website. Most was done with 066cfc9598a3, but forum was missing it. Fixes #45749 Forward-Port-Of: odoo/odoo#46006 Forward-Port-Of: odoo/odoo#45982
Original PR description
Every records created from frontend should have the website_id set to the current website. Most was done with 066cfc9598a3, but forum was missing it. Fixes #45749 Forward-Port-Of: odoo/odoo#46006 Forward-Port-Of: odoo/odoo#45982
When creating a new user on-the-fly on the employee detail page (HR Settings/Related User), if the employee is never linked with a user before, the new created user will not be linked with the employee automatically and we have to select the user again. With this commit, the new created user will be linked with the employee automatically. Fixes #44442 Forward-Port-Of: odoo/odoo#45411
Original PR description
When creating a new user on-the-fly on the employee detail page (HR Settings/Related User), if the employee is never linked with a user before, the new created user will not be linked with the employee automatically and we have to select the user again. With this commit, the new created user will be linked with the employee automatically. Fixes #44442 Forward-Port-Of: odoo/odoo#45411
Since the commit e95ccf0 invalid client-side domain will raise the error So purpose of the task is to fix the invalid client-side domain. Task: 2196805 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45680
Original PR description
Since the commit e95ccf0 invalid client-side domain will raise the error So purpose of the task is to fix the invalid client-side domain. Task: 2196805 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45680
For a upgrade the IoT Box perform a "git reset hard" And after we restart odoo. But it is not enough and we need to reboot the IoT Box 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#46079
Original PR description
For a upgrade the IoT Box perform a "git reset hard" And after we restart odoo. But it is not enough and we need to reboot the IoT Box 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#46079
- Activate the multi-step reception - Create a Subcontracting BOM for product P and supplier S. - Create a PO for S with P - Validate the PO - Validate the input transfer - Validate the internal transfer A error is raised because a mandatory field is not set. The root cause comes from the INT move being flagged as a subcontract move, while it shouldn't be. Indeed, only the input move should be flagged as subcontract. We force the `is_subcontract` value to `False` when a move is c
Original PR description
- Activate the multi-step reception - Create a Subcontracting BOM for product P and supplier S. - Create a PO for S with P - Validate the PO - Validate the input transfer - Validate the internal transfer A error is raised because a mandatory field is not set. The root cause comes from the INT move being flagged as a subcontract move, while it shouldn't be. Indeed, only the input move should be flagged as subcontract. We force the `is_subcontract` value to `False` when a move is copied in the context of a stock rule. opw-2193009 opw-2202727 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#46053
related to 896e36e Fixes #41813 Forward-Port-Of: odoo/odoo#46071 Forward-Port-Of: odoo/odoo#46021
Original PR description
related to 896e36e Fixes #41813 Forward-Port-Of: odoo/odoo#46071 Forward-Port-Of: odoo/odoo#46021
If you have a currency with 3 decimals, when you show a list view grouped, you might have result like: [group partner 1 : amount : 4.4€] - amount : 1.11€ - amount : 3.33€ which is a little odd, it is not that odd since the groupings are an approximation (eg. you could have a line in EUR and a line in USD and the grouping value would be the sum of both line). But there is no way to specify another precision, and since this is a grouping it could be of line of
Original PR description
If you have a currency with 3 decimals, when you show a list view
grouped, you might have result like:
[group partner 1 : amount : 4.4€]
- amount : 1.11€
- amount : 3.33€
which is a little odd, it is not that odd since the groupings are an
approximation (eg. you could have a line in EUR and a line in USD and
the grouping value would be the sum of both line).
But there is no way to specify another precision, and since this is a
grouping it could be of line of different currencies so we can't use the
lines currency to decide.
With this changeset, having for example:
<field name="amount" digits="[69,3]"/>
with `digits` attribute is taken into account for the aggregate value
and it would be displayed with 3 decimals.
Without the fix, the added test fails with:
aggregates monetary use digits attribute if available
Expected: "2000.000", Result: "2000.00"
opw-2195042
Forward-Port-Of: odoo/odoo#45983
Forward-Port-Of: odoo/odoo#45545Steps to reproduce the bug: - Install Manufacturing - Go to General Settings/Inventory and tick Units of Measure - Create a product P (storable) with UOM kg - Create a Bill of Material for this product: e.g. 1 kg - Add a component C with UOM "kg", but in the BOM uses "g" - Create a MO for P, Mark as todo, Produce - Click on C to change the quantities (e.g. change the first line to 900 g) - Add a second line with 0.1 kg (as the uom of C is in kg, you are forced to set in kg) Bug:
Original PR description
Steps to reproduce the bug: - Install Manufacturing - Go to General Settings/Inventory and tick Units of Measure - Create a product P (storable) with UOM kg - Create a Bill of Material for this product: e.g. 1 kg - Add a component C with UOM "kg", but in the BOM uses "g" - Create a MO for P, Mark as todo, Produce - Click on C to change the quantities (e.g. change the first line to 900 g) - Add a second line with 0.1 kg (as the uom of C is in kg, you are forced to set in kg) Bug: The consumed quantity for C in the MO was 900.1 g instead of 1000 g. opw:2181892 Forward-Port-Of: odoo/odoo#45737
fixes #19696 Forward-Port-Of: odoo/odoo#46048
Original PR description
fixes #19696 Forward-Port-Of: odoo/odoo#46048
PURPOSE The SMS confirmation settings have the right and meaning full name. SPECIFICATIONS Currently, SMS confirmation settings have name looks like a technical name so, user can not understand the feature what is it dose and what is its use. The main goal is to give a correct and meaning full name to SMS confirmation settings. To do that we modify the name of SMS confirmation settings "SMS Validation with stock move" to "SMS Validation". LINKS PR#46018 Task 2185325
Original PR description
PURPOSE The SMS confirmation settings have the right and meaning full name. SPECIFICATIONS Currently, SMS confirmation settings have name looks like a technical name so, user can not understand the feature what is it dose and what is its use. The main goal is to give a correct and meaning full name to SMS confirmation settings. To do that we modify the name of SMS confirmation settings "SMS Validation with stock move" to "SMS Validation". LINKS PR#46018 Task 2185325 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46018
Followup on 82ce815a8c4c978b3372282d88559282d32d4b07 When Content (`slide.slide`) is duplicated, public_views should not be copied for obvious reasons. 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#46011
Original PR description
Followup on 82ce815a8c4c978b3372282d88559282d32d4b07 When Content (`slide.slide`) is duplicated, public_views should not be copied for obvious reasons. 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#46011
This commit fixes an issue that raised an error when trying to create a slide.slide of type "category" on the slide.slide kanban view. Since it's not possible to disable the "group creation" on the kanban for a single filter, we disable it globally. At the same time, we removed the capability to drag and drop slides in that view. It was not very useful and could mess up the records by changing the slide type without changing the associated data (video link, presentation file, ...).
Original PR description
This commit fixes an issue that raised an error when trying to create a slide.slide of type "category" on the slide.slide kanban view. Since it's not possible to disable the "group creation" on the kanban for a single filter, we disable it globally. At the same time, we removed the capability to drag and drop slides in that view. It was not very useful and could mess up the records by changing the slide type without changing the associated data (video link, presentation file, ...). Issue #45452 Task 2201878 Forward-Port-Of: odoo/odoo#45930
It has been replaced by a button in the languages list & form views `Activate Language and Update Translations` Forward-Port-Of: odoo/odoo#46028
Original PR description
It has been replaced by a button in the languages list & form views `Activate Language and Update Translations` Forward-Port-Of: odoo/odoo#46028
Task 2198528 The xml id was duplicated, leading to a missing rule. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45598
Original PR description
Task 2198528 The xml id was duplicated, leading to a missing rule. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45598