Monday, January 16, 2023
7 changes · master
Resolved issues and error corrections
Fixed an issue where record counts in Kanban columns could show the wrong number if users quickly toggled progress bar filters. The count animation is now stopped when the underlying count changes, keeping displayed totals aligned with the active filter.
Original PR description
Before this commit, in the kanban view, if we click the progress bar to filter the column multiple times, the count of records number's could show an incorrect value. This occurs because when removing the filter from the progress bar, an animation is done to the number (to increase the value until the correct number of records). Contrariwise, when activating a filter, the number of records is set directly without animation. When we remove and add again a filter quickly, the animation to increase the value of the number finishes when the filter is already apply and the value shown is the old count of records (without the filter). To avoid this, in this commit, we stop the animation when the count of record changes. Unfortunately, testing this is very complicated (because it involves animation frames and Date.now()), and as the cost/reward ratio is very low, we didn't add a test of this behaviour. X-original-commit: 4c8bb53df6ad6382c5b168532c8493ddbb1f7252
This fix ensures payment-related tests use a known, supported currency instead of depending on whichever currency is set as the main one. It helps keep localization and payment checks reliable after recent currency-related changes.
Original PR description
Following f3a3e341503926703b2140f6df72f767422f5605, the l10n tests were failing due to the main currency changing to a currency not available for the test provider.
Swiss companies can now correctly invoice SEPA customers with the appropriate QR code when SEPA QR codes are enabled. The change also prevents incompatible QR code settings from being used for Swiss customers, reducing invoice creation errors and confusion.
Original PR description
Aim : Allow customer from Switzerland to emit an invoice with a QR code to a SEPA customer. Context: In Switzerland, adding an extra page containing a QR Bill is mandatory in many cases, mainly when the customer is also from Switzerland (although there are other conditions). However, activating the option 'QR Codes' in the settings (which is not linked to the QR Bill) can cause problem. For instance, it will be impossible to bill a foreign customer, because we check that the conditions are right to emit a swiss QR (which is a bug). After this commit : The new behaviour is : - Swiss user --> swiss customer: don't change the invoice, allow to create a QR Bill - SEPA option activated, swiss user --> SEPA customer : join the SEPA QR to the invoice - SEPA option activated, swiss user --> swiss customer : raise error task-3062570 Manual fw-port of https://github.com/odoo/odoo/pull/109808 X-original-commit: a9980477048e4adffda4a71a72ff1cc8490637f9
Kazakhstan is now included in the Eurasian Economic Union country group. This corrects country grouping data so business rules and reporting that rely on EEU membership can apply consistently.
Original PR description
EEU is missing KZ among the member countries, this commit fixes this omission. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update prevents a planning test from failing when it runs on Saturdays by creating the test shift at the current time instead of the next day. It improves the reliability of automated checks without changing how users interact with Planning.
Original PR description
Before this commit, the test, in which the `planning_shift_switching_backend` tour is launched, a slot is generated the next day from the commit [1]. By doing that, if the tour is started on Saturday, the tour will fail because slot will no longer be in the current week but in the following week in the gantt since, the last day in a week in the gantt view is Saturday. This commit creates the slot in the current datetime for a period set to one hour to be sure the slot is not considered to the past during the execution of the tour. [1] b9e4be033f0a43c9c94d9efc898787bbadd57d12
The wording in accounting lock date tooltips has been clarified so users better understand when entries can and cannot be created. This reduces confusion during period closing and helps accounting teams apply lock dates correctly.
Original PR description
The wording in the lock date tooltips is confusing and sounds as if it should be possible to create entries on the lock date. This commit makes the message clearer. task-3125611
This fix prevents field service sales projects from failing due to overly long internal constraint names. It improves reliability when creating or updating projects with long names, reducing unexpected errors for users.
Original PR description
linked to odoo/odoo#109065