Tuesday, October 31, 2023
49 changes · master
New functionality added to Odoo
Mail now includes a Chrome extension that lets users use push-to-talk controls across the system, not only while focused in Odoo. This makes voice conversations in Discuss easier to manage during multitasking and can improve meeting flow for teams.
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
Enhancements to existing features
This update makes two existing web tour helpers available for reuse in other parts of the system. It helps developers build custom interactions, such as drag-and-drop guided tours, more easily while keeping the change internal and low risk.
Original PR description
Add export to 'getDifferentParents' and 'triggerPointerEvent'. It is useful for creating a custom drag and drop for example. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Users can now save a record immediately after correcting an invalid field, without needing to click away first. The domain editor debug input also correctly marks changes right away, preventing edits from being missed when saving views.
Original PR description
First commit adds the possibility to manually reset the validity of a record's field. This is put to use in the input field hook where it allows users to directly save the record after having corrected the value of an invalid input field without needing to focus out of it to trigger the onChange. Second commit fixes an issue linked to the domain selector debug input which wouldn't set the view as dirty when used in the domain field until the user would focus away from it, preventing the user to directly save the view after editing it. task-3333060
Features or functions removed from Odoo
An unused internal helper was removed from the web module because it was no longer referenced anywhere. This keeps the codebase cleaner and slightly easier to maintain, with no expected impact on users or business workflows.
Original PR description
In this commit, we remove unused escapeMethod exported const that is no more unused in codebase.
Miscellaneous changes
Current behavior before PR: On creating link in debug mode produces prop validation error, and link dialog doesn't appear Desired behavior after PR is merged: Now the issue is resolved and link dialog appears. task-3571940 Forward-Port-Of: odoo/odoo#139851
Original PR description
Current behavior before PR: On creating link in debug mode produces prop validation error, and link dialog doesn't appear Desired behavior after PR is merged: Now the issue is resolved and link dialog appears. task-3571940 Forward-Port-Of: odoo/odoo#139851
The warehouse barcode reference PDF now includes the return action barcode, making it easier for staff to access return workflows from printed materials. This helps reduce confusion and supports smoother stock handling operations.
Financial report setup is now easier to manage because report lines are shown in their hierarchy. Users can move or delete a parent line together with all of its child lines, reducing manual work and the risk of inconsistent report structures.
Original PR description
The goal of this task is to make the creation and edition of reports easier. Now, the report edition page: * show the lines with hierarchy * allows the user to drag and drop a parent line and all its children at the same time * allows the user to delete a parent line and all its children at the same time To do that we created a new widget `account_report_x2many` that overrides the `x2ManyFiled` used in the view.
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#140181
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#140181
Purpose: -------- Before this commit, if you edit a char field with an onchange in an x2many, the FormStatusIndicator buttons will flicker. How to reproduce: ----------------- - Go to a form view with an x2many field in list mode - Type a char in the char field of a record - The FormStatusIndicator buttons are visible - Click outside the char field - An onchange is triggered Before this commit: The FormStatusIndicator buttons will disappear until the onchange returns. Afte
Original PR description
Purpose:
--------
Before this commit, if you edit a char field with an onchange in
an x2many, the FormStatusIndicator buttons will flicker.
How to reproduce:
-----------------
- Go to a form view with an x2many field in list mode
- Type a char in the char field of a record
- The FormStatusIndicator buttons are visible
- Click outside the char field
- An onchange is triggered
Before this commit:
The FormStatusIndicator buttons will disappear until the onchange returns.
After this commit:
The FormStatusIndicator buttons remain visible.
Forward-Port-Of: odoo/odoo#140179It's bad practice to use the "extension" inheritance mode for a custom component. In this case, inheritance is only necessary for the "StockMoveX2ManyField" custom field. In this commit, we will therefore use primary mode to generate a custom template used only by "StockMoveX2ManyField". 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
Original PR description
It's bad practice to use the "extension" inheritance mode for a custom component. In this case, inheritance is only necessary for the "StockMoveX2ManyField" custom field. In this commit, we will therefore use primary mode to generate a custom template used only by "StockMoveX2ManyField". 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#140301
## [IMP] sale_project: Include Archived Project in stat-button related views. ### [Context] Sales Order can be connected to projects. Before this commit archived projects were counted in the stat-button, but not in the related to stat-button project kanban view. We want to show archived (i.e. "non active") projects in both. ### [Reproduce behaviour before this commit]: - run odoo 15 with: sale_management,project,timesheet_grid - In Project, create: - project A - project B - In S
Original PR description
## [IMP] sale_project: Include Archived Project in stat-button related views. ### [Context] Sales Order can be connected to projects. Before this commit archived projects were counted in the…
## [IMP] sale_project: Include Archived Project in stat-button related views. ### [Context] Sales Order can be connected to projects. Before this commit archived projects were counted in the stat-button, but not in the related to stat-button project kanban view. We want to show archived (i.e. "non active") projects in both. ### [Reproduce behaviour before this commit]: - run odoo 15 with: sale_management,project,timesheet_grid - In Project, create: - project A - project B - In Sales/Products/Products, create: - product A (set: type="Service", Create on Order="Task", project="project A") - product B (set: type="Service", Create on Order="Task", project="project B") - In Salse/Orders/Quotations: - Create Quotation - add "product A" and "product B" - save & Confirm - OBSERVE: stat-button "projects" shows 2 projects - Click on: stat-button "projects" - OBSERVE: kanban view shows 2 projects - Archive one of project - go Project/"Project A"/Edit/Action/Archive (require debug mode) - Go back to created Quotation - OBSERVE (Desired): stat-button "projects" shows 2 projects - Click on: stat-button "projects" and OBSERVE - OBSERVE (Not-Desired): kanban view shows 1 projects (it excluded archived one) ### [Fix] Modified domain in the function/action related to the stat-button. opw-3500711 ## Some More context Originally this PR was supposed to exclude archived projects from count in the stat-button. Initial PR description below for context. > ## [FIX] sale_project: Archived Project Shall Not Be Counted In Smart Button > > ### [Context] > Archived Projects shouldn't be counted. If you associated 2 projects with some Sales Order and one project got archived, magic button counter (located on sale order form view) should get decreased to show only active projects. > > ### [To Reproduce]: > - run odoo 15 with: sale_management,project,timesheet_grid > - In Project, create: > - project A > - project B > - In Sales/Products/Products, create: > - product A (set: type="Service", Create on Order="Task", project="project A") > - product B (set: type="Service", Create on Order="Task", project="project B") > - In Salse/Orders/Quotations: > - Create Quotation > - add "product A" and "product B" > - save & Confirm > - OBSERVE: magic-button "projects" shows 2 projects > - Archive one project > - go Project/"Project A"/Edit/Action/Archive (require debug mode) > - Go back to created Quotation > - OBSERVE BUG: magic-button "projects" shows 2 projects (still) > > ### [Fix] > I'm performing additional filtering to explude archived (not active) projects. > > opw-3500711 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140018 Forward-Port-Of: odoo/odoo#138074
**Before this PR:** the scoring field was the only remaining thing in the 'Time and Scoring' Section which is read-only when `survey_type` is set to 'survey'. so there was no point of showing the whole section. **After this PR:** The 'Time and Scoring' Section will be invisible if `survey_type` is set to survey'. **Task**-3367524 Forward-Port-Of: odoo/odoo#139041
Original PR description
**Before this PR:** the scoring field was the only remaining thing in the 'Time and Scoring' Section which is read-only when `survey_type` is set to 'survey'. so there was no point of showing the whole section. **After this PR:** The 'Time and Scoring' Section will be invisible if `survey_type` is set to survey'. **Task**-3367524 Forward-Port-Of: odoo/odoo#139041
When decreasing the qty of a subcontracted POL, it can create an unexpected receipt To reproduce the issue: 1. Create a BoM for a subcontracted product P 2. Create and confirm a PO with 5 x P 3. Process the receipt 4. Return one 5. Update the POL qty to 4 Error: a new receipt is created for 3 x P. When updating the POL, nothing should happen with the receipts Updating the POL qty leads to the create/update of the related picking: https://github.com/odoo/odoo/blob/1495b54aa452498
Original PR description
When decreasing the qty of a subcontracted POL, it can create an unexpected receipt To reproduce the issue: 1. Create a BoM for a subcontracted product P 2. Create and confirm a PO with 5 x P 3.…
When decreasing the qty of a subcontracted POL, it can create an unexpected receipt To reproduce the issue: 1. Create a BoM for a subcontracted product P 2. Create and confirm a PO with 5 x P 3. Process the receipt 4. Return one 5. Update the POL qty to 4 Error: a new receipt is created for 3 x P. When updating the POL, nothing should happen with the receipts Updating the POL qty leads to the create/update of the related picking: https://github.com/odoo/odoo/blob/1495b54aa452498c79f4178c2e38426b1b423e66/addons/purchase_stock/models/purchase.py#L426 And this will lead to `_prepare_stock_moves`: https://github.com/odoo/odoo/blob/1495b54aa452498c79f4178c2e38426b1b423e66/addons/purchase_stock/models/purchase.py#L447-L450 Where we will define the values of the new SM (for the new qty). However, there are two similar issues: to get the current qty, we sum the quantities of the incoming/outgoing stock moves. But, the condition is incorrect and we therefore consider the subcontracting return as an incoming qty. So, this current qty is incorrect. Then, we get the dest moves to compute some quantities to push/attach. Here is the second issue, the filter condition to exclude the return SM is incorrect: again, we don't exclude the subcontracting return OPW-3515275 Forward-Port-Of: odoo/odoo#139720 Forward-Port-Of: odoo/odoo#138836
Before this PR, newly created direct message would be added at the bottom of the list instead of the top. This PR fix the issues by sorting the direct messages when creating a new direct message channel. Task-3566728 Forward-Port-Of: odoo/odoo#139769 Forward-Port-Of: odoo/odoo#139704
Original PR description
Before this PR, newly created direct message would be added at the bottom of the list instead of the top. This PR fix the issues by sorting the direct messages when creating a new direct message channel. Task-3566728 Forward-Port-Of: odoo/odoo#139769 Forward-Port-Of: odoo/odoo#139704
1. Install l10n_pos_in 2. Make an order 3. Observer traceback in receipt screen Similar problem in restaurant ( in bill screen ) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140123
Original PR description
1. Install l10n_pos_in 2. Make an order 3. Observer traceback in receipt screen Similar problem in restaurant ( in bill screen ) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140123
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#140051
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#140051
Steps: - Install `website_sale` - Enable `On-site payment & picking` - Set 200$ for on-site picking fees - Go to /shop - Put a product in the cart and go to checkout If you click in the element box containing on-site picking it will compute the delivery fees, but if you select it with the radio button it will not. Forward-Port-Of: odoo/odoo#139562
Original PR description
Steps: - Install `website_sale` - Enable `On-site payment & picking` - Set 200$ for on-site picking fees - Go to /shop - Put a product in the cart and go to checkout If you click in the element box containing on-site picking it will compute the delivery fees, but if you select it with the radio button it will not. Forward-Port-Of: odoo/odoo#139562
This PR fixes few issues needed for the certification of the sweden and belgian blackbox --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#133654
Original PR description
This PR fixes few issues needed for the certification of the sweden and belgian blackbox --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#133654
Since https://github.com/odoo/odoo/commit/3c62ca1eb96d571b2b686b5caee370324c589ab4, name_get is depreciated. We should replace it with a _compute_display_name. Linked to runbot error 25698 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#139082
Original PR description
Since https://github.com/odoo/odoo/commit/3c62ca1eb96d571b2b686b5caee370324c589ab4, name_get is depreciated. We should replace it with a _compute_display_name. Linked to runbot error 25698 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#139082
Before, error handling didn't work in point_of_sale when offline. This was due to poor error handling. Now, the "limited functionnalities" popup is displayed correctly. Forward-Port-Of: odoo/odoo#140037
Original PR description
Before, error handling didn't work in point_of_sale when offline. This was due to poor error handling. Now, the "limited functionnalities" popup is displayed correctly. Forward-Port-Of: odoo/odoo#140037
Corrects typos found when translating Odoo 17. \* : hr_fleet, payment Enterprise: https://github.com/odoo/enterprise/pull/49881 Forward-Port-Of: odoo/odoo#140282
Original PR description
Corrects typos found when translating Odoo 17. \* : hr_fleet, payment Enterprise: https://github.com/odoo/enterprise/pull/49881 Forward-Port-Of: odoo/odoo#140282
Forward-Port-Of: odoo/odoo#140340
Original PR description
Forward-Port-Of: odoo/odoo#140340
Before this commit, messages in livechat from visitor POV show 2 emoji icon in the quick actions. This is confusing and comes from 2 actions sharing this exact same icon: "Add a reaction" and "View reactions". This commit fixes the issue by reducing the number of quick message actions to 2 for the embed live chat. In other contexts there's "Reply-to" and "Mark as Favorite" in quick actions, so the "View reactions" item is always in expand menu. Note that this "dirty" fixes come from 2 acti
Original PR description
Before this commit, messages in livechat from visitor POV show 2 emoji icon in the quick actions. This is confusing and comes from 2 actions sharing this exact same icon: "Add a reaction" and "View reactions". This commit fixes the issue by reducing the number of quick message actions to 2 for the embed live chat. In other contexts there's "Reply-to" and "Mark as Favorite" in quick actions, so the "View reactions" item is always in expand menu. Note that this "dirty" fixes come from 2 actions with same icon. Eventually we should fix that by clearly making icons unique. This solution is decent for the time being, giving us more time to make a dedicate icon for one of the emoji actions. task-3498446 Forward-Port-Of: odoo/odoo#140335
Prior to this commit, when you removed all social links in the header, there was an error. This is because `website.header_social_links_no_color` targets selectors that don't exist in this situation. This commit adapts this template so that it works even if we remove all social links. task-3572219 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#139883
Original PR description
Prior to this commit, when you removed all social links in the header, there was an error. This is because `website.header_social_links_no_color` targets selectors that don't exist in this situation. This commit adapts this template so that it works even if we remove all social links. task-3572219 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#139883
Fixes 3 things related to auto-printing: - lot/product label printing due to refactor changing the label wizard's variable values - correctly redirect to barcode view after auto-printing (i.e. missed applied a refactor of `on_close` => `onClose`) - ensure that the multi-print action always has a context due to it being needed sometimes (i.e. for setting Shop Floor/MES context) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo
Original PR description
Fixes 3 things related to auto-printing: - lot/product label printing due to refactor changing the label wizard's variable values - correctly redirect to barcode view after auto-printing (i.e. missed applied a refactor of `on_close` => `onClose`) - ensure that the multi-print action always has a context due to it being needed sometimes (i.e. for setting Shop Floor/MES context) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140352
In this commit, we are adding partner to the order receipt as it is needed for the receipt in india and for the loyalty module. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140046
Original PR description
In this commit, we are adding partner to the order receipt as it is needed for the receipt in india and for the loyalty module. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140046
Currently, although the journals are filtered to only show purchase journals, there is no constraint preventing users from creating a new journal of any other type. This commit adds a constraint. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140344
Original PR description
Currently, although the journals are filtered to only show purchase journals, there is no constraint preventing users from creating a new journal of any other type. This commit adds a constraint. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140344
See https://github.com/odoo/odoo/pull/139871#discussion_r1377199846 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140418
Original PR description
See https://github.com/odoo/odoo/pull/139871#discussion_r1377199846 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140418
Prior to this commit, the content of the payment summary did not include line breaks when the text was too long, creating layout issue. To fix that, this commit adapts the font size and forces the text to break. task-3576830 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140423
Original PR description
Prior to this commit, the content of the payment summary did not include line breaks when the text was too long, creating layout issue. To fix that, this commit adapts the font size and forces the text to break. task-3576830 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140423
- using a string to join `Markup`s is useless, that just strips out the `Markup` - the entire toplevel `Markup` can be formatted in one shot Forward-Port-Of: odoo/odoo#140428
Original PR description
- using a string to join `Markup`s is useless, that just strips out the `Markup` - the entire toplevel `Markup` can be formatted in one shot Forward-Port-Of: odoo/odoo#140428
`''.join` would strip the `Markup` out, so the markup would appear literally in the result instead of being interpreted as HTML. Also switch to using dict-style formatting, it's a touch clearer (and shorter) for this case, since `e` is already a dict (hopefully). Forward-Port-Of: odoo/odoo#140427
Original PR description
`''.join` would strip the `Markup` out, so the markup would appear literally in the result instead of being interpreted as HTML. Also switch to using dict-style formatting, it's a touch clearer (and shorter) for this case, since `e` is already a dict (hopefully). Forward-Port-Of: odoo/odoo#140427
**Current behavior before PR:** Channel was not getting unpinned after being deleted. **Desired behavior after PR is merged:** Channel gets unpinned for all the channel members after being deleted. Task-2814440 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#137624 Forward-Port-Of: odoo/odoo#107001
Original PR description
**Current behavior before PR:** Channel was not getting unpinned after being deleted. **Desired behavior after PR is merged:** Channel gets unpinned for all the channel members after being deleted. Task-2814440 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#137624 Forward-Port-Of: odoo/odoo#107001
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140407
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140407
Before this commit, the "OdooBot has a request" notification in the Messaging Menu -- which suggest to enable push notifications -- had a muted style, which looks as if the item is unimportant and was read by the current user. This is an important notification, at an equivalent level of importance than needaction notifications. This was already highlighted by this item contributing to the global Messaging Menu counter. This commit fixes the issue by not muting this notification. To do so,
Original PR description
Before this commit, the "OdooBot has a request" notification in the Messaging Menu -- which suggest to enable push notifications -- had a muted style, which looks as if the item is unimportant and…
Before this commit, the "OdooBot has a request" notification in the Messaging Menu -- which suggest to enable push notifications -- had a muted style, which looks as if the item is unimportant and was read by the current user. This is an important notification, at an equivalent level of importance than needaction notifications. This was already highlighted by this item contributing to the global Messaging Menu counter. This commit fixes the issue by not muting this notification. To do so, it adds a new props `muted` on `NotificationItem` component to determine whether it should style the notif as muted or not. Before the change, prop `hasMarkAsReadButton` was both used to show the "mark as read" button and also determine whether the notif is muted or not. This worked when all non-muted notification had the "mark as read" button, which is the case for all but "OdooBot has a request". Task-3566799 Before  After  Forward-Port-Of: odoo/odoo#140380 Forward-Port-Of: odoo/odoo#140326
This will help the upgrade process. Currently, there is an harcoded[^1] inherit tree stored in the upgrade source. By storing this information in the databases, we: - avoid this hardcoded list. - support more than the standard modules. task-3504720 [^1]: hardcoded, but autogenerated. 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
Original PR description
This will help the upgrade process. Currently, there is an harcoded[^1] inherit tree stored in the upgrade source. By storing this information in the databases, we: - avoid this hardcoded list. - support more than the standard modules. task-3504720 [^1]: hardcoded, but autogenerated. 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#140261
A traceback is generated if config currencies are none. This is because we are trying to access the 0 index which does not exist in a None object. Steps to reproduce: 1. Go to studio. 2. Click on reports. 3. Search for sale details. 4. Click on sale details report. Current Behavior: As we click on the sales details report, a traceback pops up. Expected Behavior: There should be no traceback and the report editor should open smoothly if nothing wrong. Note: We also remove Timez
Original PR description
A traceback is generated if config currencies are none. This is because we are trying to access the 0 index which does not exist in a None object. Steps to reproduce: 1. Go to studio. 2. Click on reports. 3. Search for sale details. 4. Click on sale details report. Current Behavior: As we click on the sales details report, a traceback pops up. Expected Behavior: There should be no traceback and the report editor should open smoothly if nothing wrong. Note: We also remove Timezone information from the start_date to match the format of the date when it's provided by the user. e.g. : "23/05/2024 08:25:34" instead of "23/05/2024 08:25:34 TZInfo" OPW-3501650 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140477 Forward-Port-Of: odoo/odoo#139574
Forward-Port-Of: odoo/odoo#140562
Original PR description
Forward-Port-Of: odoo/odoo#140562
This commit fixes these issues on `o_appointment_details_column` in responsive: - It was not taking all the available space it could take - There was a lack of spacing above the title - In portal layout (no website installed), the margin at the bottom of the column was creating an undesired white space task-3573765 Fixes issues introduced in this PR: https://github.com/odoo/enterprise/pull/41534 Forward-Port-Of: odoo/enterprise#49757
Original PR description
This commit fixes these issues on `o_appointment_details_column` in responsive: - It was not taking all the available space it could take - There was a lack of spacing above the title - In portal layout (no website installed), the margin at the bottom of the column was creating an undesired white space task-3573765 Fixes issues introduced in this PR: https://github.com/odoo/enterprise/pull/41534 Forward-Port-Of: odoo/enterprise#49757
task-3561708 Forward-Port-Of: odoo/enterprise#49715
Original PR description
task-3561708 Forward-Port-Of: odoo/enterprise#49715
Forward-Port-Of: odoo/enterprise#48687
Original PR description
Forward-Port-Of: odoo/enterprise#48687
Fixes 2 cases of the return button in barcode showing when it shouldn't. - when in the "info" view of the picking then the button was showing on top of the chatter when it shouldn't show in this view at all - in done manufacturing orders Note that a getter isn't added to the JS to handle whether or not the button should be shown because mrp_model extends the picking_model and batch pickings do not currently offer the "Return" option in the backend, so it didn't seem necessary to create a ge
Original PR description
Fixes 2 cases of the return button in barcode showing when it shouldn't. - when in the "info" view of the picking then the button was showing on top of the chatter when it shouldn't show in this view at all - in done manufacturing orders Note that a getter isn't added to the JS to handle whether or not the button should be shown because mrp_model extends the picking_model and batch pickings do not currently offer the "Return" option in the backend, so it didn't seem necessary to create a getter to only override it to be "False" for mrp_model only. Forward-Port-Of: odoo/enterprise#49824
Corrects typos found when translating Odoo 17. *: appointment_account_payment, maintenance_worksheet, mrp_workorder Community: https://github.com/odoo/odoo/pull/140391 Forward-Port-Of: odoo/enterprise#49831
Original PR description
Corrects typos found when translating Odoo 17. *: appointment_account_payment, maintenance_worksheet, mrp_workorder Community: https://github.com/odoo/odoo/pull/140391 Forward-Port-Of: odoo/enterprise#49831
Previously, when PoS was in offline mode, paid orders were not sent to preparation display due to poor error handling. Now, when the PoS is offline and reconnects, paid orders are sent to the preparation display via the create_from_ui function. Forward-Port-Of: odoo/enterprise#49705
Original PR description
Previously, when PoS was in offline mode, paid orders were not sent to preparation display due to poor error handling. Now, when the PoS is offline and reconnects, paid orders are sent to the preparation display via the create_from_ui function. Forward-Port-Of: odoo/enterprise#49705
This commit adds new action buttons to the Knowledge's tree view when selecting articles. We added the buttons `Restore` and `Send to Trash`. `Restore` is seen in the Trash view and `Send to Trash` in the Search list view. Those are used to either send an article to the trash or to restore them from it in batch. task-3470267 Forward-Port-Of: odoo/enterprise#47502
Original PR description
This commit adds new action buttons to the Knowledge's tree view when selecting articles. We added the buttons `Restore` and `Send to Trash`. `Restore` is seen in the Trash view and `Send to Trash` in the Search list view. Those are used to either send an article to the trash or to restore them from it in batch. task-3470267 Forward-Port-Of: odoo/enterprise#47502
In this PR, we update both sweden and belgian localisation for the point of sale. There is also a renaming to fit the odoo guide lines about the module naming. For both module, we make them depend of the new pos_proforma module. They both have mandatory pro forma order and re use the same code. Now, instead of duplicate the code, we can use everything from the new module. For the sweden, we make sure that the black box is receiving the correct information. For the belgian, it's a first
Original PR description
In this PR, we update both sweden and belgian localisation for the point of sale. There is also a renaming to fit the odoo guide lines about the module naming. For both module, we make them depend of the new pos_proforma module. They both have mandatory pro forma order and re use the same code. Now, instead of duplicate the code, we can use everything from the new module. For the sweden, we make sure that the black box is receiving the correct information. For the belgian, it's a first step for the v17 certification. Forward-Port-Of: odoo/enterprise#46580
- [[FIX] sale_subscription: portal payment fix](https://github.com/odoo/enterprise/pull/49713/commits/448bb332ea551124126d1df43ee3a5dba871a875) - [[FIX] sale_subscription: hide upsell in all_subscription](https://github.com/odoo/enterprise/pull/49713/commits/993a21d48ea0c6246aabbc1b2a7537615a55d705) - [[FIX] sale_subscription: small code improvement](https://github.com/odoo/enterprise/pull/49713/commits/2e41e9c277ba5238171cca25e8072faa2543334f) - [[FIX] sale_subcription: close change_plan doe
Original PR description
- [[FIX] sale_subscription: portal payment fix](https://github.com/odoo/enterprise/pull/49713/commits/448bb332ea551124126d1df43ee3a5dba871a875) - [[FIX] sale_subscription: hide upsell in…
- [[FIX] sale_subscription: portal payment fix](https://github.com/odoo/enterprise/pull/49713/commits/448bb332ea551124126d1df43ee3a5dba871a875) - [[FIX] sale_subscription: hide upsell in all_subscription](https://github.com/odoo/enterprise/pull/49713/commits/993a21d48ea0c6246aabbc1b2a7537615a55d705) - [[FIX] sale_subscription: small code improvement](https://github.com/odoo/enterprise/pull/49713/commits/2e41e9c277ba5238171cca25e8072faa2543334f) - [[FIX] sale_subcription: close change_plan doesn't update plan](https://github.com/odoo/enterprise/pull/49713/commits/51a9dc4526e03ed4e1bd31a532a8a12d21d20ebe) - [[FIX] sale_subscription: show plan if no template](https://github.com/odoo/enterprise/pull/49713/commits/aa60ef00fb7ac96752a33d73470e4f24d94c49ee) - [[FIX] sale_subscription: SO template hidden when no group](https://github.com/odoo/enterprise/pull/49713/commits/ee0fcad905f3afa2d48083ec22f07567e5ba2dd4) - [[IMP] sale_subscription: move from demo_data to data](https://github.com/odoo/enterprise/pull/49713/commits/3cf7d809c93443e18abb5b8902a100d5a9c9fd1c) PR COM: odoo/odoo#140051 PR ENT: odoo/enterprise#49713 task-id : 3571692 Forward-Port-Of: odoo/enterprise#49713
Before this commit, the field is only visible if the user has no access to timesheet app. The problem is the field could be prefetched once the user has access to timesheet app even if he is not `HR User`. This commit changes the `groups` defined in definition of `billable_time_target` field to only fetch the field if the user is at least HR User, however, the field will be only visible in the form view of `hr.employee` model if the user is at least Timesheet Approver. task-3573317
Original PR description
Before this commit, the field is only visible if the user has no access to timesheet app. The problem is the field could be prefetched once the user has access to timesheet app even if he is not `HR User`. This commit changes the `groups` defined in definition of `billable_time_target` field to only fetch the field if the user is at least HR User, however, the field will be only visible in the form view of `hr.employee` model if the user is at least Timesheet Approver. task-3573317 Forward-Port-Of: odoo/enterprise#49712
Steps to reproduce: - Install website_sale_renting; - Log in as portal user; - Go to /shop on a page where there is a rental product; - Access error The error is raised because there is a missing access rule for portal user. As there is a read access to public user, we add it to portal user as well. Backport of https://github.com/odoo/enterprise/pull/49583 Forward-Port-Of: odoo/enterprise#49708
Original PR description
Steps to reproduce: - Install website_sale_renting; - Log in as portal user; - Go to /shop on a page where there is a rental product; - Access error The error is raised because there is a missing access rule for portal user. As there is a read access to public user, we add it to portal user as well. Backport of https://github.com/odoo/enterprise/pull/49583 Forward-Port-Of: odoo/enterprise#49708
Forward-Port-Of: odoo/enterprise#49862
Original PR description
Forward-Port-Of: odoo/enterprise#49862