Friday, October 25, 2024
15 changes · 17.0
Resolved issues and error corrections
The stock traceability report now opens in the correct language instead of defaulting to English. This ensures translated report content is shown consistently for users working in other languages.
Original PR description
When the language is not in the context the report will always show the en_US version. opw-4220270 Description of the issue/feature this PR addresses: Current behavior before PR: - translation is bypassed Desired behavior after PR is merged: - report will be shown in the correct language --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Uganda localization now classifies the Tax Receivable account as a current asset instead of a receivable account. This prevents it from appearing in aged receivable reports, keeping those reports focused on actual customer receivables.
Original PR description
"Tax Receivable" account shouldn't be set as a receivable account, but as a current assets one, else it will appear in aged reports, which does not make sense. Similar to the fix already made here for "Tax Payable": https://github.com/odoo/odoo/commit/2318e671c3a5535590fe6d95949835417856dce6
This fixes an issue in Indian e-waybill stock handling where a cancelled e-waybill kept its old name after being reset to pending. Resetting the name avoids confusion and helps users regenerate or manage e-waybills with the correct pending state.
Original PR description
Once the ewaybill is generated, cancelled and resetted to pending the name is not resetted After this commit: we reset ewaybill name once it's been reset to pending task-4285220 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The messaging menu no longer shows an enable push notifications item on iOS devices. This avoids presenting users with a persistent option that iOS web apps cannot act on, reducing confusion in the Mail experience.
Original PR description
Before this commit, it was showing a "enable push notification" messaging menu item on iOS devices. This item was persistent and could not be removed, because iOS does not allow to enable specifically push notifcation on web apps, except if there are installed as PWA in which case they necessarily authorized push notifications based on OS app preferences. opw-4236170 Backport of https://github.com/odoo/odoo/pull/178057
This fixes an issue where phone numbers in reports could split across two lines, leaving the final digits separated. Reports now keep each phone number together, making printed and PDF documents clearer and easier to read.
Original PR description
Before this PR it would happend that the last two digits of a phone number would go on the line below. After the PR, the phone number is always written in one line opw-3954932
A missing closing brace was added in a base module test file. This prevents syntax errors in automated checks and helps keep the system's validation tests reliable.
Original PR description
I found in the base test_views.py on line 4161 a forgotten closing curly brace for attrs attribute value for a field. Each opening tag/brace must have only one closing tag/brace. In our case it was a curly brace which must be added to avoid syntax errors. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo now skips modules that are marked for automatic installation but are also marked as not installable. This prevents unnecessary installation attempts and reduces confusing warning messages in the logs.
Original PR description
Description of the issue/feature this PR addresses: Do not try install auto installable modules that are not installable Current behavior before PR: If you have an auto_installable module (auto_install = True) that is not installable (installable = False) odoo is trying to install it and displaying warnings on the log Desired behavior after PR is merged: Avoid trying to install modules that are auto_install = True and installable = False --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves a visual bug where the 'Start' button on the sign document flow was obscured. The issue stemmed from a stacking order problem with the sign navigator item. By increasing the z-index, the 'Start' button is now correctly displayed and functional, ensuring a smooth user experience.
Original PR description
Versions: ------------ 17.0 Steps to Reproduce: ----------------------------- 1. go to sign document 2. add sign item in document 3. click on sign document now 4. click on start seems be not working properly 5. video link: https://nimb.ws/WKMlFjB Issue: ------- stacking order of sign item navigator seems to be low Solution: ------------ increase z-index value of `o_sign_sign_item_navigator`. task-4191542
This update fixes an issue where quality checks weren't visible for finished lots linked to manufacturing orders. The change ensures that the quality check button is always displayed when a finished lot's serial number is accessed, streamlining the process of verifying product quality.
Original PR description
Steps to reproduce the bug:
- Create a storable product “P1”:
- Tracked with SN
- Create a BoM:
- no need to component
- Add an operation “OP1” with steps
- Control by product
- Create a manufacturing order for one unit of P1
- Confirm the MO
- Go to the shop floor and process “OP1”
- Validate the MO
- Go to the SN of P1
Problem:
The quality check smart button is not displayed, while the SN is linked to a QC.
opw-4189396This update fixes a reporting issue where the Aged Payable report incorrectly displayed partners with zero balances when storno accounting was enabled. The fix addresses a technical detail in how the system checks for open balances within storno transactions, ensuring accurate reporting of outstanding amounts.
Original PR description
To reproduce: 1) Activate storno accounting in the settings 2) Create a new partner 3) Create a Vendor Credit Note for that partner, post it 4) Register a full payment for the credit note 5) Open the Aged Payable report ====> The partner appears in the report, even though it has an amount of 0. It shouldn't, since there is no open amount for it. This was due to the way we checked the amount of the credit note was zero. In storno, the payable line of the refund is a negative credit instead of being a debit. Still, it's linked through the debit_move_id field to the partial reconcile. So, removing the debit from the debit or credit from the credit wasn't enough in that setup. opw-4166891 Forward-Port-Of: odoo/enterprise#72422
This update resolves an issue where bank reconciliation in multiple currencies (like USD and MXN) could lead to small, unmatched amounts, particularly impacting EDI validation for localized accounting systems. The change allows users to adjust exchange amounts within the bank reconciliation process, ensuring accurate matching and compliance. This improves the reliability of financial reporting.
Original PR description
Let's say you have: - One statement line of 3000 USD / 1000 MXN (rate 1:3) - Three invoices of 1000 USD / 500MXN (rate 1:2) => If you reconcile in the bank widget, the statement entry amounts will be divided by 3 ending with 3 lines of 1000 USD and 333.33 MXN leaving a 0.01 unmatched. This can be an issue for the validation of payment EDI for localizations like Mexican one. This PR gives more flexibility to user when dealing when bank reconciliation in multiple currencies by allowing to edit amounts on generated exchange moves to allocate this small difference. opw-4128899
Miscellaneous changes
When typing '>:)' in the composer, it should be replaced by '😈'. The problem is that the emoji generator doesn't work with '<', '>' because the text is escaped and the '<', '>'is replaced by '<', '>'. In this case, the regrex doesn't match. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#185091
Original PR description
When typing '>:)' in the composer, it should be replaced by '😈'. The problem is that the emoji generator doesn't work with '<', '>' because the text is escaped and the '<', '>'is replaced by '<', '>'. In this case, the regrex doesn't match. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#185091
Steps ----- - install sale_timesheet - create a "30 hours" Unit of Measure in the Working Time category, equal to 3.75 days - create a service product with "30 hours" as the UoM - create a SO with this product for a customer - create a task for this customer and use the previously created SOL - add 15 hours of timesheet Issue ----- The remaining hours on the SO appear as +/- 26:00 (with some minor decimal precision inaccuracies), but the name of the SOL in the "Sales Order Item" f
Original PR description
Steps ----- - install sale_timesheet - create a "30 hours" Unit of Measure in the Working Time category, equal to 3.75 days - create a service product with "30 hours" as the UoM - create a SO with this product for a customer - create a task for this customer and use the previously created SOL - add 15 hours of timesheet Issue ----- The remaining hours on the SO appear as +/- 26:00 (with some minor decimal precision inaccuracies), but the name of the SOL in the "Sales Order Item" field shows 26:30 remaining. Change ----- Backport https://github.com/odoo/odoo/commit/d0cf7c0f2c039d55d024cf9a2e0676e11ba97338 which removes the rounding by 30 minutes and uses `format_duration` opw-3959886 Forward-Port-Of: odoo/odoo#181008
Issue --> A noticeable amount of time is spent in the method `_get_outgoing_incoming_moves` when doing the `OR` operation on the stock.move recordsets when there is a large number of moves to iterate through. Solution --> Replace the odoo recordset operations with set operations. Benchmarks --> | # of moves | Before | After | |--------|--------|--------| | 32000 | 24.08s | 1.43s | | 7300 | 1.74s | 0.40s | opw-4220302 Forward-Port-Of: odoo/odoo#183671
Original PR description
Issue --> A noticeable amount of time is spent in the method `_get_outgoing_incoming_moves` when doing the `OR` operation on the stock.move recordsets when there is a large number of moves to iterate through. Solution --> Replace the odoo recordset operations with set operations. Benchmarks --> | # of moves | Before | After | |--------|--------|--------| | 32000 | 24.08s | 1.43s | | 7300 | 1.74s | 0.40s | opw-4220302 Forward-Port-Of: odoo/odoo#183671
Description of the issue/feature this PR addresses: - After an internal user (without Live Chat application access) interacted with chatbot from website, he will not be able to click on the Messages icon on the top-right menu anymore:  - Cause: Internal user without Live Chat application access cannot read on model `chatbot.script.step`, so when system calls `mail_channel.chatbot_current_step_id`, securit
Original PR description
Description of the issue/feature this PR addresses: - After an internal user (without Live Chat application access) interacted with chatbot from website, he will not be able to click on the Messages icon on the top-right menu anymore:  - Cause: Internal user without Live Chat application access cannot read on model `chatbot.script.step`, so when system calls `mail_channel.chatbot_current_step_id`, security error occurs. - Solution: Use `sudo` on `mail_channel` variable to avoid security error. 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#174611