Thursday, January 12, 2023
40 changes · master
Enhancements to existing features
This update improves the appearance of settings screens by adding clearer spacing between company-related icons and their labels. The change makes accounting and other company-dependent settings easier to read without altering functionality.
Original PR description
improves the display of the icon "fa fa-lg fa-building-o" by adding a space between the text and the icon. This improvement occurs in accounting settings but also anywhere in Odoo where the setting is using the company_dependent attribute. task: 3117722 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This fixes a timing issue that could make Kanban progress bars show incorrect or empty information after creating a new item in a grouped column. The change improves reliability in automated builds and helps ensure users see accurate progress information immediately after quick creation.
Original PR description
Before this commit, test "click on the progressBar of a new column" deterministically failed on split builds. It only passed with all addons installed, and passed by chance with all addons installed.…
Before this commit, test "click on the progressBar of a new column" deterministically failed on split builds. It only passed with all addons installed, and passed by chance with all addons installed. The reason is that the flow of quick creating a record in a grouped kanban with progressbars wasn't concurrency proof at all. Commit [1] simply added a hook at the end of the `_save` function of the model, which highlighted the problem: the progressbars were updated before the group's count was incremented, so if the quick created record was the only record of the group, the progressbar was still empty after the quick creation. This commit makes the quick create code more robust. We couldn't find a way to write a qunit test for this, but it still fixes an error in nightly builds. [1] a882b725bb6bf3d11c898a69e3fa5502802c1b78 Description of the issue/feature this PR addresses: 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
Miscellaneous changes
Before this commit, the bus service would fail to initialize its worker when loaded from a different origin than the worker script URL. Moreover, the websocket URL was assumed to be on the same domain that the bus service. This PR fixes both issues: - When the bus service is loaded from a different origin than the worker script URL, create a data URL and use "importScripts" inside the worker since it is not restricted to same origin scripts. - Pass the serverURL to the worker during its ini
Original PR description
Before this commit, the bus service would fail to initialize its worker when loaded from a different origin than the worker script URL. Moreover, the websocket URL was assumed to be on the same domain that the bus service. This PR fixes both issues: - When the bus service is loaded from a different origin than the worker script URL, create a data URL and use "importScripts" inside the worker since it is not restricted to same origin scripts. - Pass the serverURL to the worker during its initialization. opw-3118394 Forward-Port-Of: odoo/odoo#109651
Survey users will no longer see a technical traceback when a handled save or validation error occurs. Dialog buttons are restored correctly when validation blocks saving, making survey interactions smoother and less confusing.
Original PR description
Due to changes in errorService added in dd6f103b, a traceback was shown due to our (handled) "unhandled" rejected promise that wasn't an "Error" object. Using the original error works now for our handleSurveyError function. The only additional requirement was to restore the buttons of the dialog when saving is blocked due to our validation process. Task-3128957
Payment-related tests were adjusted to reflect updated rules for matching payment providers with supported currencies. This helps keep automated checks reliable after the currency compatibility logic changed, reducing the risk of false test failures.
Original PR description
Following 90af85c2e4fdec0a6ac7d70663f90443fad120d2, the management of the compatible providers was modified by their available currency. Some tests weren't adapted to that change.
Updated internal tests so they no longer assume every company uses USD. This prevents localization test failures when a country-specific setup uses the local company currency instead.
Original PR description
Since https://github.com/odoo/odoo/commit/3752b3166ec6bbb5c6ea55f96bb521381bf2b2d9, the currency of the test architecture is not fixed anymore to USD (but is by default). Therefore, the nightly runbot tests of the localization (l10n_* modules) all fail when verifying the company currency is USD (because the localization sets the company currency to the country one). This commit adapts those checks to stop enforcing the USD currency as base, only enforcing that the currency used is the company one. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Enterprise web interface will now be installed automatically when the standard web app is present, even if an optional setup component is not installed. This prevents customers from missing Enterprise web features after recent dependency changes.
Original PR description
Since the merge of PWA in enterprise the dependency of `web_enterprise` has changed (`base_setup` was added) and so the `auto_install` rules isn't satisfied anymore. This commit forces to auto install `web_enterprise` when web is installed also when `base_setup` is not. PS: another fix will be to set `auto_install: True` in `base_setup`. Ref [1] odoo/enterprise#35322
**[IMP] stock: add tests for putaway rules** Test the use cases of these commits: - https://github.com/odoo/odoo/commit/ce8f2643a36a7928f16b822d9b739f1bdf0f349d - https://github.com/odoo/odoo/commit/bcf225fbdb0ae0fb6473239c385dc6cdd31b08d2 **[FIX] stock: apply putaway on package with one product category** When applying the putaway rules, if we redirect a package (with a specific type), we don't check the category of the package products. To reproduce the issue: 1. In Settings, e
Original PR description
**[IMP] stock: add tests for putaway rules** Test the use cases of these commits: - https://github.com/odoo/odoo/commit/ce8f2643a36a7928f16b822d9b739f1bdf0f349d -…
**[IMP] stock: add tests for putaway rules**
Test the use cases of these commits:
- https://github.com/odoo/odoo/commit/ce8f2643a36a7928f16b822d9b739f1bdf0f349d
- https://github.com/odoo/odoo/commit/bcf225fbdb0ae0fb6473239c385dc6cdd31b08d2
**[FIX] stock: apply putaway on package with one product category**
When applying the putaway rules, if we redirect a package (with a
specific type), we don't check the category of the package products.
To reproduce the issue:
1. In Settings, enable
- Packages
- Multi-Step Routes
- Storage Categories
2. Edit the warehouse:
- Receipt: 2 steps
3. Create three categories C1, C2, C3
- Parent: All
4. Create three locations L1, L2, L3
- Parent: WH/Stock
5. For each location Lx, create a putaway rules PRx:
- From: WH/Stock
- Category: Cx
- To: Lx
6. Create a product P
- Type: Storable
- Category: C2
7. Create a planned receipt R with 1 x P
8. Mark it as todo, set the done quantity and put it in pack
9. Set a type on the package
10. Mark R as done
11. Open the associated internal transfer
Error: the destination location of the package is not L2 -> an
incorrect putaway rule has been applied
When we try to apply the PR on the SML "input to stock", two issues
happen:
- We get all PR that do not have any product defined, but we don't
filter out the PR based on the categories.
https://github.com/odoo/odoo/blob/bcf225fbdb0ae0fb6473239c385dc6cdd31b08d2/addons/stock/models/stock_location.py#L248-L249
As a result, we get PR1, PR2 and PR3. This is incorrect as PR1 and
PR3 are not relevant
- In case of a package with a type, when calling
`_get_putaway_strategy`, we don't specify any product:
https://github.com/odoo/odoo/blob/9dcbc420f50ece3356dff57cbdc467c7893ff2c2/addons/stock/models/stock_move_line.py#L216-L218
As a result, we consider that we don't have to check the
categories on the PR. This is incorrect: the category could be the
same for all products of the package
This commit fixes the above issues and simplifies/clarifies the
filtering and sorting of all putaway rules
OPW-3098452
**[FIX] stock,mrp: redirect byproducts with capacity constraints**
When redirecting the SML of byproducts, the capacity constraints of
the locations are not considered.
To reproduce the issue:
1. In Settings, enable:
- By-Products
- Storage Locations
- Storage Categories
2. Create three storable products P01, P02, P_comp
3. Create a storage category SG:
- Max Weight: 1000
- Capacity by Products:
- 2 x P02
4. Create two locations L01, L02:
- Parent Location: WH/Stock
- Storage Category: SG
5. Create a putaway rule:
- From: WH/Stock
- Product: P02
- To: WH/Stock
- Having Category: SG
6. Create a BoM:
- Product: P01
- Components: 1 x P_compo
- By-products: 1 x P02
7. Update on hand qty of P02:
- 1 x P02 at L01
8. Create and confirm a MO with 2 x P01
9. Set the producing qty to 2
10. Open the detailed operations of P02
Error: The destination location is L01, this would break the
capacity constraint. The location should be L02
When setting the producing qty, we also set the done quantities of
the finished moves and we redirect them thanks to the putaway rules:
https://github.com/odoo/odoo/blob/cc6e31efe6fdd9dee16de1565afe9e1b502de45d/addons/stock/models/stock_move.py#L1885-L1888
However, the SML created only has the `qty_done` defined and, when
applying the putaway rules, we consider the `product_uom_qty` which
is equal to 0 in such a case.
So, when trying to redirect the SML of P02, we check if the capacity
constraint of L01 would be exceeded with the quantity of the SML.
But, as explained above, that quantity will be 0, so we conclude
that the capacity constraint is ok and we return L01 as best solution.
This is the reason why this commit suggests the use of the maximum
between done quantity and reserved quantity. This logic is already
used in the putaway application process, when we check the forecasted
quantity by location:
https://github.com/odoo/odoo/blob/a217ba27600c64c9104f8c1f003afd74ad06bd05/addons/stock/models/stock_location.py#L297-L301
OPW-3100322
Forward-Port-Of: odoo/odoo#109570
Forward-Port-Of: odoo/odoo#108975Modifier flags often take integer values 0 or 1. Since they are not of type boolean, the `evalDomain` tries to convert them to a `Domain` instance. This commit makes sure such modifier values are correctly interpreted as boolean values. Forward-Port-Of: odoo/odoo#107414
Original PR description
Modifier flags often take integer values 0 or 1. Since they are not of type boolean, the `evalDomain` tries to convert them to a `Domain` instance. This commit makes sure such modifier values are correctly interpreted as boolean values. Forward-Port-Of: odoo/odoo#107414
Before this commit, there was a crash if you quickly dragged&dropped twice the same record from a column to another (i.e. before the first write was done). This was because we couldn't find (yet) the record from the column we were dragging it. This commit prevent the crash from happening. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.o
Original PR description
Before this commit, there was a crash if you quickly dragged&dropped twice the same record from a column to another (i.e. before the first write was done). This was because we couldn't find (yet) the record from the column we were dragging it. This commit prevent the crash from happening. Description of the issue/feature this PR addresses: 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#109672
Adding my CLA declaration. Forward-Port-Of: odoo/odoo#109597
Original PR description
Adding my CLA declaration. Forward-Port-Of: odoo/odoo#109597
The action menu was no longer showing in 16.0 since the view is always in edit mode. Forward-Port-Of: odoo/odoo#109679
Original PR description
The action menu was no longer showing in 16.0 since the view is always in edit mode. Forward-Port-Of: odoo/odoo#109679
…ndia. In this commit, I have added a new module for TCS/TDS Tax Report in India. It will load TCS/TDS-related taxes for an Indian Company. Added a new character field PAN on the partner. Description of the issue/feature this PR addresses: 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#109070
Original PR description
…ndia. In this commit, I have added a new module for TCS/TDS Tax Report in India. It will load TCS/TDS-related taxes for an Indian Company. Added a new character field PAN on the partner. Description of the issue/feature this PR addresses: 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#109070
In this commit, the following points are covered - updated error messages - remove renaming the `Customer Invoices` journal name - updated Fiscal Opening Date and Year End for Indian localization - updated Indian E-Invoicing report Forward-Port-Of: odoo/odoo#109388 Forward-Port-Of: odoo/odoo#109068
Original PR description
In this commit, the following points are covered - updated error messages - remove renaming the `Customer Invoices` journal name - updated Fiscal Opening Date and Year End for Indian localization - updated Indian E-Invoicing report Forward-Port-Of: odoo/odoo#109388 Forward-Port-Of: odoo/odoo#109068
This is used together with the audit features defined in account_reports (and fixed in the enterprise counterpart of this branch). Forward-Port-Of: odoo/odoo#109457
Original PR description
This is used together with the audit features defined in account_reports (and fixed in the enterprise counterpart of this branch). Forward-Port-Of: odoo/odoo#109457
Before this commit, cut/copy operation in non-html fields will trigger the _onClipboardCut/_onClipboardCopy handler as long as there is html field in the same form view. This will cause cut/copy fail when using chrome or edge. Only bind cut/copy event to html field as these event handlers are not related to non-html fields. Fixing https://github.com/odoo/odoo/issues/109386 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo
Original PR description
Before this commit, cut/copy operation in non-html fields will trigger the _onClipboardCut/_onClipboardCopy handler as long as there is html field in the same form view. This will cause cut/copy fail when using chrome or edge. Only bind cut/copy event to html field as these event handlers are not related to non-html fields. Fixing https://github.com/odoo/odoo/issues/109386 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#109467
The function write must return True when it ends. opw:3121809 Forward-Port-Of: odoo/odoo#109692
Original PR description
The function write must return True when it ends. opw:3121809 Forward-Port-Of: odoo/odoo#109692
Steps to reproduce: - install l10n_eg_edi_eta and website_sale modules - add any product in cart - try to add an egyptian address on checkout - it fails with an internal server error Bug: the `address_format` for `egypt` doesn't have a city field while it is actually important for egypt addresses and it is also required in the l10n Fix: add the city field OPW-3098006 Forward-Port-Of: odoo/odoo#108593
Original PR description
Steps to reproduce: - install l10n_eg_edi_eta and website_sale modules - add any product in cart - try to add an egyptian address on checkout - it fails with an internal server error Bug: the `address_format` for `egypt` doesn't have a city field while it is actually important for egypt addresses and it is also required in the l10n Fix: add the city field OPW-3098006 Forward-Port-Of: odoo/odoo#108593
When installing both documents and fleet and then, add a translation to the database. Both fleet and document will be translated the same way. This is due to the fact that both of them share a lot of similar value inside of the PSQL database. opw-3120320 Forward-Port-Of: odoo/odoo#109495
Original PR description
When installing both documents and fleet and then, add a translation to the database. Both fleet and document will be translated the same way. This is due to the fact that both of them share a lot of similar value inside of the PSQL database. opw-3120320 Forward-Port-Of: odoo/odoo#109495
Since its introduction with [1], there is an issue about the full link URL which is never set. The preview has 2 URL elements: - The main one, for which the text will either be the URL itself for external website or the page title for internal pages. - The "full one", which will simply be the full URL for internal pages. It's basically the text of the "main one" which is moved here when there is a title to display. But the "full one"'s url was never set, always being "#", meaning that when
Original PR description
Since its introduction with [1], there is an issue about the full link URL which is never set. The preview has 2 URL elements: - The main one, for which the text will either be the URL itself for external website or the page title for internal pages. - The "full one", which will simply be the full URL for internal pages. It's basically the text of the "main one" which is moved here when there is a title to display. But the "full one"'s url was never set, always being "#", meaning that when you click on the title you land on the correct page but when you click on the URL itself you don't go to that page. [1]: https://github.com/odoo/odoo/commit/8fcf930a6b6b7ffb0965b0a689c7a3117962ce7e task-3129267 Forward-Port-Of: odoo/odoo#109697
To Reproduce ============ - add event on calendar - edit the event and remove the user from participants list and add another one. - save the record -> traceback Problem ======= we try to read `hasReadAccess` from `this.followedThread` that is `null` in this case. Solution ======== check if `this.followedThread` is `null` or not opw-3126545 Forward-Port-Of: odoo/odoo#109649
Original PR description
To Reproduce ============ - add event on calendar - edit the event and remove the user from participants list and add another one. - save the record -> traceback Problem ======= we try to read `hasReadAccess` from `this.followedThread` that is `null` in this case. Solution ======== check if `this.followedThread` is `null` or not opw-3126545 Forward-Port-Of: odoo/odoo#109649
Forward-Port-Of: odoo/odoo#109486
Original PR description
Forward-Port-Of: odoo/odoo#109486
Issue # 1: Before this commit, copying an empty selection (collapsed range) produced a Traceback. Making onClipboardCopy return when the selected range is empty serve as double purpose: avoid that trace and not overwrite clipboard content with an empty string (leaving the previously copied content available for pasting). Issue # 2: Before this commit, copying a selection that spans over two or more lines was producing a text/plain content without line breaks. This happened because the text
Original PR description
Issue # 1: Before this commit, copying an empty selection (collapsed range) produced a Traceback. Making onClipboardCopy return when the selected range is empty serve as double purpose: avoid that trace and not overwrite clipboard content with an empty string (leaving the previously copied content available for pasting). Issue # 2: Before this commit, copying a selection that spans over two or more lines was producing a text/plain content without line breaks. This happened because the text was obtained getting the innerText property of a detached element (thus, not being rendered). In such case, the returned value is the same as textContent, which just concatenates the text content of text nodes (thus ignoring BR elements). Selection.toString(), for instance, represents line breaks in the selection as '\n' in the resulting string. This commit also adds basic unit tests for copying and cutting that were missing. task-3114102 Forward-Port-Of: odoo/odoo#108820
Tag color is already handled in tags_list.scss Also, `$min-contrast-ratio: 2.2` was creating contrast issues and was therefore dropped enterprise: - https://github.com/odoo/enterprise/pull/33145 task-3085081 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#107950
Original PR description
Tag color is already handled in tags_list.scss Also, `$min-contrast-ratio: 2.2` was creating contrast issues and was therefore dropped enterprise: - https://github.com/odoo/enterprise/pull/33145 task-3085081 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#107950
Current behavior: In the PoS base dashboard there is a "Top Orders" section that shows the top orders by amount. The orders are shown in ascending order when it should be descending. opw-3116114 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#109540
Original PR description
Current behavior: In the PoS base dashboard there is a "Top Orders" section that shows the top orders by amount. The orders are shown in ascending order when it should be descending. opw-3116114 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#109540
Purpose ======= Make sure we display a correct progress number. Specs ===== When configuring a survey as one page per question and the random selection of the questions, the numbers near the progress bar where not correct. With this commit they now are. task-2988062 part of : #104135 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#109645 Forward-Port-Of: odoo/odoo#108664
Original PR description
Purpose ======= Make sure we display a correct progress number. Specs ===== When configuring a survey as one page per question and the random selection of the questions, the numbers near the progress bar where not correct. With this commit they now are. task-2988062 part of : #104135 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#109645 Forward-Port-Of: odoo/odoo#108664
To reproduce on runbot: - Log in a Marc Demo (demo): * Go to Calendar app * Create a event, and set privacy to "Private" - Log in a Laurie Poiret (lauriepoiret): * Go to Calendar app * Add "YourCompany, Marc Demo" in attendee filter (sidebar) => crash TypeError: attendees is not iterable updateAttendeeData@https://22697845-16-0-all.runbot174.odoo.com/\ web/assets/2283-d20ef14/web.assets_backend.min.js:13915:603 This commit ensure that `attendees` is a list. --- I
Original PR description
To reproduce on runbot:
- Log in a Marc Demo (demo):
* Go to Calendar app
* Create a event, and set privacy to "Private"
- Log in a Laurie Poiret (lauriepoiret):
* Go to Calendar app
* Add "YourCompany, Marc Demo" in attendee filter (sidebar) => crash
TypeError: attendees is not iterable
updateAttendeeData@https://22697845-16-0-all.runbot174.odoo.com/\ web/assets/2283-d20ef14/web.assets_backend.min.js:13915:603
This commit ensure that `attendees` is a list.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#109748The title is aligned to the right on mobile. This is the result of the two rules of Bootstrap: ```css .modal-header { display: flex; justify-content: space-between; } ``` To avoid this we add `margin-inline: start`, to force left alignment of the title. Steps to reproduce: * Open Sales (on small/mobile screen) * Create a new Quotation * Click on Customer field => BUG title of dialog on the right Note: on desktop there is no problem as there is the close button on the right.
Original PR description
The title is aligned to the right on mobile. This is the result of the two rules of Bootstrap:
```css
.modal-header {
display: flex;
justify-content: space-between;
}
```
To avoid this we add `margin-inline: start`, to force left alignment of the title.
Steps to reproduce:
* Open Sales (on small/mobile screen)
* Create a new Quotation
* Click on Customer field => BUG title of dialog on the right
Note: on desktop there is no problem as there is the close button on the right.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#106231Case: - you have a BOM with 3 components (1 of each) consumed in their own separate operation. - you create a MO for 10 units of final product. - You do the first operation for 10 units of final product. - You do the second operation for 5 units of final product. Issue: the third operation will indicate 5/10 units of final product but will indicate 10/5 component to register. This fix ensures that the correct quantity of component is set automatically. task 3127618 Forward-Port-Of: od
Original PR description
Case: - you have a BOM with 3 components (1 of each) consumed in their own separate operation. - you create a MO for 10 units of final product. - You do the first operation for 10 units of final product. - You do the second operation for 5 units of final product. Issue: the third operation will indicate 5/10 units of final product but will indicate 10/5 component to register. This fix ensures that the correct quantity of component is set automatically. task 3127618 Forward-Port-Of: odoo/enterprise#35696
Forward-Port-Of: odoo/enterprise#35703
Original PR description
Forward-Port-Of: odoo/enterprise#35703
Steps to reproduce: - install "website_sale" and "sale_renting" modules; - for a product, add an accessory product which can be rented; - go to ecommerce; - add the product to the cart; - view the cart. Issue: A traceback appears. Cause: We are trying to access a dictionary value with a key which does not exist and more particularly, we try to access the value of a product that can be rented. Solution: Test if a product can be rented using the `is_rental` key before accessing
Original PR description
Steps to reproduce: - install "website_sale" and "sale_renting" modules; - for a product, add an accessory product which can be rented; - go to ecommerce; - add the product to the cart; - view the cart. Issue: A traceback appears. Cause: We are trying to access a dictionary value with a key which does not exist and more particularly, we try to access the value of a product that can be rented. Solution: Test if a product can be rented using the `is_rental` key before accessing its information. opw-3117535 Forward-Port-Of: odoo/enterprise#35695
before this commit, in the accounting reports, the icon and selected filter in the date filter is showing without any spaces in between them. after this commit, a space is added in between the calendar icon and selected filter as we have for the other filters in screen like partner filter and account filter. before:  after:  after:  Forward-Port-Of: odoo/enterprise#35499
In the new version 16.0, changing the quantity produced on the tablet view of a workorder does not automatically change the quantity of consumed material when focusing out of the input field. The only way to do so is to do another action (e.g. press the menu button). This patch fixes this issue. task 2985735 Forward-Port-Of: odoo/enterprise#34904
Original PR description
In the new version 16.0, changing the quantity produced on the tablet view of a workorder does not automatically change the quantity of consumed material when focusing out of the input field. The only way to do so is to do another action (e.g. press the menu button). This patch fixes this issue. task 2985735 Forward-Port-Of: odoo/enterprise#34904
We should allow different identifiers for suppliers and customers. The system parameters are not used anymore, for the length of the account field in the export. We want this in stable, so it is a new module. t-3053417 Forward-Port-Of: odoo/enterprise#34959 Forward-Port-Of: odoo/enterprise#34563
Original PR description
We should allow different identifiers for suppliers and customers. The system parameters are not used anymore, for the length of the account field in the export. We want this in stable, so it is a new module. t-3053417 Forward-Port-Of: odoo/enterprise#34959 Forward-Port-Of: odoo/enterprise#34563
Colors that have been modified : Greyscale colors : o-gray-100 to o-grey-900 Satus colors : o-success, o-info, o-warning and o-danger Others : o-main-favorite-color, o-main-code-color Accessibility improved (better contrast) Harmony in colors improved Also fixed in this PR : color gap between light mode and dark mode tags task-3085081 community : https://github.com/odoo/odoo/pull/107950 Forward-Port-Of: odoo/enterprise#33145
Original PR description
Colors that have been modified : Greyscale colors : o-gray-100 to o-grey-900 Satus colors : o-success, o-info, o-warning and o-danger Others : o-main-favorite-color, o-main-code-color Accessibility improved (better contrast) Harmony in colors improved Also fixed in this PR : color gap between light mode and dark mode tags task-3085081 community : https://github.com/odoo/odoo/pull/107950 Forward-Port-Of: odoo/enterprise#33145
Before this commit, if we scrolled down on article and opened a new one, the state of scroll would stay the same. Now we scroll up the article before showing it on a page. Task-3101372 Forward-Port-Of: odoo/enterprise#35277
Original PR description
Before this commit, if we scrolled down on article and opened a new one, the state of scroll would stay the same. Now we scroll up the article before showing it on a page. Task-3101372 Forward-Port-Of: odoo/enterprise#35277
To reproduce, on a db with only the demo data: 1) Open the Aged Payable/Receivable. 2) Select a report date 2 months in the future. 3) Unfold Azure Interior's line. It has one late invoice, from the current month. 4) Click on "Journal Items" for Azure Interior. An empty tree view is shown. ===> This is because the "Report Dates" filter uses a date_from and a date_to. Despite the fact Aged Payable/Receivable both only allow the selection of one date, implementation reasons make it so that
Original PR description
To reproduce, on a db with only the demo data: 1) Open the Aged Payable/Receivable. 2) Select a report date 2 months in the future. 3) Unfold Azure Interior's line. It has one late invoice, from the current month. 4) Click on "Journal Items" for Azure Interior. An empty tree view is shown. ===> This is because the "Report Dates" filter uses a date_from and a date_to. Despite the fact Aged Payable/Receivable both only allow the selection of one date, implementation reasons make it so that their options dict contains both such dates : so the Report Dates filter here only applies to this range, which is not what we want. To select all the entries before the date_to, we add a new filter in the community counterpart of this branch. Existing users will have to update their database to benefit from this fix. Without doing so, the report will consider all the move lines and ignore the report dates. Forward-Port-Of: odoo/enterprise#35588
Steps to reproduce: Whenever we create a sales order with the shipping configured with EasyPost it estimates the price. Imagine we create a sales order, confirm it, and then we realize we made a mistake with one of the products. Given that the picking was already confirmed, we cannot delete the line, however, we can change its quantity to 0. Problem: If we change the quantity of one of the products to 0, we currently get an error "The estimated price cannot be computed because the weight o
Original PR description
Steps to reproduce: Whenever we create a sales order with the shipping configured with EasyPost it estimates the price. Imagine we create a sales order, confirm it, and then we realize we made a mistake with one of the products. Given that the picking was already confirmed, we cannot delete the line, however, we can change its quantity to 0. Problem: If we change the quantity of one of the products to 0, we currently get an error "The estimated price cannot be computed because the weight of your product %s is missing.". Solution: Such raise is not needed in this particular case. If all the quantities are 0, there is already another error that will be raised before. If some of the products are 0, the weight is also 0 and it will not impact the package. The error will still be raised (as it should) if the quantity is not 0 and the weight has not been defined on the product. OPW-2845255 Forward-Port-Of: odoo/enterprise#34710 Forward-Port-Of: odoo/enterprise#33748
Steps: - Install documents_hr - Click on "My Profile" in the user dropdown - Click on "Documents" smart button There is just the default kanban view, the list view is not present opw-3090397 Forward-Port-Of: odoo/enterprise#35675
Original PR description
Steps: - Install documents_hr - Click on "My Profile" in the user dropdown - Click on "Documents" smart button There is just the default kanban view, the list view is not present opw-3090397 Forward-Port-Of: odoo/enterprise#35675
Before this commit, the trial balance was not balanced when using a period other that a fiscal year. The problem was due to an error in the date_to computation of the initial balance when the key 'include_current_year_in_unaff_earnings' was True. We were computing the initial balance date_to once in '_get_options_initial_balance' and then again in '_get_options_unaffected_earnings' when we should just use the date_to already computed in '_get_options_initial_balance'. Task-id: 3099868
Original PR description
Before this commit, the trial balance was not balanced when using a period other that a fiscal year. The problem was due to an error in the date_to computation of the initial balance when the key 'include_current_year_in_unaff_earnings' was True. We were computing the initial balance date_to once in '_get_options_initial_balance' and then again in '_get_options_unaffected_earnings' when we should just use the date_to already computed in '_get_options_initial_balance'. Task-id: 3099868 Forward-Port-Of: odoo/enterprise#34955