Daily updates from Odoo
Navigate
Branch
Wednesday, November 16, 2022
26 changes
Enhancements to existing features
When a sales order line price is changed, Odoo now offers to update other lines that share the same pricing when at least two matching lines exist. This makes bulk pricing updates easier and reduces the chance of inconsistent prices across subscription-related sales lines.
Original PR description
When updating the pricing of a SOL, if there is at least 2 other lines with a similar pricing, a wizard pop up to ask if Odoo must update the pricing of those lines. Previously, this wizard only popped up when there was at least 2 other lines and all of them had a similar pricing. taskid-2859459
Users can now double-click spreadsheet cards in creation, insertion, and dashboard selection dialogs to confirm their choice immediately. This makes adding or creating spreadsheets faster and reduces extra clicks in common document and dashboard workflows.
Original PR description
… selection modal Double-clicking on a card of the spreadsheet modal (both insertion, creation, and selection modals) should submit it with the clicked item. Modals updated : - Documents => "Create a spreadsheet" modal - "Insert in spreadsheet" modal (for Graph/List/Pivot/Link inserted in spreadsheet/dashboard) - Dashboard configuration => "Add a spreadsheet" modal Odaoo task [2950594](https://www.odoo.com/web#id=2950594&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
This update makes Field Service easier to use by improving task search, clearer warning messages, and cleaner task reports. It also avoids showing irrelevant budget information when no project budget is linked, helping users focus on applicable details.
Original PR description
Purpose of this PR to improve generic usage of industry_fsm app. So, in this PR done following changes: -added quick search Description in project.task search view task-2924215
This update reworks the customer payment follow-up workflow to make reminders easier to manage and send. It adds better contact synchronization, manual reminder tools, email and postal mail options, and fixes issues around reconciliation and follow-up reporting.
Original PR description
This is a draft PR but I don't have access to mark it as draft task id: 2719175
Resolved issues and error corrections
Rental product availability is now computed more accurately during online sales, helping prevent customers from booking items that are not actually available. This improves the reliability of the rental checkout experience and reduces follow-up corrections for sales teams.
Code cleanup and technical improvements
This update removes a redundant email field from Helpdesk because the existing partner email information already covers the same need. It simplifies the underlying Helpdesk setup without changing day-to-day ticket handling for users.
Original PR description
[REF] helpdesk: remove useless field email `email` field is no more usefull as: - `partner_email` is a compute stored not readonly, thus creating a related non readonly is useless. - `partner_email` is used in `_message_get_default_recipients` prior to the `email` field task-3054699
Miscellaneous changes
Current behavior: While editing an empty worksheet template, adding an element raises an error (UnboundLocalError). Steps to reproduce: 1. Install Field Service and Worksheet 2. Go to the Field Service app 3. Open the Configuration > Worksheet Templates 4. Create a new template and click on Design Template 5. Remove everything from the view 6. Try adding anything to the view Solution: The issue comes from a local variable not set if the node is empty. Therefore, adding
Original PR description
Current behavior: While editing an empty worksheet template, adding an element raises an error (UnboundLocalError). Steps to reproduce: 1. Install Field Service and Worksheet 2. Go to the Field Service app 3. Open the Configuration > Worksheet Templates 4. Create a new template and click on Design Template 5. Remove everything from the view 6. Try adding anything to the view Solution: The issue comes from a local variable not set if the node is empty. Therefore, adding the line into the correct scope fixes the issue. opw-2995272 Forward-Port-Of: odoo/enterprise#31776
Before this PR, two flows going to the same view were broken. When "intrastat" is checked in the parameters: * the first flow "Accounting -> Reconciliation -> (if the text "Good job ! ..." appears) Press on unreconciled entries -> not the desired view", the view displayed is not the one we want. * The second flow "Chart of accounts -> configuration -> smart button Balance" the view displayed is also not the one we want. In fact, before you check "intrastat" in the settings, a tree view is a
Original PR description
Before this PR, two flows going to the same view were broken. When "intrastat" is checked in the parameters: * the first flow "Accounting -> Reconciliation -> (if the text "Good job ! ..." appears) Press on unreconciled entries -> not the desired view", the view displayed is not the one we want. * The second flow "Chart of accounts -> configuration -> smart button Balance" the view displayed is also not the one we want. In fact, before you check "intrastat" in the settings, a tree view is available thanks to the two flows explained above, but as soon as you check "intrastat", the tree view is replaced by another one because it will display the highest priority (the lowest number). Changing the priority of the intrastat tree view is enough to solve the problem. There is also no problem the other way around since the action is called directly when the particular tree view is needed. task-id: 3070967 Forward-Port-Of: odoo/enterprise#33993
Steps to reproduce: - Create a new unit of measure worth 50 hours - Create a service product that uses that uom - Activate the time billing on a helpdesk team settings - Create a sale order with the service product you created - Create a helpdesk ticket for that sale order - Add one hour on the ticket timesheets without saving Current behavior: The remaining hours count falls to zero Expected behavior: The remaining hours should be 49 Explanation: In _compute_remaining_hours we
Original PR description
Steps to reproduce: - Create a new unit of measure worth 50 hours - Create a service product that uses that uom - Activate the time billing on a helpdesk team settings - Create a sale order with the service product you created - Create a helpdesk ticket for that sale order - Add one hour on the ticket timesheets without saving Current behavior: The remaining hours count falls to zero Expected behavior: The remaining hours should be 49 Explanation: In _compute_remaining_hours we used the sale order line uom that does not match the true uom of the unit_amount in every scenario, instead we should use the product_uom_id. opw-2996610 Forward-Port-Of: odoo/enterprise#33896 Forward-Port-Of: odoo/enterprise#32393
Current behavior: Timesheet doesn't contain the correct name of the actual Access Right opw-2999292 Forward-Port-Of: odoo/enterprise#33853
Original PR description
Current behavior: Timesheet doesn't contain the correct name of the actual Access Right opw-2999292 Forward-Port-Of: odoo/enterprise#33853
When multiple partners match the detected supplier of the OCR, we will now select the one that has the highest supplier rank. See ticket #3045675 Forward-Port-Of: odoo/enterprise#33944
Original PR description
When multiple partners match the detected supplier of the OCR, we will now select the one that has the highest supplier rank. See ticket #3045675 Forward-Port-Of: odoo/enterprise#33944
Before this commit, total order value and currency were missing from information sent to sendcloud. Forward-Port-Of: odoo/enterprise#33688
Original PR description
Before this commit, total order value and currency were missing from information sent to sendcloud. Forward-Port-Of: odoo/enterprise#33688
The view was broken since the recent css change, the notebook manual operations is composed by two tables and one was below the other. Thanks to this PR it's now fixed, the two tables are now next to each other. Moreover the progress bar was just a purple square, the behaviour of v15.0 is now restore + adapted to dark mode This PR also correct multiple dark mode problem * White rectangle * Border * Hover Line * Hover Field The second commit is about duplicate function that needed
Original PR description
The view was broken since the recent css change, the notebook manual operations is composed by two tables and one was below the other. Thanks to this PR it's now fixed, the two tables are now next to each other. Moreover the progress bar was just a purple square, the behaviour of v15.0 is now restore + adapted to dark mode This PR also correct multiple dark mode problem * White rectangle * Border * Hover Line * Hover Field The second commit is about duplicate function that needed to be removed. task-id: 3055687 Forward-Port-Of: odoo/enterprise#33699
Current behaviour: When we have a payment token linked to the SO, we skip the update of the `next_invoice_date` to update it on the reconciliation of the payment. The issue is that the reconciliation call back is only called when the invoice transaction is created by `do_payment` which only happen for automatic invoice. Behaviour after PR: If we are creating a new manual invoice, the next invoice date is updated even if we have a payment token task-id : [3007712](https://odoo.com/we
Original PR description
Current behaviour: When we have a payment token linked to the SO, we skip the update of the `next_invoice_date` to update it on the reconciliation of the payment. The issue is that the reconciliation call back is only called when the invoice transaction is created by `do_payment` which only happen for automatic invoice. Behaviour after PR: If we are creating a new manual invoice, the next invoice date is updated even if we have a payment token task-id : [3007712](https://odoo.com/web#id=3007712&model=project.task) Forward-Port-Of: odoo/enterprise#32301
In sign, we try to avoid as much as possible overwriting the signature of the user, as the device which was used to sign affects the resolution of the image saved in the user profile. Therefore, we only save the signature when the user interacted with any of the buttons in the signature widget. However, the signature was not being changed if the user didn't click on any of the buttons but drew while being on the draw mode. This commit fixes this. task-3002677 Forward-Port-Of: odoo/enterprise
Original PR description
In sign, we try to avoid as much as possible overwriting the signature of the user, as the device which was used to sign affects the resolution of the image saved in the user profile. Therefore, we only save the signature when the user interacted with any of the buttons in the signature widget. However, the signature was not being changed if the user didn't click on any of the buttons but drew while being on the draw mode. This commit fixes this. task-3002677 Forward-Port-Of: odoo/enterprise#33855 Forward-Port-Of: odoo/enterprise#32117
In case HR provides the simulation link to the employee via copy pasting the link from the wizzard, and employee does not have email set on home address, after filling in the configurator, it will raise an error that not all signers have valid email address. To avoid this behavior, we display warning in the wizzard. task -2971112 Forward-Port-Of: odoo/enterprise#32867
Original PR description
In case HR provides the simulation link to the employee via copy pasting the link from the wizzard, and employee does not have email set on home address, after filling in the configurator, it will raise an error that not all signers have valid email address. To avoid this behavior, we display warning in the wizzard. task -2971112 Forward-Port-Of: odoo/enterprise#32867
The content lines displayed in component `AutofillTooltip` could have the same value. This would generate a duplicate key in the template. Forward-Port-Of: odoo/enterprise#33976 Forward-Port-Of: odoo/enterprise#33955
Original PR description
The content lines displayed in component `AutofillTooltip` could have the same value. This would generate a duplicate key in the template. Forward-Port-Of: odoo/enterprise#33976 Forward-Port-Of: odoo/enterprise#33955
Prior to this commit, the action's context would not be propagated properly meaning that actions that lead to a document view (for example hr.job.action_open_attachments) would not create the spreadsheet linked to the model. Forward-Port-Of: odoo/enterprise#33945
Original PR description
Prior to this commit, the action's context would not be propagated properly meaning that actions that lead to a document view (for example hr.job.action_open_attachments) would not create the spreadsheet linked to the model. Forward-Port-Of: odoo/enterprise#33945
In the commit: https://github.com/odoo/enterprise/commit/72435a6912fc6c62f5a843e8843a1773f1ba5240 A new system for ellipsis in reports has been introduced. There is a slight issue where if you manually set a colspan on a line, it would be overriden here anyway. In the journal report, we rely on manually setting the colspan for grouping lines (such as the journal line). By ignoring the calculation if a colspan has already been manually specified, it will bring back the old behaviour and fix a
Original PR description
In the commit: https://github.com/odoo/enterprise/commit/72435a6912fc6c62f5a843e8843a1773f1ba5240 A new system for ellipsis in reports has been introduced. There is a slight issue where if you manually set a colspan on a line, it would be overriden here anyway. In the journal report, we rely on manually setting the colspan for grouping lines (such as the journal line). By ignoring the calculation if a colspan has already been manually specified, it will bring back the old behaviour and fix an issue with the line width in the journal report. Task id #3063211 Forward-Port-Of: odoo/enterprise#33917
After Reportalypse, some translation files were not updates to the new structure, causing the translations to not be loaded. This commit fixes the issue such that translations are correctly loaded on the reports. [task-3059090](https://www.odoo.com/web#id=3059090&cids=1&menu_id=4720&action=4043&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#33794
Original PR description
After Reportalypse, some translation files were not updates to the new structure, causing the translations to not be loaded. This commit fixes the issue such that translations are correctly loaded on the reports. [task-3059090](https://www.odoo.com/web#id=3059090&cids=1&menu_id=4720&action=4043&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#33794
exception is raised on printing worksheet reports when the type is "Take a Picture" and no picture is attached to the QC and when type is selected as Measure, currently in the model there is no field with name result. Quality -> Quality Control -> Quality Checks --> Create a QC with type take a picture, keep image field empty and print the report from print button. --> Create a QC with type as measure and print the report ![Screenshot from 2022-11-10 22-31-31](https://user-images.githubu
Original PR description
exception is raised on printing worksheet reports when the type is "Take a Picture" and no picture is attached to the QC and when type is selected as Measure, currently in the model there is no field with name result. Quality -> Quality Control -> Quality Checks --> Create a QC with type take a picture, keep image field empty and print the report from print button. --> Create a QC with type as measure and print the report   Forward-Port-Of: odoo/enterprise#33887
Use standard Tags for the taxes Forward-Port-Of: odoo/enterprise#33727
Original PR description
Use standard Tags for the taxes Forward-Port-Of: odoo/enterprise#33727
See https://github.com/odoo/odoo/pull/103791 Forward-Port-Of: odoo/enterprise#33275 Forward-Port-Of: odoo/enterprise#33093
Original PR description
See https://github.com/odoo/odoo/pull/103791 Forward-Port-Of: odoo/enterprise#33275 Forward-Port-Of: odoo/enterprise#33093
Following https://github.com/odoo/odoo/commit/bc40795c56eb463fea29be08306883d7d8ea31fc Forward-Port-Of: odoo/enterprise#19294
Original PR description
Following https://github.com/odoo/odoo/commit/bc40795c56eb463fea29be08306883d7d8ea31fc Forward-Port-Of: odoo/enterprise#19294
When unfolding a groupby line, the groupby keys corresponding to inactive records were not displayed. For example, inactive customers did not appear in the Aged Receivable report. This was due to the fact a call to .sorted() is done on the recordset containing the grouping keys, and this function calls .search() to fetch its results. A context key was hence missing in order to keep the archived records. Forward-Port-Of: odoo/enterprise#33959
Original PR description
When unfolding a groupby line, the groupby keys corresponding to inactive records were not displayed. For example, inactive customers did not appear in the Aged Receivable report. This was due to the fact a call to .sorted() is done on the recordset containing the grouping keys, and this function calls .search() to fetch its results. A context key was hence missing in order to keep the archived records. Forward-Port-Of: odoo/enterprise#33959
Currently in marketing automation, the logo is missing in the template ids "mass_mailing_offer_free_trial" and "mass_mailing_after_7_days" of the demo data. This is because there is a wrong file reference in the templates With a recent refactoring (see commit[1]), it renames the "s_default_image_logo" with "s_default_image_header_logo" but does not change the file reference in the template of the demo data in marketing automation. This commit resolves the above issue by including the corre
Original PR description
Currently in marketing automation, the logo is missing in the template ids "mass_mailing_offer_free_trial" and "mass_mailing_after_7_days" of the demo data. This is because there is a wrong file reference in the templates With a recent refactoring (see commit[1]), it renames the "s_default_image_logo" with "s_default_image_header_logo" but does not change the file reference in the template of the demo data in marketing automation. This commit resolves the above issue by including the correct file reference in the demo data template. commit[1] -https://github.com/odoo/odoo/commit/a559fe4 task-3054248 Forward-Port-Of: odoo/enterprise#33891