Tuesday, July 28, 2020
17 changes · master
Enhancements to existing features
Outdated reporting filter settings were replaced with their current equivalents in Recruitment and Point of Sale. This helps keep reports consistent with the modern system behavior and reduces maintenance risk without changing day-to-day workflows.
Original PR description
…t_measures and pivot_column_groupby. Task: https://www.odoo.com/web#id=33834&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Adds a new display option so time values can omit unnecessary zero minutes, showing values like 1 instead of 1:00. This improves readability for grid totals and similar views where compact time summaries are easier for users to scan.
Original PR description
This commit adds noZeroMinuteHour option to formatFloatTime. The noZeroMinuteHour option can be used to format the value like 1 instead of 1:30 This format behavior is wanted for fields in the web_grid module. task - 2261846
Analytic fields on posted accounting entries are now read-only because changing them after posting has no practical effect. This reduces confusion for users and helps keep posted financial records clearer and more consistent.
Original PR description
Analytics fields are currently updatable when the move has been posted, even though editing them as no effect. This change make them read-only when the move has been posted. Task ID: #2299319 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Several Odoo business apps were updated to replace outdated internal definitions for reports and window actions. This keeps payroll, accounting, rental, manufacturing, point of sale, and localization features compatible with newer platform standards without changing day-to-day workflows.
Features or functions removed from Odoo
Odoo is moving away from older shortcut tags used to define reports and window actions in module data files, replacing them with clearer standard definitions. This is mainly an internal cleanup that improves consistency for developers and reduces ambiguity, with little direct impact on day-to-day users.
Miscellaneous changes
- Create a repair order - Cancel the creation - Create another repair order There is a gap in the sequence number. The gap is due to the fact that the sequence number is consumed by the `default_get`. Although this is a change of behavior, the actual one is not really expected. Even if a gap is possible with the sequence, we don't want to consume a number every time we get the default values. opw-2301412 Description of the issue/feature this PR addresses: Current behavior
Original PR description
- Create a repair order - Cancel the creation - Create another repair order There is a gap in the sequence number. The gap is due to the fact that the sequence number is consumed by the `default_get`. Although this is a change of behavior, the actual one is not really expected. Even if a gap is possible with the sequence, we don't want to consume a number every time we get the default values. opw-2301412 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#54987
Original PR description
Cf odoo/odoo#54564 Task 2296297 Note: instances of `attachment_use="False"` were replaced by `<field name="attachment_use">True</field>`: `<report>` never evaluated that value, so specifying the attribute would always opt into attachment_use, unless the value was set to empty (at which point you might as well leave the attribute out).
Original PR description
Take a gander at how that looks like, as they seem pretty underwhelming in terms of gains and clarity Task 2296297 ## TODO: - [x] remove documentation for <report> tag - [x] convert use of `<report>` and `<act_window>` in exercise
Steps to reproduce the bug: - Create a promotional program P with company A - Change to company B and create a SO - Click on Promotion Bug: The promotion created in company A was applied to SO created in company B opw:2303169 Forward-Port-Of: odoo/odoo#54853
Original PR description
Steps to reproduce the bug: - Create a promotional program P with company A - Change to company B and create a SO - Click on Promotion Bug: The promotion created in company A was applied to SO created in company B opw:2303169 Forward-Port-Of: odoo/odoo#54853
Some PO lines could be ignore during _run_buy and _find_candidate. It happens since the sorted only take a function and a string do nothing. Close #53247 Forward-Port-Of: odoo/odoo#53330
Original PR description
Some PO lines could be ignore during _run_buy and _find_candidate. It happens since the sorted only take a function and a string do nothing. Close #53247 Forward-Port-Of: odoo/odoo#53330
### Issue - Safari - Sales with product configurator - Have a product with color black & white size M, XL - Exclude M size when color is white - Create a SO with that product - Select white color The size's M option is not grayed in the select ### Cause We do not disable the option when it's not available. We are just adding a css class which grays the option. Safari ignores the style ### Solution Since the flow can't be completed if you select a
Original PR description
### Issue - Safari - Sales with product configurator - Have a product with color black & white size M, XL - Exclude M size when color is white - Create a SO with that product - Select white color The size's M option is not grayed in the select ### Cause We do not disable the option when it's not available. We are just adding a css class which grays the option. Safari ignores the style ### Solution Since the flow can't be completed if you select a grayed item, disable the option **OPW-2289666** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54978
Steps to reproduce: - install studio, website and sales - go to sales > open studio > go to 'reports' > Quotation/Order - add a field anywhere on the report with the field expression set to "doc.signature" > save - go to sles > create a quotation > send by email > send > go to the customer portal - sign and send the quotation > go back to the edit mode > open the pdf attached to the latest message in the chatter Previous behavior: the custom field added was not rendered properly, the
Original PR description
Steps to reproduce: - install studio, website and sales - go to sales > open studio > go to 'reports' > Quotation/Order - add a field anywhere on the report with the field expression set to "doc.signature" > save - go to sles > create a quotation > send by email > send > go to the customer portal - sign and send the quotation > go back to the edit mode > open the pdf attached to the latest message in the chatter Previous behavior: the custom field added was not rendered properly, the attachment is not available during the request and the generated pdf shows the placeholder image instead Current behavior: the message posted in the chatter is generated in another request, this makes the attachment available opw-2260989 Forward-Port-Of: odoo/odoo#54732
Fix the standard effect with template logo on top/below to avoid an hopping when scrolling. task-2229127 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#51446
Original PR description
Fix the standard effect with template logo on top/below to avoid an hopping when scrolling. task-2229127 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#51446
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#55039 Forward-Port-Of: odoo/odoo#54899
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#55039 Forward-Port-Of: odoo/odoo#54899
Issue Traceback raised in case no link provided when content type is a video. Solution Format url only if provided. Related fix : https://github.com/odoo/odoo/pull/54536 opw-2294344 Forward-Port-Of: odoo/odoo#55052
Original PR description
Issue Traceback raised in case no link provided when content type is a video. Solution Format url only if provided. Related fix : https://github.com/odoo/odoo/pull/54536 opw-2294344 Forward-Port-Of: odoo/odoo#55052
According to the official rules from CCT 19/9, signed on April 2019 and applicable as of February 1st, 2020, the employe reimbursement for non-train-based public transportation, *when based on a flat fee*, is computed as 71.8% of the actual cost, capped at the reimbursement for 7km of train-based transportation (34.00 EUR) The rule can be found in [1], Chapter 4, Article 4, b), with the train reimbursement table in the same document, Article 3. [1] http://www.cnt-nar.be/CCT-COORD/c
Original PR description
According to the official rules from CCT 19/9, signed on April 2019 and applicable as of February 1st, 2020, the employe reimbursement for non-train-based public transportation, *when based on a flat fee*, is computed as 71.8% of the actual cost, capped at the reimbursement for 7km of train-based transportation (34.00 EUR)
The rule can be found in [1], Chapter 4, Article 4, b), with the train reimbursement table in the same document, Article 3.
[1] http://www.cnt-nar.be/CCT-COORD/cct-019-09.pdf
Forward-Port-Of: odoo/enterprise#11974d912d161a8299e676d175c7d70582480cb006a85 removed a bit too much Forward-Port-Of: odoo/enterprise#12056
Original PR description
d912d161a8299e676d175c7d70582480cb006a85 removed a bit too much Forward-Port-Of: odoo/enterprise#12056
Task [2300173](https://www.odoo.com/web#id=2300173&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720) The pencil was not shown for payment lines, which was a problem for reconciliation with outstanding amounts Forward-Port-Of: odoo/enterprise#11964
Original PR description
Task [2300173](https://www.odoo.com/web#id=2300173&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720) The pencil was not shown for payment lines, which was a problem for reconciliation with outstanding amounts Forward-Port-Of: odoo/enterprise#11964
Forward-Port-Of: odoo/enterprise#12052
Original PR description
Forward-Port-Of: odoo/enterprise#12052