Thursday, September 16, 2021
44 changes · master
Enhancements to existing features
Work entries for employees are now generated in smaller scheduled batches instead of one long database transaction. This improves reliability and significantly reduces processing time for large companies, helping payroll-related data stay up to date without slowdowns.
Original PR description
TaskID: 2646056
This update makes it easier to add images from web links that include sizing or other extra parameters, preventing valid images from being rejected. It also improves website event editing by hiding repeated date displays, making event pages cleaner and less confusing to edit.
Original PR description
This branch adds various small improvements, each described in their respective commit. task-2618494
Chrome could incorrectly autofill signing text fields with saved usernames when users opened a signature request. This update prevents that unwanted autofill, helping users complete documents without accidental or confusing pre-filled information.
Original PR description
Ideally, we should use 'autocomplete' to prevent the autofill. But currently, Chrome doesn't support this. By default, Chome will search 'input' with type 'password' and auto fill its preivous 'input' with type 'text' Since we use pdfjs in the iframe, it has a 'password' 'input' to decrypt PDFs, and the 'input' triggers autofill of Chrome. We add a fake 'password' 'input' before all sign items within the iframe to prevent Chrome autofilling 'input' in our sign items Before this task: Currently, 'autocomplete' doesn't work for Chrome. So when the a user opens a sign request, Chrome will try to fill the text input with a user name. taskid: 2641679
Signed documents now keep the correct location information based on GeoIP after a signature is completed. This improves the accuracy of location details shown later when documents are viewed or downloaded.
Original PR description
Get correct geo location according to GeoIP after signature Before this commit, when a sign request item is signed, Its longtitude and latitude for future "Download/View" will be the same as the geo location of signature taskid: 2633349
Resolved issues and error corrections
The French accounting localization no longer includes unused negative tax groups. Taxes previously assigned to those groups are now linked to the corresponding standard tax groups, reducing confusion in tax configuration and reporting.
Original PR description
There exist negative tax groups defined in the account data. They appear to have no meaning. This removes the negative tax groups from account data. and reassigns the taxes that were in the negative tax groups to their positive counterparts.
Features or functions removed from Odoo
Odoo removed an old redirect helper that is no longer needed because modern browsers now preserve URL fragments during redirects. Redirects now use a standard library approach, simplifying maintenance while keeping login, portal, web, and website navigation behavior aligned with current browser standards.
Original PR description
This helper is now obsolete as most modern mainstream browsers now implement RFC 7231 [1], which dictates that browsers preserve the original fragment of the URL through redirects. Its use has been replaced by `werkzeug.utils.redirect` since browsers now automatically block/sandbox `data:` and `javascript:` schemes. Complements https://github.com/odoo/enterprise/pull/3572 [1] https://tools.ietf.org/html/rfc7231
Miscellaneous changes
See sub-commits for details. This merge allows to create and edit gradients instead of just having the possibility to select pre-defined ones. task-2599771 Forward-Port-Of: odoo/odoo#74045
Original PR description
See sub-commits for details. This merge allows to create and edit gradients instead of just having the possibility to select pre-defined ones. task-2599771 Forward-Port-Of: odoo/odoo#74045
This update fixes a typo in an internal stock module test case. It does not change how users work with inventory, but helps keep automated checks clear and reliable for future updates.
Original PR description
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
This commits adds to the existing conditional visibility option introduced in [1], the option to display or hide blocs to a user, depending on if he's logged in or not. A select widget was added as an alternative to the many2one widgets that were currently used, as we don't need to connect to the database to display logged in/logged out option. [1]: 1c44278 task-2618946 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of
Original PR description
This commits adds to the existing conditional visibility option introduced in [1], the option to display or hide blocs to a user, depending on if he's logged in or not. A select widget was added as an alternative to the many2one widgets that were currently used, as we don't need to connect to the database to display logged in/logged out option. [1]: 1c44278 task-2618946 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#75107
Before this commit, if a user does a search and press enter before the commands are loaded, then the wrong command will be executed. So we will wait for the commands to be loaded before executing the right command. Solves the navigation problems with the arrows in the command palette on firefox. 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
Original PR description
Before this commit, if a user does a search and press enter before the commands are loaded, then the wrong command will be executed. So we will wait for the commands to be loaded before executing the right command. Solves the navigation problems with the arrows in the command palette on firefox. 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#76477
The fix https://github.com/odoo/odoo/commit/18ea11c99a7e2bd58d7469927352587cb14c76c4 incorrectly set the rule o_control_panel .o_cp_bottom_left { display: inline-block } to fix a problem with the graph view buttons in mobile mode: the graph view has many buttons and they were put on the same line pushing the view switcher far too rigth. But the above rule had some other unexpected effects. For example, an action menu button was put incorrectly on an different line from the button line. Her
Original PR description
The fix https://github.com/odoo/odoo/commit/18ea11c99a7e2bd58d7469927352587cb14c76c4 incorrectly set the rule
o_control_panel .o_cp_bottom_left { display: inline-block } to fix a
problem with the graph view buttons in mobile mode: the graph view has
many buttons and they were put on the same line pushing the view switcher
far too rigth. But the above rule had some other unexpected effects.
For example, an action menu button was put incorrectly on an different line
from the button line. Here we simply fix the css rules that regulate on witch line
the control panel buttons are put and their spacing.
Forward-Port-Of: odoo/odoo#76569Forward-Port-Of: odoo/odoo#76484
Original PR description
Forward-Port-Of: odoo/odoo#76484
While only notes can be deleted on threads, some tracking messages are created with the type "notification", some messages are created as notes. This commit prevents deletion and editing of messages that have tracking values, as they are invaluable for traceability and not user-created. Forward-Port-Of: odoo/odoo#76547
Original PR description
While only notes can be deleted on threads, some tracking messages are created with the type "notification", some messages are created as notes. This commit prevents deletion and editing of messages that have tracking values, as they are invaluable for traceability and not user-created. Forward-Port-Of: odoo/odoo#76547
1. Define a product [TEST] with automated inventory valuation (AVCO) 2. Define a landed cost product in the same way 3. Create a RFQ for [TEST], Confirm and Receive product 4. Create Bill, add the landed cost on the bill 5. Confirm the Bill and create the landed cost (from transfer of point 3) 6. Create a SO for [TEST], confirm, delivery and create the invoice 7. Generate product margin analysis, [TEST] will be present 8. Register a payment for the invoice (it should have the status 'In
Original PR description
1. Define a product [TEST] with automated inventory valuation (AVCO) 2. Define a landed cost product in the same way 3. Create a RFQ for [TEST], Confirm and Receive product 4. Create Bill, add the landed cost on the bill 5. Confirm the Bill and create the landed cost (from transfer of point 3) 6. Create a SO for [TEST], confirm, delivery and create the invoice 7. Generate product margin analysis, [TEST] will be present 8. Register a payment for the invoice (it should have the status 'In Payment') Generate product margin analysis again, [TEST] entries will be missing This occur because, when the invoice is in 'in_payment' state the records are not taken into account opw-2631974 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#76449
Currently, a bunch of features are not supported for guests, some on purpose (eg modifying the channel name or description), while some are not yet implemented (eg /commands or the member list). This PR adapts the code so that these unsupported features no longer have a corresponding element in the UI, since these interacting with these UI elements only leads to a crash. This PR also adds the main components container to guest pages so that guests now get error dialogs when errors occur. For
Original PR description
Currently, a bunch of features are not supported for guests, some on purpose (eg modifying the channel name or description), while some are not yet implemented (eg /commands or the member list). This PR adapts the code so that these unsupported features no longer have a corresponding element in the UI, since these interacting with these UI elements only leads to a crash. This PR also adds the main components container to guest pages so that guests now get error dialogs when errors occur. Forward-Port-Of: odoo/odoo#76557
Forward-Port-Of: odoo/odoo#76566
Original PR description
Forward-Port-Of: odoo/odoo#76566
Forward-Port-Of: odoo/odoo#76568
Original PR description
Forward-Port-Of: odoo/odoo#76568
Steps to reproduce: Open the gantt view and add a few shifts for different resources Observed behavior: https://nimb.ws/1t38Jl resources are not sorted by alphabetical order Expected behavior: https://nimb.ws/NqIAG3 resources should be sorted by alphabetical order task-2633936 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76570
Original PR description
Steps to reproduce: Open the gantt view and add a few shifts for different resources Observed behavior: https://nimb.ws/1t38Jl resources are not sorted by alphabetical order Expected behavior: https://nimb.ws/NqIAG3 resources should be sorted by alphabetical order task-2633936 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76570
PURPOSE To fix the stat button count of mailing.mailing in campaign. SPECIFICATION Currently we are getting all records of mailing.mailing instead of getting only records with mailing_type=mail. To bE: Only show count of records which have mailing_type = mail. TASK ID: 2417993 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76574 Forward-Port-Of: odoo/odoo#74841
Original PR description
PURPOSE To fix the stat button count of mailing.mailing in campaign. SPECIFICATION Currently we are getting all records of mailing.mailing instead of getting only records with mailing_type=mail. To bE: Only show count of records which have mailing_type = mail. TASK ID: 2417993 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76574 Forward-Port-Of: odoo/odoo#74841
Forward-Port-Of: odoo/odoo#76575
Original PR description
Forward-Port-Of: odoo/odoo#76575
Description of the issue/feature this PR addresses: Before this patch, if you wrote newlines or more than a single whitespace character while sharing any document, in the note, those'd get collapsed in the final email. Current behavior before PR: https://user-images.githubusercontent.com/973709/133422942-fb907f77-43ae-443b-b64b-14f23c07840d.mp4 Desired behavior after PR is merged: https://user-images.githubusercontent.com/973709/133422949-76c8dd88-580d-4a97-a232-46c49bc1a020.mp4
Original PR description
Description of the issue/feature this PR addresses: Before this patch, if you wrote newlines or more than a single whitespace character while sharing any document, in the note, those'd get collapsed in the final email. Current behavior before PR: https://user-images.githubusercontent.com/973709/133422942-fb907f77-43ae-443b-b64b-14f23c07840d.mp4 Desired behavior after PR is merged: https://user-images.githubusercontent.com/973709/133422949-76c8dd88-580d-4a97-a232-46c49bc1a020.mp4 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @Tecnativa TT31901 Forward-Port-Of: odoo/odoo#76577
Before this PR, the RPC to notify peers was called too much time too quickly. Reducing request overload significantly improves the overall connection time. Forward-Port-Of: odoo/odoo#76580
Original PR description
Before this PR, the RPC to notify peers was called too much time too quickly. Reducing request overload significantly improves the overall connection time. Forward-Port-Of: odoo/odoo#76580
Forward-Port-Of: odoo/odoo#76585
Original PR description
Forward-Port-Of: odoo/odoo#76585
When generating coupons for customers, the email was sent twice due to the values given on the email_values that is generating a TO (email_to) value (plus using the one given on the template (recipients_ids)) opw-2574046 Forward-Port-Of: odoo/odoo#74760
Original PR description
When generating coupons for customers, the email was sent twice due to the values given on the email_values that is generating a TO (email_to) value (plus using the one given on the template (recipients_ids)) opw-2574046 Forward-Port-Of: odoo/odoo#74760
Currently, if the survey participant does not answer questions of type: - simple_choice - multiple_choice - matrix The system does not register any survey.user_input_line with the "skipped" attribute set to True. Meaning that this question's answer will not appear in the survey statistics as skipped (in fact it will not appear at all). This commit makes sure we correctly save a user_input_line set as skipped=True when not answering to those types of questions. A unit test has been
Original PR description
Currently, if the survey participant does not answer questions of type: - simple_choice - multiple_choice - matrix The system does not register any survey.user_input_line with the "skipped" attribute set to True. Meaning that this question's answer will not appear in the survey statistics as skipped (in fact it will not appear at all). This commit makes sure we correctly save a user_input_line set as skipped=True when not answering to those types of questions. A unit test has been added to make sure that we consider every non-answered question type as properly skipped within the survey statistics. Task-2622869 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#76587 Forward-Port-Of: odoo/odoo#75586
Clean/remove subcontracting operation type when we uninstall subcontracting. task-2633558 Forward-Port-Of: odoo/odoo#76448
Original PR description
Clean/remove subcontracting operation type when we uninstall subcontracting. task-2633558 Forward-Port-Of: odoo/odoo#76448
Before this fix, a cash basis OSS tax used together with a product using the "non-EU origin" tag didn't appear properly in the OSS import report. This was due to the fact the product tag was not copied on the cash basis move: it only appeared on the invoice, on non exigible lines. To fix that, we make the choice to keep the product tag as markup on the invoice, and to copy it to the cash basis lines created from move lines containing this tag. We therefore need a non-ambiguous way to identify
Original PR description
Before this fix, a cash basis OSS tax used together with a product using the "non-EU origin" tag didn't appear properly in the OSS import report. This was due to the fact the product tag was not copied on the cash basis move: it only appeared on the invoice, on non exigible lines. To fix that, we make the choice to keep the product tag as markup on the invoice, and to copy it to the cash basis lines created from move lines containing this tag. We therefore need a non-ambiguous way to identify account.account.tag objects that are used on products, since we don't want to copy tags used by taxes. Hence, we introduct a new value for the 'applicability' field of account.account.tag, limitating their use to products. Forward-Port-Of: odoo/odoo#76583
Description of the issue/feature this PR addresses: When validating a stock picking with expired products, in some cases a validation error is raised because default_lot_ids is passed back in context for creating new stock_move_line. The behaviour is similar to the one fixed with https://github.com/odoo/odoo/pull/73209 but on stock picking when reference was on manufacturing. Problem reproduced on runbot on v14.0 community edition Current behavior before PR: - Go to Inventor
Original PR description
Description of the issue/feature this PR addresses: When validating a stock picking with expired products, in some cases a validation error is raised because default_lot_ids is passed back in context…
Description of the issue/feature this PR addresses:
When validating a stock picking with expired products, in some cases a validation error is raised because default_lot_ids is passed back in context for creating new stock_move_line.
The behaviour is similar to the one fixed with https://github.com/odoo/odoo/pull/73209 but on stock picking when reference was on manufacturing.
Problem reproduced on runbot on v14.0 community edition
Current behavior before PR:
- Go to Inventory > Configuration > Settings and activate "Expiration Dates"
- Create a storable product tracked by lot with expiration date (i.e. Product A)
- Update quantity of Product A in a lot with an expired expiration date (i.e. Lot A)
- Create a storable product tracked by lot (i.e. Product B)
- Create a Stock Picking for Product A with a quantity to deliver set to 1
- Save the Picking and mark as To-Do
- Edit Picking to add Product B with quantity >= 1
- Validate Picking
- You get a confirmation popup : "You are going to deliver the product Product A, Lot A which is expired. Do you confirm you want to proceed ?"
- Click on Confirm
The following Validation Error is triggered:
"This lot Lot A is incompatible with this product Product B"
Desired behavior after PR is merged:
Validate picking and create extra stock move lines without error
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#76087Description 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#75639
Original PR description
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#75639
Since cfe079221cd unsplash is not working anymore, as that commit did not adapt the unsplash code to that change. task-2581567 Forward-Port-Of: odoo/odoo#76360
Original PR description
Since cfe079221cd unsplash is not working anymore, as that commit did not adapt the unsplash code to that change. task-2581567 Forward-Port-Of: odoo/odoo#76360
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#76122
Original PR description
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#76122
**Description of the issue/feature this PR addresses:** Add the country natural vat number for partners from Uruguay. **Current behavior before PR:** If you create an invoice for an Uruguayan partner (not a company) and then you try to export the vat book it will return a traceback since we do not have the natural vat to report to AFIP. **Steps to replicate the error:** 1. Create a partner from Uruguay with Cédula Extranjera and AFIP responsibility type: Cliente / Proveedor del Exterio
Original PR description
**Description of the issue/feature this PR addresses:** Add the country natural vat number for partners from Uruguay. **Current behavior before PR:** If you create an invoice for an Uruguayan partner (not a company) and then you try to export the vat book it will return a traceback since we do not have the natural vat to report to AFIP. **Steps to replicate the error:** 1. Create a partner from Uruguay with Cédula Extranjera and AFIP responsibility type: Cliente / Proveedor del Exterior 2. Create an invoice for this partner 3. Try to export the Sales VAT Book -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#75860
Before this commit opening the color palette only checked for the available space below the button to open the popup above instead. Because of this the popup sometimes opened higher than the top of the screen making it unusable. After this commit an additional check is done on the space available above the button. If there is not enough room above then just opens below, which makes the area scrollable if there was insufficient space, thus keeping the palette usable. task-2599771 D
Original PR description
Before this commit opening the color palette only checked for the available space below the button to open the popup above instead. Because of this the popup sometimes opened higher than the top of the screen making it unusable. After this commit an additional check is done on the space available above the button. If there is not enough room above then just opens below, which makes the area scrollable if there was insufficient space, thus keeping the palette usable. task-2599771 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#76209
Following wowl and https://github.com/odoo/odoo/pull/73725, isRpcError no longer works. We introduce a new method called isConnectionError since it's actually what we are interested of in the previous use of isRpcError. After handling connection error, we just rethrow any other errors such as RPCError (which includes server error such as UserError or any programming error in the server) and let the errorHandler in Chrome handle them. -- I confirm I have signed the CLA and read the PR
Original PR description
Following wowl and https://github.com/odoo/odoo/pull/73725, isRpcError no longer works. We introduce a new method called isConnectionError since it's actually what we are interested of in the previous use of isRpcError. After handling connection error, we just rethrow any other errors such as RPCError (which includes server error such as UserError or any programming error in the server) and let the errorHandler in Chrome handle them. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#75857
Before this commit the link popover test sometimes froze on a test that was added to hide the popover in case it did not work automatically. The popover is however automatically hidden before this step from time to time, thus making this step blocking. After this commit this step just hides the popover in case it was still there. Related to staging build https://runbot.odoo.com/runbot/build/9990797 Description of the issue/feature this PR addresses: Current behavior before PR:
Original PR description
Before this commit the link popover test sometimes froze on a test that was added to hide the popover in case it did not work automatically. The popover is however automatically hidden before this step from time to time, thus making this step blocking. After this commit this step just hides the popover in case it was still there. Related to staging build https://runbot.odoo.com/runbot/build/9990797 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#76638
When displaying a view with the same html field in multiple places, we would have some conflicts between the editors if they start in collaborative on the same channel. task-2647125 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76637
Original PR description
When displaying a view with the same html field in multiple places, we would have some conflicts between the editors if they start in collaborative on the same channel. task-2647125 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76637
This PR fixes behaviors of the project task gantt view. As the ORM doesn't handle the fake many2many field defined in the project task model : personal_stage_type_ids, we need to write on the personal_stage_type_id and use its inverse method. This is done by removing the personal_stage_type_ids from every vals passed through rpc calls, or through context keys, and adding the personal_stage_type_id key to thoses vals/context. task-2642872 Forward-Port-Of: odoo/enterprise#20934
Original PR description
This PR fixes behaviors of the project task gantt view. As the ORM doesn't handle the fake many2many field defined in the project task model : personal_stage_type_ids, we need to write on the personal_stage_type_id and use its inverse method. This is done by removing the personal_stage_type_ids from every vals passed through rpc calls, or through context keys, and adding the personal_stage_type_id key to thoses vals/context. task-2642872 Forward-Port-Of: odoo/enterprise#20934
The '&' should be removed. Before this commit, if the server uses the latest(0.21.0) libsass the '&' will trigger an error "Top Level selectors May not Contain the Parent Selector &" And the scss cannot be compiled successfully. Forward-Port-Of: odoo/enterprise#20862
Original PR description
The '&' should be removed. Before this commit, if the server uses the latest(0.21.0) libsass the '&' will trigger an error "Top Level selectors May not Contain the Parent Selector &" And the scss cannot be compiled successfully. Forward-Port-Of: odoo/enterprise#20862
When signing selection items in sign, the options are shown unaligned and depending on the viewport, even hidden. This PR fixes this alignment error by changing the selection sign item css only for the sign session. task-2628919 Forward-Port-Of: odoo/enterprise#20362
Original PR description
When signing selection items in sign, the options are shown unaligned and depending on the viewport, even hidden. This PR fixes this alignment error by changing the selection sign item css only for the sign session. task-2628919 Forward-Port-Of: odoo/enterprise#20362
The Deductions should only be applied to types of operations 1001, 1002, 1003 and 1004. These operations are intended exclusively for invoices that meet this requirement. Currently, we are generating the value for all invoices that contain a product with deductions or that exceed 700 soles. The latter prevents invoices from being generated for Non-domiciled sales that do not qualify as export that contain products with the assigned deduction field. The regulations indicate that for
Original PR description
The Deductions should only be applied to types of operations 1001, 1002, 1003 and 1004. These operations are intended exclusively for invoices that meet this requirement. Currently, we are generating the value for all invoices that contain a product with deductions or that exceed 700 soles. The latter prevents invoices from being generated for Non-domiciled sales that do not qualify as export that contain products with the assigned deduction field. The regulations indicate that for export invoices with tax free, deductions should not be considered.   Forward-Port-Of: odoo/enterprise#20911
TaskIDS: 2464368, 2646046 Forward-Port-Of: odoo/enterprise#20670
Original PR description
TaskIDS: 2464368, 2646046 Forward-Port-Of: odoo/enterprise#20670
From technical: 1) The account 754110 should be into account in section "a) provenant d’entreprises liées" (code LU_PLABR_729). 2) The section 12. “Share of profit or loss of undertakings accounted for under the equity method" should be translated as "Quote-part dans le résultat des entreprises mises en équivalence". From customer: 3) "LU_BSABR_205" should be corrected to include all the accounts starting by 4025 => ('account_id.code', '=like', '4025%') instead of ('account_id.code', '=',
Original PR description
From technical:
1) The account 754110 should be into account in section "a) provenant d’entreprises liées" (code LU_PLABR_729).
2) The section 12. “Share of profit or loss of undertakings accounted for under the equity method" should be translated as "Quote-part dans le résultat des entreprises mises en équivalence".
From customer:
3) "LU_BSABR_205" should be corrected to include all the accounts starting by 4025 => ('account_id.code', '=like', '4025%') instead of ('account_id.code', '=', '4025%').
4) "LU_BS_155" ("a) Matières premières et consommables") should be renamed "1. Matières premières et consommables".
opw-2634704
Forward-Port-Of: odoo/enterprise#20869
Forward-Port-Of: odoo/enterprise#20840Before this fix, a cash basis OSS tax used together with a product using the "non-EU origin" tag didn't appear properly in the OSS import report. This was due to the fact the product tag was not copied on the cash basis move: it only appeared on the invoice, on non exigible lines. To fix that, we make the choice to keep the product tag as markup on the invoice, and to copy it to the cash basis lines created from move lines containing this tag. We therefore need a non-ambiguous way to identify
Original PR description
Before this fix, a cash basis OSS tax used together with a product using the "non-EU origin" tag didn't appear properly in the OSS import report. This was due to the fact the product tag was not copied on the cash basis move: it only appeared on the invoice, on non exigible lines. To fix that, we make the choice to keep the product tag as markup on the invoice, and to copy it to the cash basis lines created from move lines containing this tag. We therefore need a non-ambiguous way to identify account.account.tag objects that are used on products, since we don't want to copy tags used by taxes. Hence, we introduct a new value for the 'applicability' field of account.account.tag, limitating their use to products. Forward-Port-Of: odoo/enterprise#20900
Forward-Port-Of: odoo/enterprise#20844
Original PR description
Forward-Port-Of: odoo/enterprise#20844