Monday, July 1, 2024
16 changes
2 changes
Resolved issues and error corrections
This fixes an error that could stop Adyen or Viva Wallet payment terminals from working in Point of Sale. Businesses using these terminals can process payments more reliably after the recent system change in version 17.2.
Original PR description
Setting a adyen/viva-wallet terminal PoS setup and using it would cause the JS traceback: `TypeError: Cannot read properties of undefined (reading 'getPendingPaymentLine')` This error happen starting 17.2 due to the change of patched class PosBus (17.1) -> PosStore (17.2) see: https://github.com/odoo/odoo/pull/136621 opw-3977273
This fix ensures the French accounting module is automatically installed when a company is set to France and the Invoicing or Accounting app is installed. It prevents missing localization features, helping French companies get the correct accounting setup without manual intervention.
Original PR description
To reproduce the bug, follow these instructions: - Change the company localization to France. - Install the Invoicing or Accounting app. - Check if the l10n_fr_account module is auto-installed. The module won't get installed because the auto-install dependencies are ['account', 'l10n_fr'], and l10n_fr does not have an auto-install dependency, so the l10n_fr_account module won't get installed. OPW-3898999
6 changes
Enhancements to existing features
This update improves how employee billing rate values are tracked in the timesheet sales process. It helps businesses keep a clearer record of billing rate changes, supporting more accurate project costing and customer billing reviews.
Original PR description
temp task-3922896
8 changes
Resolved issues and error corrections
Fixed an issue where employee searches in the timesheet forecast view were displaying incorrect results. When searching for a specific employee name, non-matching employees were still appearing in the list. The fix corrects the search filter logic to properly exclude employees that don't match the search criteria.
Original PR description
Steps to reproduce: - install timesheet module - install project_timesheet_forecast bridge module - open timesheets - click on all timesheets - search an employee name Issue: - employees that are not matching this search are still being displayed Cause: - the conditions that are in domain causes this issue Solution: - if we gave the condition in domain ,that the filter is based on related search then the issue will be solved task-3653034
The rental calendar now displays orders according to their actual rental start and return dates instead of the next planned activity date. This makes it easier for users to understand rental schedules and manage equipment or product availability at a glance.
Original PR description
Before the commit: The calendar view of the rental was based on the next activity date (which is expected for sales and subscriptions). Customers expect to see the orders based on the rental period. There was no customized calendar view dedicated to rental orders. After the commit: Now the rental periods are shown in the calendar view which is based on the rental start date and rental return date. The new view is extended from the calendar view of the sale order and overridden necessary attributes to display the rental period task-3893588
Payroll teams can now start creating a payslip directly from an employee contract, even when no payslip already exists for that contract. The payslip opens with the employee and contract already filled in, saving time and reducing manual entry for payroll officers.
Original PR description
Before this commit, payroll manager was not able to generate payslip directly from employee contract form if there is not any payslip present for contract. This commit brings, the direct payslip generation from employee contract form by stat button with payroll officer rights. The employee and contract will be preselected on payslip from contract. task-3922123
Employee bank account trust actions are now handled directly from the employee form, reducing clutter in employee action menus. Payroll warnings now point users to the relevant bank accounts and respect the selected companies, making follow-up clearer and more accurate.
Original PR description
The employee action menu is becoming more and more overloaded. This PR aims to address the issue. It also aims to adjust the warnings in the payroll app. This PR: 1. removes Trust Bank Account option from the action menu in employee form and list views and gives the ability to trust/untrust bank accounts in the employee form view. 2. Adds a menu item in the employees app to access the bank accounts of employees. 3. Makes untrusted bank accounts warning lead to bank accounts instead of employees. 4. Makes the warnings in the payroll app depend on the selected companies. task-3916836 Co-authored-by: Rob Coekaerts <roco@odoo.com>
Payroll batches can now be marked as paid even when some payslips in the batch were already paid. This streamlines payroll processing by updating only the remaining unpaid payslips and avoiding unnecessary manual work.
Original PR description
This PR improves the efficiency of processing group payslips in the payroll module. - Allows moving the batch to `paid` status while only affecting the unpaid payslips, even if some payslips in the batch are already paid. task-3815871
Asset users can now define a non-depreciable portion as either an amount or a percentage, including default percentages on asset models. This helps keep asset residual value calculations consistent and warns users when entered values are outside valid limits.
Original PR description
- This commit will allow the user to enter Not Depreciable Value of an asset based on the selection of Amount or Percentage. - Users can also add Not Depreciable Value (in percentage) in the Asset Model form. - When a user selects any asset model in asset form, Not Depreciable Value (in percentage) will be automatically filled based on the selected model. - If Not Depreciable Value (in amount) is greater than Original Value or Not Depreciable Value (in percentage) is not between 0 to 100 for an asset then it will show the warning message. **task**-3669618
This fix prevents the helpdesk ticket creation command from appearing in chat when users don't have access to any helpdesk teams with chat enabled. Previously, users could trigger the command and create tickets with no team assigned, making them unusable. Now the command only appears when users have proper access to at least one active helpdesk team.
Original PR description
This commit's purpose is to disable the helpdesk ticket creation command when there are no teams available for the current connected user. Currently, using this command this way will create a new…
This commit's purpose is to disable the helpdesk ticket creation command when there are no teams available for the current connected user. Currently, using this command this way will create a new ticket without any team attached, rendering it useless. step to reproduce: - install helpdesk application - open helpdesk - open confifuration menu, select helpdesk team - select 'customer care' - activate the livechat option and saves - leave helpdesk - change from the current active company to any other company that doesn't have any helpdesk team with the livechat feature enabled - open the discuss app and select the 'general' discussion - type /helpdesk your_ticket a new ticket will be created without any team linked to it. source of the issue: when a team has the livechat option enable, the command is added to the livechat regardless of the connected user's access right to the team. solution: Only add the command to the list of livechat command if the user has access to at least one team with the livechat feature enable. affected version : 15.0 - master task - 3631682 https://www.odoo.com/web#id=3631682&menu_id=4720&cids=1&action=333&active_id=4105&model=project.task&view_type=form Forward-Port-Of: odoo/enterprise#64765 Forward-Port-Of: odoo/enterprise#53510
This fix adds a helpful warning message when users try to sign invoices for contacts that have a Mexican tax ID (RFC) but no country configured. Previously, users would see no alert even though the invoice would be signed with a generic placeholder tax ID instead of the correct one, creating confusion. Now they'll be notified during the send and print process so they can fix the contact information.
Original PR description
When a contact is created with an RFC (VAT number) but no country configured, signing an invoice for that contact results in the invoice being signed correctly. However, the PDF shows the partner's RFC, while the XML file shows the generic RFC (XAXX01010101). This discrepancy misleads users into believing their setup is correct, as no error or alert is provided. This commit introduces a non-blocking warning message in the 'Send and Print' wizard for cases where the contact's country is missing. opw-3891896
This fix resolves an issue where users encountered validation errors when creating timesheets from tickets if their active company differed from the project's company. The fix ensures the correct company information is properly set when creating timesheets, allowing users to work seamlessly across multiple company configurations in the helpdesk billing workflow.
Original PR description
When creating a timesheet from the ticket view form, an access error is raised if the active company is different from the company of its project. Step to reproduce: - install helpdesk_sale_timesheet…
When creating a timesheet from the ticket view form, an access error is raised if the active company is different from the company of its project. Step to reproduce: - install helpdesk_sale_timesheet - open helpdek - open configuration menu -> helpdesk teams - select a team with the visibility set on 'invited portal users' - enable the 'billing' feature, and add a project on this team - select as active company any company other than the one set on the project selected before - select an existing ticket, or create a new one on the team - try creating a new timesheet Validation error is raised Source of the issue: If no company_id is given in the vals_list, the default company_id used by analytic line model is the active company. The issue is not present on task, because the key 'company_id' is correctly set in the '_timesheet_preprocess' method. This method is overwritten in the helpdesk_sale module and the updates done in it prevent the correct setting of the 'company_id' later on. Solution: Ensure that the 'company_id' key is present and consistent when creating a new timesheet from the ticket form view. version: 16.0 - master task - 3581941 Forward-Port-Of: odoo/enterprise#50150
This update fixes a display issue in the Knowledge app where embedded views (like charts or tables) were overlapping and hiding text when placed in multi-column layouts. The fix ensures these embedded elements stay properly contained within their assigned columns, improving the readability and usability of Knowledge documents with complex layouts.
Original PR description
This commit fixes an issue withthe embedded views inside the columns block in the editor. The embedded views were overlapping the columns on their right meaning that some text could be hidden behind them. To fix this a new rule is added to these blocks so that when they are inside a column block that is not the last one we remove the negative margin-right. This way we preserve their style when inside the right-most column. task-3901864
This fix resolves an issue where document attachments were not being properly exported when using the German Datev export feature with the "Datev + ATCH (zip)" option from the general ledger. The export now correctly includes the document identifier (GUID) in the designated column for documents that have attachments, ensuring complete and accurate financial record exports.
Original PR description
When a document has an attachment, the export done through the general ledger and "Datev + ATCH (zip)" should have a column filled with the guid of the document, which is not the case currently. To solve it, use the helper to get the attachments opw-3984450
This fix corrects a bug in the Accounting Reports module where the Account Coverage Report was incorrectly displaying linked accounts instead of unused accounts. The report now properly shows which accounts are not being used in your accounting setup, helping you maintain a cleaner chart of accounts.
Original PR description
The coverage reports do not print the right account ids when searching for the ones that are not used. ### Steps to reproduce: - Install the 'l10n_de' module and switch to a German company - Go in Accounting > Configuration > Management > Accounting Reports - Go in the German Profit and Loss report - Click on the button 'Accounts Coverage Report' - In the downloaded report the yellow lines should not appear as they are linked ### Cause: When searching for the ids that are not linked, the code actually only look up the ones that are linked to an account. ### Solution: Fix the condition on the ids. opw-3993835
The 30% Exemption field was appearing on all employee contracts, but it should only be visible for Dutch contracts. This update restricts the field visibility to Dutch contracts only, ensuring the correct payroll information is displayed based on employee location.
Original PR description
30% Exemption field shows on all contracts although it should only show on dutch employees contracts. This change restricts the 30% Exemption to only show on dutch contracts. task-3946599