Tuesday, February 1, 2022
9 changes · master
Resolved issues and error corrections
This change updates an internal accounting test so it correctly handles a newly added calculated field. It helps keep development checks reliable and prevents unrelated test failures from slowing future accounting updates.
Original PR description
In master, the tax template consistency test is broken since 8fb53c53c3128e8cea7ef20b9ab4946ac2f9b7d9 Fix this to make sure we add an exception for that new computed field as it should not be in the template. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures archived records still load their related chatter information, such as followers, activities, and suggested recipients. Business users can now view and use communication details on archived documents without missing data or errors.
Original PR description
With a recent commit[1], we now gather the chatter related data with a single controller ('/mail/thread/data') which was a bit scattered previously. With this controller, instead of searching in…
With a recent commit[1], we now gather the chatter related data with a
single controller ('/mail/thread/data') which was a bit scattered
previously. With this controller, instead of searching in dedicated
model, we now simply use the main document/record itself and it's
fields whenever possible. For example, previously for the followers,
we used to search data from 'mail.followers' model, but now we simply
use `message_follower_ids` field of the record itself.
The problem with this approach is, if the record is archived, we won't
be able to fetch the related data. That leads to empty follower list/
activities and a trackback while getting suggested recipients.
This PR fixes the issue by loading the record even if it's
archived, and thus fetching the data required by chatter.
commit[1] - https://github.com/odoo/odoo/commit/e0913197ac84b25b40e7599a6432362141d104c9
TaskID-2748030
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThe payment registration process now automatically uses the partner's bank account and prevents users from changing or creating a different recipient account for inbound and cash-related payments. This helps reduce payment mistakes and hides the bank account field when it is not relevant for cash journals.
Original PR description
Currently: the "register payment" wizard allows selecting different bank accounts or even creating one when registering a payment on customer invoice/vendor refund. Should be: the field should be set to partner_bank_id and be set as readonly. Task ID: 2710936 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change temporarily turns off unreliable automated tests in the sales stock area until they can be fixed properly. It helps keep development checks stable and avoids false failures that could slow down future work, with no expected impact on users.
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change prevents activities and mailing traces from being saved without a valid linked business record. It improves data reliability and avoids follow-up items or mailing history entries pointing to missing records, including in sales workflows.
Original PR description
Activities and mailing trace models are linked to records through a model and a many2one reference field. The latter one is required but is implemented like an integer field, meaning writing 0 is actually a valid value for 'required'. In this commit we add a constraint to ensure we never update activities with a void res_id value. Same for mailing traces. Source: internal feedback about activities with 0 as res_id Task-2694133
This fix reverts an unintended change to labels on the payment form in Accounting. It restores the expected wording so users see clearer, familiar field names while working with payments.
Original PR description
The part of 9311b087e1cdcfd2e1c4ab4a559a55d517b542fa affecting field labels on account.payment's form view was mistakenly merged. The actual fix regarding those labels is done in 15.0 here https://github.com/odoo/odoo/pull/83674 .
Improved how Odoo finds failed outgoing mail, SMS, and letters for the current user. This prevents long waits in failure-related views or actions, reducing response time from potentially over 20 seconds to near-instant in affected cases.
Original PR description
We are currently lacking an index with (author, failure) due to the information being spread out in two different tables which are both rather big (there are a lot of non-failure messages for the current user, as well as a lot of failure messages for other users), so the fetch of failures for the current user can become extremely slow (> 20s). With this new index, the query takes less than 1ms. task-2742946
Saving a record now avoids sending unchanged selection data to the server. This prevents unrelated sales order lines from being recalculated, reducing unexpected price changes and improving save behavior.
Original PR description
Following recent conversion of onchanges to computes in the sale scope, it was observed that updating one line triggered price recomputation in other lines (which isn't expected). After investigation, it seems that the `product_packaging_id` field is considered modified and sent on SO save for all the lines, which triggers the `product_uom_qty` record computation, then the whole price computation is triggered, since it depends on that quantity field. This commit aims to fix this case by only considering a m2o field as modified if its value was effectively changed. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes visual inconsistencies when adding text fields during signing and restores pinch-to-zoom behavior on mobile. It improves the signing experience by making text fields look consistent and preventing mobile errors while users zoom documents.
Original PR description
This task fixes some UI issues found in sign while testing v15.1 and v15.2 - [FIX] sign: fix edit while signing text type handlers and font-size When a text sign item is added while signing, its font-size and handlers have different size than an item created in the template editor. This commit fixes the css of the sign item and also fixes the default width and height of text sign items. - [FIX] sign: fix pinching in mobile In mobile version of sign, pinching the screen while signing should zoom-in/ zoom-out. However, after refactoring the js code in task-2664886, pinching started causing an error. This commit fixes this issue, preventing the error caused from the loss of context when calling `PinchItemMixin.init`.