Daily updates from Odoo
Navigate
Branch
Thursday, May 7, 2020
10 changes
Enhancements to existing features
Planning users can now see allocation percentages without needing a special access group. They can also allocate more than 100% of a slot when business needs require extra planned hours, reducing confusion from automatic resets.
Original PR description
Task 2229296
This update keeps Odoo Studio's view editor sidebar aligned with recent changes in the core web interface. It helps ensure Studio continues to work smoothly when editing views after the related platform update.
Resolved issues and error corrections
Default demonstration user access settings are now protected from being reapplied during module upgrades. This helps deployed databases keep their customized access choices instead of unexpectedly restoring broad admin rights on upgraded apps.
Original PR description
For demonstration purposes, the default user of a new database has admin rights on every app. Because deployed databases are expected to have modified those default groups, this commit ensures that the default value isn't brought back after module upgrades. Enterprise Counterpart of https://github.com/odoo/odoo/pull/49334 [Task Id - 2213520](https://www.odoo.com/web?#id=2213520&action=333&active_id=2818&model=project.task&view_type=form&cids=1&menu_id=4720)
Miscellaneous changes
Forward-Port-Of: odoo/enterprise#10430 Forward-Port-Of: odoo/enterprise#10422
Original PR description
Forward-Port-Of: odoo/enterprise#10430 Forward-Port-Of: odoo/enterprise#10422
In the `stock_barcode` app, user can get a traceback when trying to open a transfer who refers to a archived location. It was due to a replacement of `browse` (who doesn't filter on `active` field) by a `search_read` (who does it by default). task-2252729 Forward-Port-Of: odoo/enterprise#10432
Original PR description
In the `stock_barcode` app, user can get a traceback when trying to open a transfer who refers to a archived location. It was due to a replacement of `browse` (who doesn't filter on `active` field) by a `search_read` (who does it by default). task-2252729 Forward-Port-Of: odoo/enterprise#10432
Forward-Port-Of: odoo/enterprise#10425 Forward-Port-Of: odoo/enterprise#10415
Original PR description
Forward-Port-Of: odoo/enterprise#10425 Forward-Port-Of: odoo/enterprise#10415
In c104926332 close_hours ("Open Time (hours)") that was a stored field updated with a cron, was replaced by: - close_hours ("Time to close (hours)") a stored field set when a ticket moved to a "closed" stage - open_hours ("Open Time (hours)") equivalent of original close_hours field but that is not stored. This was not changed in the dashboard, so the statistics of hours would be over the number to close a ticket for open tickets (so 0 unless you close a ticket then re-open it). With th
Original PR description
In c104926332 close_hours ("Open Time (hours)") that was a stored field
updated with a cron, was replaced by:
- close_hours ("Time to close (hours)") a stored field set when a ticket
moved to a "closed" stage
- open_hours ("Open Time (hours)") equivalent of original close_hours
field but that is not stored.
This was not changed in the dashboard, so the statistics of hours would
be over the number to close a ticket for open tickets (so 0 unless you
close a ticket then re-open it).
With this changeset, we use the open_hours instead to get back to the
behavior before 13.0 version.
opw-2244822
Forward-Port-Of: odoo/enterprise#10380Step to reproduce: - Activate multi-companies feature - Switch to company B - Create a sign request with employee of company B in sign module - Switch to company A - Click on "Signatures" menu in sign module The error occures due to a right access issue; one company is not allowed to fetch employee of an other company. This commit add a "sudo()" request on partner_id.name to avoid the issue. Task ID 2244219 Forward-Port-Of: odoo/enterprise#10339 Forward-Port-Of: odoo/enterprise#1
Original PR description
Step to reproduce: - Activate multi-companies feature - Switch to company B - Create a sign request with employee of company B in sign module - Switch to company A - Click on "Signatures" menu in sign module The error occures due to a right access issue; one company is not allowed to fetch employee of an other company. This commit add a "sudo()" request on partner_id.name to avoid the issue. Task ID 2244219 Forward-Port-Of: odoo/enterprise#10339 Forward-Port-Of: odoo/enterprise#10283
See commit messages Forward-Port-Of: odoo/enterprise#10419 Forward-Port-Of: odoo/enterprise#9630
Original PR description
See commit messages Forward-Port-Of: odoo/enterprise#10419 Forward-Port-Of: odoo/enterprise#9630
Steps to reproduce the bug: - Let's consider a pricelist PL in € with 50% of discount on product P and discount_policy = without_discount - Let's consider a suscription product P with a sales price = 100€ - Create a subscription of P with PL Bug: The subtotal was 50€ but the discount was not displayed on the line opw:2240946 Forward-Port-Of: odoo/enterprise#10263 Forward-Port-Of: odoo/enterprise#10224
Original PR description
Steps to reproduce the bug: - Let's consider a pricelist PL in € with 50% of discount on product P and discount_policy = without_discount - Let's consider a suscription product P with a sales price = 100€ - Create a subscription of P with PL Bug: The subtotal was 50€ but the discount was not displayed on the line opw:2240946 Forward-Port-Of: odoo/enterprise#10263 Forward-Port-Of: odoo/enterprise#10224