Thursday, May 9, 2024
10 changes · master
Enhancements to existing features
Portal users viewing shared project tasks can now see how long tasks spend in each stage, matching information already available to internal users. Project stage displays also use the duration-aware status bar when enabled, giving external collaborators clearer progress context.
Original PR description
-In the backend view, internal user can view the duration on each stage but in the form view of project sharing, portal user only see stage and can't see the duration between them. This commit apply the duration for portal user view -The 2nd commit change statusbar to statusbar_duration for stage of project in case we have enabled it --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Inventory records now use the date products actually arrive at the warehouse, rather than another movement-related date. This helps businesses keep more accurate stock aging, valuation, and traceability information.
Original PR description
Discussion in https://github.com/odoo/odoo/issues/54557 and https://github.com/odoo/odoo/pull/55111 (back from v12). --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
### [FIX] payment_razorpay: fix proccessing data in token flow Steps: - Install razorpay and sales app. - Enable Razorpay provider. - Create a create a token in razorpay. - Pay via that token. Issue: - When we are paying via token we really don't need processing values because those processing values only needed when we open Razorpay form so here it is calling APIs(customer and order) and creating order unwantedly. Fix: - Return empty dict when operation is `online_token` in `_
Original PR description
### [FIX] payment_razorpay: fix proccessing data in token flow Steps: - Install razorpay and sales app. - Enable Razorpay provider. - Create a create a token in razorpay. - Pay via that token. Issue: - When we are paying via token we really don't need processing values because those processing values only needed when we open Razorpay form so here it is calling APIs(customer and order) and creating order unwantedly. Fix: - Return empty dict when operation is `online_token` in `_get_specific_processing_values` method IMP/REV of PR: https://github.com/odoo/odoo/pull/157533 task-3653372 Forward-Port-Of: odoo/odoo#164595 Forward-Port-Of: odoo/odoo#159250
This traceback occurs when the user tries to edit the website searchbar To reproduce this issue:- 1) Install `website_sales` 2) open `website` and click on the `search icon` 3) A `website search box` will popup 4) Now open the `editor` and try to change the `inline text` 5) Save the record 6) A traceback appears Error:- ``` ValueError: not enough values to unpack (expected 1, got 0) ``` The issue is occurring because on `web search box` we are getting section_xpath - `/d
Original PR description
This traceback occurs when the user tries to edit the website searchbar To reproduce this issue:- 1) Install `website_sales` 2) open `website` and click on the `search icon` 3) A `website search box` will popup 4) Now open the `editor` and try to change the `inline text` 5) Save the record 6) A traceback appears Error:- ``` ValueError: not enough values to unpack (expected 1, got 0) ``` The issue is occurring because on `web search box` we are getting section_xpath - `/data/xpath[3]/form/t[1]/div[1]/button[1]/i[1]` and we are not getting any value in root from this `section_xpath` over here - https://github.com/odoo/odoo/blob/cdedc1752b845bed9acc0dd4bfeb4b343b675326/addons/web_editor/models/ir_ui_view.py#L121 To fix this issue `o_not_editable` class has been used on that website search bar sentry-3933794130 Forward-Port-Of: odoo/odoo#164129
Box 49 of the Swedish tax report should be the total of the amounts in boxes 10, 11, 12, 30, 31, 32, 60, 61 and 62 minus the amount in box 48. See [doc](https://skatteverket.se/servicelankar/otherlanguages/inenglishengelska/businessesandemployers/startingandrunningaswedishbusiness/declaringtaxesbusinesses/vat/vatitemsboxbybox.4.3dfca4f410f4fc63c8680004502.html#:~:text=Here%20you%20enter%20the%20VAT%20that%20you%20will%20pay%20or%20have%20refunded%20for%20the%20period%2C%20meaning%20the%20total%2
Original PR description
Box 49 of the Swedish tax report should be the total of the amounts in boxes 10, 11, 12, 30, 31, 32, 60, 61 and 62 minus the amount in box 48. See…
Box 49 of the Swedish tax report should be the total of the amounts in boxes 10, 11, 12, 30, 31, 32, 60, 61 and 62 minus the amount in box 48. See [doc](https://skatteverket.se/servicelankar/otherlanguages/inenglishengelska/businessesandemployers/startingandrunningaswedishbusiness/declaringtaxesbusinesses/vat/vatitemsboxbybox.4.3dfca4f410f4fc63c8680004502.html#:~:text=Here%20you%20enter%20the%20VAT%20that%20you%20will%20pay%20or%20have%20refunded%20for%20the%20period%2C%20meaning%20the%20total%20of%20the%20amounts%20in%20boxes%2010%2C%2011%2C%2012%2C%2030%2C%2031%2C%2032%2C%2060%2C%2061%20and%2062%C2%A0minus%20the%20amount%20in%20box%2048.%20%C2%A0). Currently, Box 49 is defined as `Block B + Block I + Block D + Block F`, with: ``` Block B = (box 10 + box 11 + box 12) Block I = (box 60 + box 61 + box 62) Block D = (box 30 + box 31 + box 32) Block F = (box 48) ``` Therefore, Box 49 should be `Block B + Block I + Block D - Block F`. Enterprise PR: https://github.com/odoo/enterprise/pull/61525 opw-3860025 Forward-Port-Of: odoo/odoo#164780 Forward-Port-Of: odoo/odoo#162006
At the end of the chat with odoobot, odoobot state is `idle` and the message which is sent to user in this state doesn't contain `start the tour` so at the end of the chat, user never knows that it's possible to start the tour again! This PR changes the wording in messages from odooBot in `idle` state to contain `start the tour` again possibility. This is a part of task-3570249 but since from 15.0 it's similar in all versions, the fix should be applied on all of them. Forward-Port-Of:
Original PR description
At the end of the chat with odoobot, odoobot state is `idle` and the message which is sent to user in this state doesn't contain `start the tour` so at the end of the chat, user never knows that it's possible to start the tour again! This PR changes the wording in messages from odooBot in `idle` state to contain `start the tour` again possibility. This is a part of task-3570249 but since from 15.0 it's similar in all versions, the fix should be applied on all of them. Forward-Port-Of: odoo/odoo#164784 Forward-Port-Of: odoo/odoo#163950
**Steps to reproduce:** - Install Accounting - Create a branch company (e.g. Branch Company) for a company (e.g. YourCompany) - Switch to Branch Company - Create a product with taxes from the parent and the branch companies - Create an invoice - Add a line with the created product **Issue:** Both taxes from the branch company and its parent are set on the invoice line. It should only take the tax from the branch. And if there is no tax, it should check the parent company for a tax an
Original PR description
**Steps to reproduce:** - Install Accounting - Create a branch company (e.g. Branch Company) for a company (e.g. YourCompany) - Switch to Branch Company - Create a product with taxes from the parent…
**Steps to reproduce:** - Install Accounting - Create a branch company (e.g. Branch Company) for a company (e.g. YourCompany) - Switch to Branch Company - Create a product with taxes from the parent and the branch companies - Create an invoice - Add a line with the created product **Issue:** Both taxes from the branch company and its parent are set on the invoice line. It should only take the tax from the branch. And if there is no tax, it should check the parent company for a tax and so on, as it is done in Sales. The same issue happens in: - "Purchase": the taxes on PO lines - "Point of Sale": the taxes on the products when loading a session - "eCommerce": (when "Tax Included" is configured for "Display Product Prices") * the displayed price on product page * the displayed price on the products list page * the displayed price on the Products snippet - "Delivery": the taxes on the delivery line of a SO - "Sale Loyalty": the taxes on the free product or free shipping opw-3850514 opw-3873659 opw-3775579 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#164926 Forward-Port-Of: odoo/odoo#163775
Before this commit, users were not allowed to activate the bridge to the documents app to work on Bank and Cash journals. This commit allows Bank and Cash journal documents to be centralized the same way other journals are. There does not seem to be particular reason about excluding Bank and Cash journals from the documents bridge. The potential of showing unwanted bank account numbers in a general repository can always be managed by other means such as access rights. The exclusion was add
Original PR description
Before this commit, users were not allowed to activate the bridge to the documents app to work on Bank and Cash journals. This commit allows Bank and Cash journal documents to be centralized the same way other journals are. There does not seem to be particular reason about excluding Bank and Cash journals from the documents bridge. The potential of showing unwanted bank account numbers in a general repository can always be managed by other means such as access rights. The exclusion was added in this PR https://github.com/odoo/enterprise/pull/10141 but it seems unnecessary and needs to be removed. task-3839839 Forward-Port-Of: odoo/enterprise#62088
Community PR: https://github.com/odoo/odoo/pull/162006 opw-3860025 Forward-Port-Of: odoo/enterprise#62124 Forward-Port-Of: odoo/enterprise#61525
Original PR description
Community PR: https://github.com/odoo/odoo/pull/162006 opw-3860025 Forward-Port-Of: odoo/enterprise#62124 Forward-Port-Of: odoo/enterprise#61525
Avatax support confirmed to us that they now require a modeDescription for "Other" payment methods. There are other required attributes we can't easily add, so instead we change the cardTpIntegration type to one that doesn't need these new attributes. opw-3915009 Forward-Port-Of: odoo/enterprise#62161
Original PR description
Avatax support confirmed to us that they now require a modeDescription for "Other" payment methods. There are other required attributes we can't easily add, so instead we change the cardTpIntegration type to one that doesn't need these new attributes. opw-3915009 Forward-Port-Of: odoo/enterprise#62161