Monday, December 4, 2023
11 changes
Resolved issues and error corrections
Fixed display issues with the timesheet timer on tablet-sized screens where the layout was breaking. The timer now displays properly without shifting content, and buttons remain readable on smaller screens. This improves the user experience when tracking time on tablets and other medium-sized devices.
Original PR description
This commit adapts the timesheet_timer_header to better handle its responsiveness. On tablet size screen (mg to lg) the view was breaking. This commit adds a text-nowrap on the stop button and adapt the size of the inputs next to the timer. The timer was also moving the content since it's not a monospace font, a .SCSS file is created to add `tabular-nums` to manage the font size. task-3580643 Community: https://github.com/odoo/odoo/pull/140750
A technical update was made to the Field Service Management date widget to ensure it correctly targets the right element after a recent system change. This fix restores proper functionality for date selection in field service operations, preventing potential issues with scheduling and task management.
Original PR description
Since commit 8c8dfb07f9dcf1612100996a0a224b556da8c508 in community, the xpath was no longer targeting the correct element. Community PR https://github.com/odoo/odoo/pull/132215 task-3463329 part of task-3326263 Forward-Port-Of: odoo/enterprise#51081 Forward-Port-Of: odoo/enterprise#51011
This fix resolves an issue where manufacturing orders created without work orders were showing zero average cost in production reports. The problem occurred because employee cost calculations were returning null values when no work orders existed, which broke downstream cost computations. This ensures accurate cost reporting for all manufacturing orders regardless of whether they include work orders.
Original PR description
When there are no work orders on a manufacturing order, the employee cost is `null`, breaking the computation of other fields. ## Steps to reproduce: 1. Install `mrp_workorder_hr_account` 2. Make a MO without work orders and validate 3. Go to Manufacturing > Reporting > Production Analysis 4. Open the pivot view and search for the MO 5. 'Average Total Cost / Unit' is 0 opw-3600343 Forward-Port-Of: odoo/enterprise#51789 Forward-Port-Of: odoo/enterprise#51303
This update fixes how private tasks display their planned dates in project views and removes duplicate rating metrics from helpdesk reporting. The changes ensure that private tasks show planned dates correctly in the gantt view, and simplifies the SLA Status Analysis reporting by removing the redundant "Average Rating" option when "Rating (/5)" is already available.
Original PR description
… is private
Before this commit
-> project.task gantt view > the planned date should not be visible when the task is private
-> In reporting after entering into SLA Status Analysis, in the measures button
we'll be having both Average Rating and Rating (/5). So we have to disable
Average Rating from the Measures drop down menu
After this commit
-> project.task gantt view > the planned date should be set by default even if the task is private
-> I have disabled the Average Rating field from the Measures drop down men
task-3474438
Forward-Port-Of: odoo/enterprise#46377This update improves the shipping information sent to Sendcloud by including the commercial company name for both the sender and receiver. This ensures that shipping labels and delivery information display the correct business entity names, providing better accuracy and professionalism in shipping communications.
Original PR description
This commit adds commercial company name for the receiver and sender partners to the shipping request to sendcloud. opw-3591211 Forward-Port-Of: odoo/enterprise#51676
Fixed a bug where changes made to document fields in the inspector panel were not being saved when the document wasn't selected in the main view. The system now automatically saves inspector changes even when documents are being previewed without selection, ensuring users don't lose their edits.
Original PR description
Bug === When we open the document inspector without selecting the record, if we change some field values, those changes are not saved. The reason for that is that the web client expects the record to be selected in the kanban view / list view if we make a change, which is not always the case in Documents. Task-3586696 Forward-Port-Of: odoo/enterprise#50516
Portal users creating helpdesk tickets via email now receive confirmation emails from the ticket template, improving their experience. Previously, these emails were not sent because the system assumed users don't need notifications for their own actions—but portal users benefit from this feedback since they're less familiar with the system.
Original PR description
Since 7b338e0, Odoo does not send emails if you change the stage of your own tickets (or create them), the rationale being that you don't need to be informed of your own actions. But portal users are not familiar with Odoo so we want to always send them an email if they create a ticket. steps to reproduce: - create a portal user - create an helpdesk team with an alias - set a template on the initial stage - send an email from the portal user email address to that alias before this commit: - the ticket is created but no email is send from the mail template after this commit: - an email from the mail template is sent if a portal user creates a ticket using the email alias opw-3555716 Forward-Port-Of: odoo/enterprise#51992
Field Service users in single-company setups can now create quotations directly from tasks without encountering errors. The fix automatically sets the company field to the current company, matching the behavior in multi-company environments and removing the need for manual configuration.
Original PR description
Issue: In a mono-company setup, users trying to create a quotation from a task face an error message because the mandatory 'company' field in the 'other info' tab is not visible, unlike in multi-company setups. Steps to Reproduce: 1. Install the Field Service app. 2. Activate 'Extra Quotations' in the Field Service general settings. 3. Enable 'Extra Quotation' in the settings of the relevant project. 4. Try creating a quotation from a task in a mono-company environment. 5. Encounter an error. Resolution: Modified the functionality so that the 'company_id' field defaults to the current company. opw-3596984 Forward-Port-Of: odoo/enterprise#51290
Fixed an issue where bank reconciliation would fail when a user with access to multiple companies tried to reconcile a bank statement. The problem occurred when a bank account with the same account number existed in different companies. The fix ensures the system correctly retrieves the bank account from the appropriate company, allowing seamless reconciliation across multi-company environments.
Original PR description
…another company - Create a bank account linked to a partner in company A. - Create a statement line with the same account_number in company B. - Open the bank reco widget using a user having access to company A and B => check_company failed when validating the statement line. Forward-Port-Of: odoo/enterprise#51923 Forward-Port-Of: odoo/enterprise#51132
The website appointment payment module was missing a required dependency declaration in its configuration file. This caused errors during system upgrades because the module tried to use features from the appointment module without it being properly installed first. Adding this dependency ensures the modules load in the correct order and prevents upgrade failures.
Original PR description
The module is dependant on `website_appointment`, but it is missing in the manifest. While upgrading, the issue happens because we try to parse the inherited `website_appointment` view But the module is not installed Since it is a direct dependency, it is better to have it in the manifest https://github.com/odoo/enterprise/blob/17.0/website_appointment_account_payment/views/appointment_templates_appointments.xml#L3
This fix corrects an accounting error where closing an asset with a non-depreciable value would incorrectly show the book value as equal to the non-depreciable amount instead of zero. This ensures accurate financial reporting when retiring assets that have residual non-depreciable value.
Original PR description
When closing an asset with a non-depreciable value, the book value is equal to the non-depreciable value instead of zero. opw-3565329 Forward-Port-Of: odoo/enterprise#51453