Monday, October 14, 2024
8 changes · 17.0
Enhancements to existing features
This update ensures that all date fields in a document are filled with the same date format when signing, rather than varying based on the user's location. The date format now depends on the company partner's language setting, providing a consistent and professional appearance across all signed documents.
Original PR description
Before this commit, it was possible to fill two date fields in two different date formats in the same document. This happened because the date format was dependent on the location of the user who is signing. After this commit, date fields will be auto-filled by a fixed date format, that format depends on the language of the company's partner. Task: 3930358
Resolved issues and error corrections
This fix prevents duplicate accounting records from being created when setting up companies with parent-subsidiary relationships. The system now loads the chart of accounts from parent companies first during initialization and migration, ensuring clean and accurate financial data structures across all localization modules.
Original PR description
In migration and init scripts, when loading the chart of accounts or parts of it, we should always start with the parent companies to avoid creating duplicate chart records
This update resolves a crash that occurred when users tried to print or export the trial balance report to Excel. The issue was caused by a recent code change that didn't properly handle certain data conditions, resulting in an error message instead of a successful export. Users can now export trial balance reports without encountering errors.
Original PR description
before this commit, on printing trial balance report in excel, raises an exception when the level is None it cannot be compared with >= and thus exception is shown: elif level >= 3: TypeError: '>=' not supported between instances of 'NoneType' and 'int'  introduced in the commit: https://github.com/odoo/enterprise/commit/9d1f27082cc2e837951a3a5c3337cc90531de04a after this commit, no error wont be shown when printing trial balance in excel Forward-Port-Of: odoo/enterprise#71846
This fix prevents helpdesk timesheets from being incorrectly merged together when tracking time on different helpdesk tickets. Previously, when users tracked time on different tickets within the same helpdesk project, the system would combine them into a single timesheet entry instead of creating separate ones. This update ensures each ticket gets its own timesheet record, improving time tracking accuracy for helpdesk teams.
Original PR description
Steps to reproduce: - Helpdesk app > Any team > : Menu > Enable 'Timesheets' setting - Timesheets app > Start timer - Set your helpdesk project and any task (Do not add a description) - Stop timer >…
Steps to reproduce: - Helpdesk app > Any team > : Menu > Enable 'Timesheets' setting - Timesheets app > Start timer - Set your helpdesk project and any task (Do not add a description) - Stop timer > Do it again with same the project and a different task - Stop timer > Time is added to previous timesheet The expected behavior would be to create a new timesheet since the task is different. The reason both timesheets are merged is that we check 'task_id' for redundance while helpdesk 'tasks' are instead recorded in the 'helpdesk_ticket_id'. Since it is forbidden for a timesheet to have both a 'task_id' and 'helpdesk_ticket_id', it is guaranteed that task_id will be False for both of our entries, leading to a merge. Similarily we can use that property since adding helpdesk_ticket_id to the domain won't change the usual behavior (the field will always be False if the project is not from Helpdesk) to add an extra condition here. Source: we have a contraint '_check_no_link_task_and_ticket' which ensures that. opw-4203678
This fix improves the default configuration for document projects by automatically setting the correct group assignment. Previously, users could easily forget to configure the proper group settings, leading to incorrect access permissions. This change reduces manual configuration errors and ensures documents are properly organized from the start.
Original PR description
It’s too easy to forget to set the right group opw-4206894 Forward-Port-Of: odoo/enterprise#70894
Fixed a system error that occurred when calculating taxes on invoices with multiple product lines using different cost centers, where the same tax applied to each line. The system now properly handles multiple tax lines for the same tax by distributing any rounding differences evenly across all affected lines, preventing calculation failures.
Original PR description
Set up Avatax environment Create an Invoice with 2 lines: - Prod A, Analytic Account A - Prod B, Analytic Account B Compute taxes Now open one of the newly added taxes On the repartition line click on the 3 dots menu, show 'Tax Closing Entry' Disable 'Tax Closing Entry' on the invoice repartition line Now go back to the invoice Compute taxes again Issue: Traceback will raise 'ValueError: Expected singleton: account.move.line(...' This occurs because, with this tax configuration, on the move we will have 2 tax lines for the same tax, as the lines needs a different analytic account and cannot be grouped together. When we compare the amount per tax we'll have a recordset and it will raise an error. A solution is to acknowledge that we might have more than 1 line and split the possible difference evenly on the tax lines opw-3976597
This fix resolves an issue where users received a CSRF error when uploading documents through the document request feature. The problem was caused by JavaScript files loading in the wrong order, preventing security tokens from being properly added. The fix reorders the file loading sequence to ensure all necessary components are available before they're needed.
Original PR description
Current behaviour: --- When you click on the "request a document" link, then upload a document, you get a CSRF error Steps to reproduce: --- 1. Install documents 2. In documents, click the arrow next to "new", then "request" 3. Add a name, and a "request to", then click "request" 4. Go to messages, copy the link in the generated email 5. Paste the link in an incognito window 6. Upload a document, CSRF error Cause of the issue: --- The js file that adds the CSRF token (documents_public_pages.js) could not be loaded due to an error caused by website_sale_renting: `TypeError: odoo.define is not a function` The mixin file was loaded before the odoo module loader. Caused by: https://github.com/odoo/enterprise/commit/93d09071a08bd5de948886729d827b1c46e907d9 Fix: --- Put js code from website_sale_renting before owl.js which is right after assets_frontend_minimal, containing module_loader.js opw-4138333
This fix resolves a problem where the real-time connection breaks when users delete and recreate a spreadsheet in different browser tabs. The system now properly checks if a spreadsheet exists before attempting to update it, preventing connection failures when working with spreadsheets.
Original PR description
Steps to reproduce: - open a first tab - create a new spreadsheet - open a second tab - from that new tab, delete the spreadsheet (send to trash, then permanently delete it from the trash) - create a new spreadsheet => update a few cells, the websocket connection is broken. Task: 4252590