Monday, December 12, 2022
15 changes · master
Enhancements to existing features
This update keeps the appraisal survey department settings aligned after a related company field was moved elsewhere. It helps ensure the appraisal configuration screen continues to work as expected without changing business workflows.
Original PR description
The field company_id is moved in #106005. This PR adapts the XPath to it. task-3071039
The subscription process now leaves the original order reference empty for the first recurring contract instead of linking it to itself. This makes monthly reporting on newly created contracts simpler and more accurate for business analysis.
Original PR description
…t contract Before this commit, origin_order_id was set to the first order id, pointing to himself for the first recurring sale.order. It prevented to easily calculate the number of new contracts per month with a simple domain. taskid: 3048181
Features or functions removed from Odoo
An unused data model in the expense receipt extraction feature has been removed. This simplifies maintenance without changing how users submit or process expenses.
Original PR description
This model isn't used at all and can thus safely be removed. Upgrade PR: https://github.com/odoo/upgrade/pull/3984
Miscellaneous changes
Account 4686 was used twice in the balance sheet. The reason is we take the 468 account in AUTRES_DETTES_CREDIT and the 4686 account in AUTRES_DETTES. In this commit, we exclude the 4686 account from AUTRES_DETTES_CREDIT. opw-3052943 Forward-Port-Of: odoo/enterprise#34890 Forward-Port-Of: odoo/enterprise#33702
Original PR description
Account 4686 was used twice in the balance sheet. The reason is we take the 468 account in AUTRES_DETTES_CREDIT and the 4686 account in AUTRES_DETTES. In this commit, we exclude the 4686 account from AUTRES_DETTES_CREDIT. opw-3052943 Forward-Port-Of: odoo/enterprise#34890 Forward-Port-Of: odoo/enterprise#33702
This commit re-introduces some UI elements that were missing from the latest versions of the apps. These UI elements include a self assign button in the gantt's form view as well as showing the role of open shift slots in the Kanban view. Task-3037867 Forward-Port-Of: odoo/enterprise#33137
Original PR description
This commit re-introduces some UI elements that were missing from the latest versions of the apps. These UI elements include a self assign button in the gantt's form view as well as showing the role of open shift slots in the Kanban view. Task-3037867 Forward-Port-Of: odoo/enterprise#33137
The generic tax report already adds a Closing Entry button and the German Tax report inherits from the generic tax report in 16.0 (will be different in master). Currently two buttons appear for Closing Entry when opening DE tax report. This commit removes the additional button. Forward-Port-Of: odoo/enterprise#34865
Original PR description
The generic tax report already adds a Closing Entry button and the German Tax report inherits from the generic tax report in 16.0 (will be different in master). Currently two buttons appear for Closing Entry when opening DE tax report. This commit removes the additional button. Forward-Port-Of: odoo/enterprise#34865
Steps to reproduce ================== - On safari, go to an odoo instance with https (you can use browserstack + ngrok) - Install appointment - Go to calendar - Click on share availabilities -> NotAllowedError Solution ======== Use a timeout as this is allowed in safari opw-3031660 Forward-Port-Of: odoo/enterprise#34877 Forward-Port-Of: odoo/enterprise#34440
Original PR description
Steps to reproduce ================== - On safari, go to an odoo instance with https (you can use browserstack + ngrok) - Install appointment - Go to calendar - Click on share availabilities -> NotAllowedError Solution ======== Use a timeout as this is allowed in safari opw-3031660 Forward-Port-Of: odoo/enterprise#34877 Forward-Port-Of: odoo/enterprise#34440
There is no reason for analytic breakdown to only be present on a single line of the depreciation entries. t-3076423 Forward-Port-Of: odoo/enterprise#34872 Forward-Port-Of: odoo/enterprise#34346
Original PR description
There is no reason for analytic breakdown to only be present on a single line of the depreciation entries. t-3076423 Forward-Port-Of: odoo/enterprise#34872 Forward-Port-Of: odoo/enterprise#34346
When an article does not have any title and the user clicks on the title, the script will retrieve the first heading of the editor and use it as default title. When the user uses a mobile device, wysiwyg will add a toolbar in the editor and the selector used to fetch the first heading of the editor will match with a title of that toolbar. To avoid that, we will update the selector to only select a heading from the editable zone. Step to reproduce the issue: 1. Open Odoo on a mobile phone (ma
Original PR description
When an article does not have any title and the user clicks on the title, the script will retrieve the first heading of the editor and use it as default title. When the user uses a mobile device, wysiwyg will add a toolbar in the editor and the selector used to fetch the first heading of the editor will match with a title of that toolbar. To avoid that, we will update the selector to only select a heading from the editable zone. Step to reproduce the issue: 1. Open Odoo on a mobile phone (make sure that the toolbar of the editor to edit the text is always visible). 2. Create a new article. 3. Click on the article title of the header. => The article title will have "Header 1" as title. task-3092930 Forward-Port-Of: odoo/enterprise#34811
Now that the SO portal page is refreshed whenever an optional product is added/removed or its quantity updated, the code to force the tax recomputation whenever the option is updated can be dropped. Indeed, taxes are already recomputed every time the page is loaded, in the override of the /my/orders/ID route. Also clean a bit the code while working on it. Community PR: https://github.com/odoo/odoo/pull/107283 Forward-Port-Of: odoo/enterprise#34832
Original PR description
Now that the SO portal page is refreshed whenever an optional product is added/removed or its quantity updated, the code to force the tax recomputation whenever the option is updated can be dropped. Indeed, taxes are already recomputed every time the page is loaded, in the override of the /my/orders/ID route. Also clean a bit the code while working on it. Community PR: https://github.com/odoo/odoo/pull/107283 Forward-Port-Of: odoo/enterprise#34832
Some of the dashboard files were using currency formats, which are hardcoded with a given currency. Because of that, some amounts are displayed with a $ sign, even if the amount is in €, according to the record's currency. It should use the automatic currency formatting of LIST functions to use the record's currency. This commits removes the hardcoded currency formats. Note that the automatic format displays the decimal values while the hardcoded format did not. This is a functional ch
Original PR description
Some of the dashboard files were using currency formats, which are hardcoded with a given currency. Because of that, some amounts are displayed with a $ sign, even if the amount is in €, according to the record's currency. It should use the automatic currency formatting of LIST functions to use the record's currency. This commits removes the hardcoded currency formats. Note that the automatic format displays the decimal values while the hardcoded format did not. This is a functional change. opw 3071160 opw 3058192 Forward-Port-Of: odoo/enterprise#34823
Task 3002282 Forward-Port-Of: odoo/enterprise#33101
Original PR description
Task 3002282 Forward-Port-Of: odoo/enterprise#33101
Fix the delete icon in the calendar slot when creating a custom appointment type. The icon was broken because of the new bootstrap which seems to not go well with fontawesome icon. task-3091111 Forward-Port-Of: odoo/enterprise#34664
Original PR description
Fix the delete icon in the calendar slot when creating a custom appointment type. The icon was broken because of the new bootstrap which seems to not go well with fontawesome icon. task-3091111 Forward-Port-Of: odoo/enterprise#34664
Steps to reproduce: - We go to documents app > Configuration > Settings > Accounting, and activate this option with workspace as Finance. - Then we go to journal (just under the previous option) and we create a journal for Customer invoices within Finance workspace. - We go back to Documents > Finance > Mark Inbox in tags and upload a new file. - We select a contact for this file and we select Create Customer Invoice. Issue: After all the steps we're gonna see that the contact
Original PR description
Steps to reproduce: - We go to documents app > Configuration > Settings > Accounting, and activate this option with workspace as Finance. - Then we go to journal (just under the previous option) and we create a journal for Customer invoices within Finance workspace. - We go back to Documents > Finance > Mark Inbox in tags and upload a new file. - We select a contact for this file and we select Create Customer Invoice. Issue: After all the steps we're gonna see that the contact that we set is not set as the customer of the invoice created, it get lost. Solution: The easies solution I found so far is to change the order we get the partner_id in the create_record method. This is because after _create_document_from_attachment the document.partner_id is overridden and we lost the one that we had initially. This bug affects all versions. opw-2991015 Forward-Port-Of: odoo/enterprise#33187
When a view is grouped by a date or datetime fields, the Group datapoints expect to receive a `range` param (e.g. indicating that the group corresponds to the period from 12/1/2022 to 12/31/2022). In the KanbanEditor, when there's no data, we manually create datapoints to simulate that there's a record (and we keep the fact that the view is grouped). So, we manually create a Group datapoint. Before this commit, we didn't pass the `range` param to that Group datapoint, and it thus crashed. Thi
Original PR description
When a view is grouped by a date or datetime fields, the Group datapoints expect to receive a `range` param (e.g. indicating that the group corresponds to the period from 12/1/2022 to 12/31/2022). In the KanbanEditor, when there's no data, we manually create datapoints to simulate that there's a record (and we keep the fact that the view is grouped). So, we manually create a Group datapoint. Before this commit, we didn't pass the `range` param to that Group datapoint, and it thus crashed. This commit passes an empty `range` which does the trick. Forward-Port-Of: odoo/enterprise#34856