Daily updates from Odoo
Navigate
Branch
Friday, April 18, 2025
49 changes
30 changes
New functionality added to Odoo
Adds Austrian point-of-sale localization to help businesses comply with RKSV cash register requirements. The update supports tamper-proof transaction signing, compliant receipts with QR codes, and audit-ready transaction records using Fiskaly.
Original PR description
The Cash Register Security Ordinance (RKSV) has been in effect in Austria, aimed at making transactions tamper-proof and thus increasing transparency and security in business payments. RKSV (Registrierkassensicherheitsverordnung), ensures tax compliance and prevents fraud by regulating cash register systems.. - Mandatory Cash Register: Required if annual turnover > €15,000 and cash > €7,500. - Tamper-Proof Data: All transactions must be digitally signed to preventmanipulation. - Signature Creation Unit (SCU): Cryptographic device generates digital signatures. - Receipt Obligation: Receipts must include key details and a QR code with a digital signature. - Data Collection Protocol (DEP): Secure log of all transactions for audits (DEP7). These key aspects of the RKSV have been implemented in our system using Fiskaly. Task: 4013917
Enhancements to existing features
A manufacturing work order test was updated to use the current batch size field after an older field was removed. This helps keep automated checks aligned with the product and reduces the risk of future manufacturing changes being blocked by outdated tests.
Original PR description
In this commit: ================= - changed the field in a test case from counter to maximum_batch_size as it removed from the model. task- 4274773
This update makes it possible to use additional PDF generation engines, including Paper-muncher, for business reports. It also adds a related action in accounting reports, giving teams more flexibility in how they produce and handle PDF documents.
Customers can now change the invoicing address for their subscriptions directly from the portal. This reduces manual requests handled by sales, support, or finance teams while keeping shipping address changes out of scope for now to avoid billing or tax risks.
Original PR description
## Purpose Currently, a customer can not change the invoicing and the delivery address of a subscription from the portal it leads to additional work for sales, support or financial team due to customer requests. task id: 4655497
Administrators can now better control how access groups are displayed across many Odoo apps. This improves the setup experience for user permissions by making group organization clearer and more configurable.
Original PR description
task: 4341594
UPS shipping settings now let users require a recipient signature for deliveries, helping protect high-value shipments. The UPS configuration screen was also reorganized so related delivery payment and signature options are easier to find and read.
Original PR description
- Enabled the option to require a signature for UPS shipments, allowing users to choose this for high-value packages upon delivery. - Improved the UPS configuration form by grouping the "Duties Paid By" and "Require Signature" fields into separate columns for better usability and readability. task-4504624
The restaurant preparation display setup now stays aligned with the main restaurant point-of-sale setup process. This helps avoid setup issues when loading demo data and keeps the feature compatible with the broader system.
Original PR description
This commit updates the `_load_restaurant_demo_data` method to accept a required parameter, ensuring compatibility with its parent method. Task: 4572251 Related: odoo/odoo#197861
The signing process now has a clearer and more helpful refusal flow, including an improved dialog and better email messaging. This makes it easier for users to decline documents confidently and understand what happens next.
Original PR description
This update makes it easier for users to refuse documents by improving the following: - The dialog interface. - The email title and description. - Overall user interface (UI). task-4210639
Maintenance screens now include clearer URL paths for the main actions, making pages easier to identify, bookmark, and share. This improves navigation consistency for users working with maintenance requests and worksheets without changing core workflows.
Original PR description
Added path in URL for the main actions of Maintenance.
WhatsApp live chat now aligns with new call tracking information added in the related core update. This keeps automated security checks compatible with the new call statistics data so live chat call reporting can work reliably.
Original PR description
The community coutnerpart of this PR adds call statistics to live chat. A new field was added to keep track of calls so tests that assets bus notifications have to be adapted. task-4614125 community: https://github.com/odoo/odoo/pull/203684
Restaurants and shops can now track how long each POS order takes to prepare and serve, with clearer timing information shown on preparation displays. Completed orders can also be automatically cleared, helping teams keep displays focused and review performance through new reporting.
Original PR description
- Added `auto_clear` and `clear_time_interval` fields to auto-remove completed orders (from "Order status screen"). - Introduced `completion_time` field to track total order preparation & service duration. - Updated POS order views to display `preparation_time` and `service_time`. - Improved frontend logic for order status updates and clearing outdated orders. - Added new `preparation_time_report` model & SQL view for preparation time analysis. task-id: 4623457
The Helpdesk onboarding tour text was updated to better explain the internal note step. This avoids suggesting that selecting a channel notifies people in that channel, reducing confusion for new users.
Original PR description
This commit adapts a step asking to click on `log note` button to send an internal note. We no longer mention the user can select a channel because that feature does not ping the users inside the channel selected, it is just to have a button to redirect the user to that channel. task-4662201
Production quantities are no longer filled in automatically when a work order starts. Users must now register production deliberately through the wizard or quick registration, helping prevent premature or unintended production records.
Original PR description
- Updated the logic for the "Register Production" cross-out line, ensuring production registration can only be done manually—either through the wizard or quick registration. - Replaced the old flow, where quantities were auto-set on starting a work order, with manual registration, updating all relevant flows accordingly. - This change ensures production registrations are intentional and accurate, preventing unintended or premature entries. Task-id: 4387836
Manufacturing work order users now receive immediate confirmation after completing Scrap, Quality Alert, and Move to Work Center actions. This helps reduce uncertainty on the shop floor and supports a smoother, more confident workflow.
Original PR description
Added feedback notifications for Scrap, Quality Alert, and Move to Work Center actions. Users now receive immediate confirmation upon completing these actions, ensuring clear feedback and a smoother workflow. task-4403621
The contact form has been refreshed to make key partner information easier to review. Users can now see relevant partner statistics at a glance, with details adapting based on installed apps such as accounting, helpdesk, payroll, and WhatsApp.
Original PR description
This PR focuses on enhancing the UI of the contacts views and some part of CRM views. Improve partner view. Introduce statistics field on partner, allowing to see various statistics at a glance, based on installed applications. Enterprise PR: odoo/enterprise#75958 Task [link](https://www.odoo.com/odoo/project/967/tasks/4377720) task-4377720
Shopfloor users can now keep work order steps expanded after completing actions instead of having them automatically collapse. This gives operators better control over their view and helps maintain a smoother workflow during manufacturing tasks.
Original PR description
In This Commit: ------------------------ - Prevent steps from folding back automatically after any action, allowing users to keep steps unfolded as needed. - This improvement ensures a smoother workflow and providing users with better control over their view. task-4387836
Internal users with edit permissions can now unlock documents when appropriate, while users without access will not see the unlock option. Locked documents also better restrict actions like renaming, moving, deleting, version management, duplication, PDF splitting or merging, and detail editing, helping preserve document control.
Original PR description
- This PR enables internal users to unlock documents when the user_permission is set to `edit`. - We also removed the is_locked because the document is locked for all the users - Unlock button will not be there if the user lacks the unlock access. - One should not be able to see the following actions `rename`, `move or delete`, `manage version`, `duplicate`, `merge or split pdf` when the document is locked. - One should not able to edit details of the documents when the document is locked. Task-4273020
Demo records for rental and subscription products now use clearer, more polished images. This makes sample databases look more realistic and helps sales teams better understand how these apps can be presented to customers.
Original PR description
task-4717155 part-of-task-4252024 community: - https://github.com/odoo/odoo/pull/206246
Resolved issues and error corrections
This change fixes an automated test related to disallowed fleet expenses after a Runbot failure. It helps keep the accounting and fleet expense checks reliable without changing day-to-day user functionality.
Original PR description
Runbot error build 163135
Date fields in Sign documents now show a placeholder that follows the company's configured language and regional date format. This prevents confusion for users preparing signature requests across different locations.
Original PR description
Before this commit, When adding a date sign item, the date format in the placeholder might mismatch the company's location date format since it is a static value. After this commit, the placeholder value is dynamic, it is computed initially from the company lang date_format. task-id: 4607440
A small naming issue was fixed in the Indian GST reporting workflow so the system can correctly recognize the field update behavior for tax units. This improves reliability and maintainability without changing the user-facing reporting process.
Original PR description
This **PR** rectifies the incorrect name on onchange method of tax_unit_id. This will help to improve the visibility of this method.
Code cleanup and technical improvements
The preparation display used by Point of Sale has been moved into the enterprise POS module and its internal orderline status tracking has been redesigned. This keeps the feature aligned with enterprise POS installations, simplifies unused components, and should make preparation display behavior easier to maintain going forward.
Original PR description
- The pos_preparation_display has been moved to pos_enterprise since it is installed if point_of_sale is installed in an enterprise environement. - The preparation order_stage model is rename in pos_prep_state and is now specific to an preparation orderline and not order anymore. The done field is now infer by checking if the state is in the last stage and todo false. The todo field has been moved to the state model since it is different per orderline per preparation display. - Related models is now introduced in the preparation display. - The logic in the preparation display front end is mainly done using the states of the preparation orderlines. - pos_hr_preparation_display has been removed since it's not used anymore. Related: odoo/odoo#201170
Miscellaneous changes
`_test_send_invoice_and_credit_note` and `_test_send_invoiced_stock_moves` try to create sale orders, but don't check that the group is set on the user. https://runbot.odoo.com/odoo/error/163637 Forward-Port-Of: odoo/enterprise#83691
Original PR description
`_test_send_invoice_and_credit_note` and `_test_send_invoiced_stock_moves` try to create sale orders, but don't check that the group is set on the user. https://runbot.odoo.com/odoo/error/163637 Forward-Port-Of: odoo/enterprise#83691
Followup to #83427 as I missed a second issue in the test: `action_validate` can only be performed by a time off officer. So set that on the current user. Also `self.Requests.env.user` is the same as `self.env.user` so don't bother with the unnecessary indirection. https://runbot.odoo.com/odoo/error/164047 Forward-Port-Of: odoo/enterprise#83579
Original PR description
Followup to #83427 as I missed a second issue in the test: `action_validate` can only be performed by a time off officer. So set that on the current user. Also `self.Requests.env.user` is the same as `self.env.user` so don't bother with the unnecessary indirection. https://runbot.odoo.com/odoo/error/164047 Forward-Port-Of: odoo/enterprise#83579
These tests create sale orders, but `self.env.user` does not necessarily have the right to create one by default. https://runbot.odoo.com/odoo/error/163635 Forward-Port-Of: odoo/enterprise#83672
Original PR description
These tests create sale orders, but `self.env.user` does not necessarily have the right to create one by default. https://runbot.odoo.com/odoo/error/163635 Forward-Port-Of: odoo/enterprise#83672
`TestPayslipValidation.setUpClass` tries to create an `hr.leave.type` but that requires hr admin access. So add that. Issue likely became visible from the removal of demo data, though it only popped up on April 1st instead of March 27th or whenever the demo data change was merged. https://runbot.odoo.com/odoo/error/162257 Forward-Port-Of: odoo/enterprise#83665
Original PR description
`TestPayslipValidation.setUpClass` tries to create an `hr.leave.type` but that requires hr admin access. So add that. Issue likely became visible from the removal of demo data, though it only popped up on April 1st instead of March 27th or whenever the demo data change was merged. https://runbot.odoo.com/odoo/error/162257 Forward-Port-Of: odoo/enterprise#83665
to reproduce: ============= - with employee having attendace houre based contract - set in attendace settigns that overtime should be approved by manager - create attendace for this employee with overtime pending for approval - create payslip for this employee -> the overtime is included in the payslip even if it is not approved Problem: ======== unapproved overtimes are not filtred while computing payslip lines Solution: ========= - add a filter to exclude unapproved overtimes
Original PR description
to reproduce: ============= - with employee having attendace houre based contract - set in attendace settigns that overtime should be approved by manager - create attendace for this employee with overtime pending for approval - create payslip for this employee -> the overtime is included in the payslip even if it is not approved Problem: ======== unapproved overtimes are not filtred while computing payslip lines Solution: ========= - add a filter to exclude unapproved overtimes in payslip line computation opw-4610454 Forward-Port-Of: odoo/enterprise#83449
The percentage sign is missing on the tax line in the invoice report opw-4661577 Forward-Port-Of: odoo/enterprise#83596 Forward-Port-Of: odoo/enterprise#83497
Original PR description
The percentage sign is missing on the tax line in the invoice report opw-4661577 Forward-Port-Of: odoo/enterprise#83596 Forward-Port-Of: odoo/enterprise#83497
In [1] we added a compute on wa_account_id in stead of a default to allow for a smarter default. We forgot to mark the field readonly in the process. This prevents the import of existing templates, or of templates from different accounts. task-4734669 Correction for: task-4369979 [1]: 7a593a4aa5040998dc12468dec12dca62f573030 Forward-Port-Of: odoo/enterprise#83562
Original PR description
In [1] we added a compute on wa_account_id in stead of a default to allow for a smarter default. We forgot to mark the field readonly in the process. This prevents the import of existing templates, or of templates from different accounts. task-4734669 Correction for: task-4369979 [1]: 7a593a4aa5040998dc12468dec12dca62f573030 Forward-Port-Of: odoo/enterprise#83562
Revert odoo/enterprise#81587 because errors are triggered on dry-run. Also see discussion here: ref: https://github.com/odoo/enterprise/pull/82900#issuecomment-2800848343 Forward-Port-Of: odoo/enterprise#83422 Forward-Port-Of: odoo/enterprise#83391
Original PR description
Revert odoo/enterprise#81587 because errors are triggered on dry-run. Also see discussion here: ref: https://github.com/odoo/enterprise/pull/82900#issuecomment-2800848343 Forward-Port-Of: odoo/enterprise#83422 Forward-Port-Of: odoo/enterprise#83391
19 changes
Resolved issues and error corrections
Point of Sale sessions connected to an IoT box no longer show a brief loading icon every few seconds while checking device status. This makes the checkout screen feel smoother and less distracting for staff during daily operations.
Original PR description
Before this commit, when using a POS with an IoT box connected, there would be a brief loading icon flickering in the top right every 5 seconds. This is due to the call to get the latest status of the IoT devices. After this commit, the flickering is gone due to fetching the device status using the ORM service instead of the POS data service. task-4570905
This fix prevents an inter-company sales and purchase workflow from failing when a user lacks access to lot or serial number fields. It helps users complete related stock operations without needing unnecessary permissions.
Original PR description
`(stock.picking).move_ids_without_package.lot_ids` is gated on `stock.group_production_lot`, if the user doesn't have this group, the field is unavailable and trying to set it via the form fails. https://runbot.odoo.com/odoo/error/163100
Approving an employee leave no longer fails when another overlapping leave has already been refused. The planning holidays workflow now ignores refused leave records in this check, preventing an error and allowing valid approvals to proceed.
Original PR description
Currently, a traceback is occurring when trying to approve a leave having the same time off with the refused state of another leave. <b>To reproduce this issue:</b> 1) Install planning_holidays…
Currently, a traceback is occurring when trying to approve a leave having the same time off with the refused state of another leave. <b>To reproduce this issue:</b> 1) Install planning_holidays without demo 2) Enable flexible hours for the working schedules of an employee 3) Create two time-offs for an employee with the same date and time 4) Refuse the first one and try to approve the second one <b>Issue:-</b> ``` ValueError: Expected singleton: hr.leave(5, 6) ``` When there are more than one leave record with different states, leave_date will search the record based on the employee, date and time only. https://github.com/odoo/enterprise/blob/747482f34ca8210d89d81b3363ec5a8fc3a4ff6f/planning_holidays/models/resource_calendar.py#L16-L24 So indeed we get multiple records, and this leads to the above traceback when accessing values from the leave_data. <b>Solution:-</b> Make the domain of leave_data more robust by including the state containing no refused leaves. opw-4712858,4700495
Point of Sale now prevents staff from settling customer dues or taking deposits when the required pay-later payment method is unavailable. This avoids failed partial payments, stuck screens, and follow-up errors caused by an incomplete POS payment setup.
Original PR description
Partial payments in POS are buggy if there is no pay later POS payment method Steps to reproduce: 1. Navigate to Point of Sale > Configuration > Payment Methods 2. Archive the "Customer Account" payment method (which is of `type == 'pay_later'`) 3. Try to settle a partially paid invoice in POS 4. Selecting the the "Validate" button will close the order without settling and will leave the UI in a buggy state where any further interactions produce a traceback Solution: Block the user from settling dues or making deposits when no pay_later payment method is loaded. OPW-4712869 The following error dialog is shown: <img width="163" alt="Screenshot 2025-04-18 at 00 28 41" src="https://github.com/user-attachments/assets/7651c863-bc75-4486-8483-8a8ee2fed5db" />
The payroll test setup now has the required HR administrator access to create leave types during validation checks. This prevents internal automated tests from failing after demo data changes, improving reliability without changing user-facing payroll behavior.
Original PR description
`TestPayslipValidation.setUpClass` tries to create an `hr.leave.type` but that requires hr admin access. So add that. Issue likely became visible from the removal of demo data, though it only popped up on April 1st instead of March 27th or whenever the demo data change was merged. https://runbot.odoo.com/odoo/error/162257
Fixed an issue where postpaid subscriptions with note or non-recurring lines could be treated like prepaid subscriptions. This prevented contracts from being checked every day unnecessarily and helps keep the next invoice date aligned with the subscription billing cycle.
Original PR description
Before thos commit, the next invoice date was updated at post invoice based on the order line properties. pre paid lines are will use the last deferred end date of the linked account move lines and post paid line simply increment the next invoice date. Before this commit, the post paid detection was faulty: we checked that all line were postpaid but if line notes or non recurring lines existed, they would not have the postpaid property. As a result, the next invoice date would be incremented with the prepaid condition. As a result, the next invoice date would only be incremented by one day and the cron would run on these contracts every day. opw-4618947 opw-4668741 opw-4686930
This fix makes an automated test for rental period selection on the website more stable. It reduces random test failures, helping teams trust release checks without changing the customer-facing rental flow.
Original PR description
In this commit we fix the website_sale_renting_select_wrong_period tour that can cause undeterministic errors.
The UrbanPiper username setting was renamed internally so it no longer shares the same label as another localization setting. This prevents warning messages when the module loads, with no expected change to how users configure or use the feature.
Original PR description
The field `res.config.settings.urbanpiper_username` has the same label `Username` as the field [`res.config.settings.l10n_co_edi_username`](https://github.com/odoo/enterprise/blob/e0307b19d85f9cc3dba883f3fe8eab2a4cb23ebd/l10n_co_edi/models/res_config_settings.py#L8-L9) from module `l10n_co_edi`. Having multiple fields on the same model with the same label generates warnings when loading the module. The label is already changed in [`saas-18.1`](https://github.com/odoo/enterprise/blob/e0307b19d85f9cc3dba883f3fe8eab2a4cb23ebd/pos_urban_piper/models/res_config_settings.py#L11), and the [view](https://github.com/odoo/enterprise/blob/3f828af20e7936e6730d2f94b79aef755bd4b359/pos_urban_piper/views/res_config_settings_views.xml#L11) displaying the field uses an explicit label as well.
Fixed a display issue where switch buttons in the Documents app could show incorrect padding after using the activity view switch. This improves visual alignment and makes the interface look more consistent for users.
Original PR description
This PR fixes an issue where the switch buttons in the documents module had incorrect padding when clicking on the activity switch view button.This fix ensures proper spacing and alignment across the interface. Task-4680512
Miscellaneous changes
### Steps to reproduce: - In the settings enable "Rental transfers" - Create a storable product that can be rented put 100 units in stock. - Create a rental order for 10 units of that product planed for the period : [today + 2 days, today + 3 days] and confirm it. - Create a rental order for 10 units of that product planed for the period : [today + 1 days, today + 2 days] and confirm it. - Look at the forecast rentable quantity. #### > It should be 90 but it is 100. ### Cause of the i
Original PR description
### Steps to reproduce: - In the settings enable "Rental transfers" - Create a storable product that can be rented put 100 units in stock. - Create a rental order for 10 units of that product planed…
### Steps to reproduce: - In the settings enable "Rental transfers" - Create a storable product that can be rented put 100 units in stock. - Create a rental order for 10 units of that product planed for the period : [today + 2 days, today + 3 days] and confirm it. - Create a rental order for 10 units of that product planed for the period : [today + 1 days, today + 2 days] and confirm it. - Look at the forecast rentable quantity. #### > It should be 90 but it is 100. ### Cause of the issue: Since c18a7d2dc36d33134c5bdb1569865bd554e04130, the rentable forecast for future dates ignores the `rented_qty_during_period` if the setting "Rental transfers" is enabled. This happens because that rented quantity during period is supposed to be absorbed by the stock forecast: https://github.com/odoo/enterprise/blob/8ea5f4f9a0a907c57844c6274688171193f6a904/sale_stock_renting/models/sale_order_line.py#L132-L134 However, the stock forecast of the 'virtual_available' relies solely on deliveries and receipt happening prior to the start of the renting period. Therefore the rental orders that are planned to start during the renting period should still contribute to the `rented_qty_during_period` in that use case. opw-4552760 Forward-Port-Of: odoo/enterprise#83262 Forward-Port-Of: odoo/enterprise#82172
`_test_send_invoice_and_credit_note` and `_test_send_invoiced_stock_moves` try to create sale orders, but don't check that the group is set on the user. https://runbot.odoo.com/odoo/error/163637 Forward-Port-Of: odoo/enterprise#83691
Original PR description
`_test_send_invoice_and_credit_note` and `_test_send_invoiced_stock_moves` try to create sale orders, but don't check that the group is set on the user. https://runbot.odoo.com/odoo/error/163637 Forward-Port-Of: odoo/enterprise#83691
In this PR we : -Allow manual input of source tax adjustments -Improve transmission error messages -Add missing translations -Reintroduce work information and skills tab Forward-Port-Of: odoo/enterprise#83381 Forward-Port-Of: odoo/enterprise#81754
Original PR description
In this PR we : -Allow manual input of source tax adjustments -Improve transmission error messages -Add missing translations -Reintroduce work information and skills tab Forward-Port-Of: odoo/enterprise#83381 Forward-Port-Of: odoo/enterprise#81754
Followup to #83427 as I missed a second issue in the test: `action_validate` can only be performed by a time off officer. So set that on the current user. Also `self.Requests.env.user` is the same as `self.env.user` so don't bother with the unnecessary indirection. https://runbot.odoo.com/odoo/error/164047 Forward-Port-Of: odoo/enterprise#83579
Original PR description
Followup to #83427 as I missed a second issue in the test: `action_validate` can only be performed by a time off officer. So set that on the current user. Also `self.Requests.env.user` is the same as `self.env.user` so don't bother with the unnecessary indirection. https://runbot.odoo.com/odoo/error/164047 Forward-Port-Of: odoo/enterprise#83579
This commit slightly adapts a Gantt test to accommodate adjustments made in Chrome 135 to some rounding done during painting. To do so, and to avoid a purely arbitrary value, the related assert is modified to check the visibility of the "today" column and that there is an actual scroll applied instead of an arbitrary scroll of 762px. References (not exhaustive): - https://chromium.googlesource.com/chromium/src.git/+/a629cc4312019dfa43b686bdb2d9418a625f9bc6 - https://chromium.googlesource.co
Original PR description
This commit slightly adapts a Gantt test to accommodate adjustments made in Chrome 135 to some rounding done during painting. To do so, and to avoid a purely arbitrary value, the related assert is modified to check the visibility of the "today" column and that there is an actual scroll applied instead of an arbitrary scroll of 762px. References (not exhaustive): - https://chromium.googlesource.com/chromium/src.git/+/a629cc4312019dfa43b686bdb2d9418a625f9bc6 - https://chromium.googlesource.com/chromium/src.git/+/2efdf2a6f8e184ece09acca4677d1ce9eb7a43ea - https://chromium.googlesource.com/chromium/src.git/+/ce7a5f6b60b175c780fb39e2f751d82abb8b011b Forward-Port-Of: odoo/enterprise#83587
This PR follows the new format of the pairing code introduced in the internal PR https://github.com/odoo/internal/pull/3462/ It removes the spaces around the introduced pairing code and makes all leters uppercase before sending them to odoo iot proxy Forward-Port-Of: odoo/enterprise#82905
Original PR description
This PR follows the new format of the pairing code introduced in the internal PR https://github.com/odoo/internal/pull/3462/ It removes the spaces around the introduced pairing code and makes all leters uppercase before sending them to odoo iot proxy Forward-Port-Of: odoo/enterprise#82905
In [1] we added a compute on wa_account_id in stead of a default to allow for a smarter default. We forgot to mark the field readonly in the process. This prevents the import of existing templates, or of templates from different accounts. task-4734669 Correction for: task-4369979 [1]: 7a593a4aa5040998dc12468dec12dca62f573030 Forward-Port-Of: odoo/enterprise#83562
Original PR description
In [1] we added a compute on wa_account_id in stead of a default to allow for a smarter default. We forgot to mark the field readonly in the process. This prevents the import of existing templates, or of templates from different accounts. task-4734669 Correction for: task-4369979 [1]: 7a593a4aa5040998dc12468dec12dca62f573030 Forward-Port-Of: odoo/enterprise#83562
Forward-Port-Of: odoo/enterprise#83524
Original PR description
Forward-Port-Of: odoo/enterprise#83524
This PR fixes two behavior on the lipe xml export in Italy. --- The first one linked to this fix: https://github.com/odoo/enterprise/commit/7323435468c8db15cd5643f7d6ecf5928ab2f3dc . It makes sure the options are gathered the right way depending on whether we export the xml from the report or from the closing entry. --- The second one makes sure the closing entry move is posted when the xml export is done pressing the "Post" button on it. --- no-task Forward-Port-Of: odoo/ente
Original PR description
This PR fixes two behavior on the lipe xml export in Italy. --- The first one linked to this fix: https://github.com/odoo/enterprise/commit/7323435468c8db15cd5643f7d6ecf5928ab2f3dc . It makes sure the options are gathered the right way depending on whether we export the xml from the report or from the closing entry. --- The second one makes sure the closing entry move is posted when the xml export is done pressing the "Post" button on it. --- no-task Forward-Port-Of: odoo/enterprise#83503
The percentage sign is missing on the tax line in the invoice report opw-4661577 Forward-Port-Of: odoo/enterprise#83497
Original PR description
The percentage sign is missing on the tax line in the invoice report opw-4661577 Forward-Port-Of: odoo/enterprise#83497