Thursday, July 21, 2022
16 changes · master
Enhancements to existing features
Point of Sale now automatically validates an order when the payment amount exactly matches the order total. This reduces an extra step for cashiers and helps speed up checkout while avoiding validation when payments do not fully match.
Original PR description
Only when the total payment is exactly the order's total price. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
POS orders connected through IoT are now covered by tests to ensure they are automatically validated once an electronic payment fully covers the amount due. This helps streamline checkout and reduces the chance of staff needing extra manual steps after payment.
Original PR description
Unfortunately, we need to write the test here in pos_iot for the feature to automatically validate an order when it's fully paid after an electronic payment.
Resolved issues and error corrections
This fix prevents duplicate planning entries from appearing and ensures allocated time matches the displayed total time. This helps managers and employees rely on planning views for accurate workload information.
Original PR description
in this commit, fixes the duplication pills are remove and total time and allocate time are equal. task: 2891983
Code cleanup and technical improvements
The public live chat experience is being modernized to use the same underlying structure as Odoo Discuss. This helps make future live chat improvements easier to deliver and maintain, with limited immediate visible change for users.
Original PR description
*: website_livechat This commit is a step towards refactoring the JS of public livechat, so that it reuses the same architecture as the code of Discuss. This implies code that uses JS models and OWL components. Task-2925850
Miscellaneous changes
Description of the issue/feature this PR addresses: Currently in many2many_avatar widget, image shrink with their container, make avatar user looking weird. Specially with vertical portrait image This PR will fix this kind of bug UI. Before:  After:  After:  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#96356
This commit increases the timeout for some steps in the `google_analytics_view_item` tour. The step would time out semi-regularly due to a timeout. TaskId-2925407 Forward-Port-Of: odoo/odoo#96370
Original PR description
This commit increases the timeout for some steps in the `google_analytics_view_item` tour. The step would time out semi-regularly due to a timeout. TaskId-2925407 Forward-Port-Of: odoo/odoo#96370
Forward-Port-Of: odoo/odoo#96438 Forward-Port-Of: odoo/odoo#96362
Original PR description
Forward-Port-Of: odoo/odoo#96438 Forward-Port-Of: odoo/odoo#96362
Steps to reproduce: - Load odoo on a small screen / mobile phone - Go to accounting > Miscellaneous Operations - Click on create -> The button to add a line in Journal Items is missing Cause of the issue: On mobile, the kanban view is used for Journal Items The kanban view used [0] has an attribute `create="false"` Solution: Override the `create` attribute when the kanban view is a subview [0]: https://github.com/odoo/odoo/blob/93520cc291ffb76dd1425e413f29653df37b4062/addons/
Original PR description
Steps to reproduce: - Load odoo on a small screen / mobile phone - Go to accounting > Miscellaneous Operations - Click on create -> The button to add a line in Journal Items is missing Cause of the issue: On mobile, the kanban view is used for Journal Items The kanban view used [0] has an attribute `create="false"` Solution: Override the `create` attribute when the kanban view is a subview [0]: https://github.com/odoo/odoo/blob/93520cc291ffb76dd1425e413f29653df37b4062/addons/account/views/account_move_views.xml#L94 opw-2870637 Forward-Port-Of: odoo/odoo#96289
Steps to reproduce: - Go to stock > Replenishment - Click on a forecast report widget - Go back using the browser arrows -> The page is redirected to another forecast report and the breadcrumbs are cleared Cause of the issue: The forecast report action uses the `window.history.pushState` to add the active model in the url. When going back, the new url is the same one but without the active model. We can get the correct behavior by doing `window.history.go(-2)
Original PR description
Steps to reproduce: - Go to stock > Replenishment - Click on a forecast report widget - Go back using the browser arrows -> The page is redirected to another forecast report and the breadcrumbs are cleared Cause of the issue: The forecast report action uses the `window.history.pushState` to add the active model in the url. When going back, the new url is the same one but without the active model. We can get the correct behavior by doing `window.history.go(-2)` in the console. Solution: Use `history.replaceState` instead opw-2917725 Forward-Port-Of: odoo/odoo#96423
Release notes: https://github.com/odoo/owl/releases/tag/v2.0.0-beta-14 Details: - [FIX] compiler: better handle update of properties with same value 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#95671
Original PR description
Release notes: https://github.com/odoo/owl/releases/tag/v2.0.0-beta-14 Details: - [FIX] compiler: better handle update of properties with same value 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#95671
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#94148
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#94148
Currently, two lost buttons will appear, if you go to the form view of a lead that has 100% probability. The difference between the two duplicated "Lost" buttons is that one ask for a "lost reason" before marking a lead/opportunity as lost, the other does not. After discussing with the PO for CRM, it appears that the button that asks for a "lost reason" should not be displayed for leads. This commit makes the necessary changes to reflect that behavior. opw-2886623 Forward-Port-Of: odoo/o
Original PR description
Currently, two lost buttons will appear, if you go to the form view of a lead that has 100% probability. The difference between the two duplicated "Lost" buttons is that one ask for a "lost reason" before marking a lead/opportunity as lost, the other does not. After discussing with the PO for CRM, it appears that the button that asks for a "lost reason" should not be displayed for leads. This commit makes the necessary changes to reflect that behavior. opw-2886623 Forward-Port-Of: odoo/odoo#96210 Forward-Port-Of: odoo/odoo#95911
- We should grant access right project.collaborator to internal user group, i think it only is typing mistake. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#96138
Original PR description
- We should grant access right project.collaborator to internal user group, i think it only is typing mistake. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#96138
Steps to reproduce: - set a pricelist: discount, global, 10% - set promotion program: free product - In pos, select the product Issue: The product is deducted at its lst_price and not at the discounted price such as in `Sales`. opw-2892748 Forward-Port-Of: odoo/odoo#96427 Forward-Port-Of: odoo/odoo#96016
Original PR description
Steps to reproduce: - set a pricelist: discount, global, 10% - set promotion program: free product - In pos, select the product Issue: The product is deducted at its lst_price and not at the discounted price such as in `Sales`. opw-2892748 Forward-Port-Of: odoo/odoo#96427 Forward-Port-Of: odoo/odoo#96016
Since last owl update, the way t-att-value works has been slightly changed, and now, each owl update will force the input to match the internal state of owl, even if it has been modified in the meantime. Because of that, the timer in the timesheet grid header could behave in a wrong way: if the user would modify the input state manually, then the internal state does not match the input, and any subsequent render would override the user value. We fix this by making sure that the intern
Original PR description
Since last owl update, the way t-att-value works has been slightly changed, and now, each owl update will force the input to match the internal state of owl, even if it has been modified in the meantime. Because of that, the timer in the timesheet grid header could behave in a wrong way: if the user would modify the input state manually, then the internal state does not match the input, and any subsequent render would override the user value. We fix this by making sure that the internal state is also updated. Note that this does not require a test, since a test was failing before this commit (with the owl update code in community) Forward-Port-Of: odoo/enterprise#29310
The special date changer on LU_BS_319 and LU_BS_ABR319 are incorrect. It says "At the beginning of the period". For example, user wants to extract a mid-term Balance Sheet and P&L. Fiscal year : 01/01/xx up to 12/31/xx Balance Sheet as of 06/30/xx At the beginning means : 06/01/xx While he expects "from the beginning" : 01/01/xx It is not enough to change the special date changer to "from the beginning" or the items on P&L accounts will be double counted in LU_BS_319 and LU_BS_321, r
Original PR description
The special date changer on LU_BS_319 and LU_BS_ABR319 are incorrect. It says "At the beginning of the period". For example, user wants to extract a mid-term Balance Sheet and P&L. Fiscal year : 01/01/xx up to 12/31/xx Balance Sheet as of 06/30/xx At the beginning means : 06/01/xx While he expects "from the beginning" : 01/01/xx It is not enough to change the special date changer to "from the beginning" or the items on P&L accounts will be double counted in LU_BS_319 and LU_BS_321, respectively "Profit and Loss brought forward" and "Profit and Loss for the financial year". Adapt the formula of LU_BS_319 and LU_BSABR_319. opw-2920822 Forward-Port-Of: odoo/enterprise#29692