Tuesday, February 4, 2025
10 changes · master
Enhancements to existing features
Tickets created from chatbot conversations now show the chat history in a clearer format and include a direct shortcut back to the original discussion. This helps support teams understand customer requests faster and continue the conversation with less manual searching.
Original PR description
*: website_helpdesk_livechat. This PR aims to improve live chat consultations for tickets created by a chatbot. Specifically, it enhances the formatting of the ticket description to make the conversation easier to read, introduces a smart button to redirect users to the discussion channel where the ticket originated and set the ticket name according to the user request. task-4432728 community: https://github.com/odoo/odoo/pull/191813
Recruiters can now post job listings to job boards more smoothly, including jobs that have not yet been published. The update reduces interruptions during posting by requiring key information upfront and makes related recruitment modules easier to understand, while also fixing a missing job post icon in Firefox.
Contract template management is moved into the core employee contract area so templates are available where users expect them. The update also improves related hiring and payroll salary screens, making contract setup more consistent and easier to navigate.
Original PR description
Contract template should already exist in hr_contract and some other UX improvements. Task: 4320233
The disallowed expenses reporting now supports cases where businesses can deduct more than 100% of an expense, such as Belgium's enhanced deduction for eInvoicing costs. Reports and fleet-related expense settings now show both the disallowed and actually deductible amounts, helping finance teams apply the correct tax treatment.
Original PR description
Our Disallowed Expense module does not allow for deductibility of >100%. We have cases where it's needed, for example in Belgium you are allowed to deduct 120% of your amounts expensed for eInvoicing. For this we need to inverse the percentage to the part that is allowed in the expenses, so that we can take it into account in the report, and add another column showing the amounts that can actually be deduced. task-id 4421297 Upgrade PR: https://github.com/odoo/upgrade/pull/6971, https://github.com/odoo/upgrade/pull/7807 Documentation PR: https://github.com/odoo/documentation/pull/11634
Appraisal goals can now be linked to more than one employee, making shared objectives easier to track in performance reviews. The appraisal screens and demo data were updated to display these multi-employee goals clearly, including small visual fixes to status ribbons.
Original PR description
- change the field to Many2Many - edit the view and demo data to match the new type Task: 4391198
The appraisal survey experience now includes better demo data and an easier way to request 360 Feedback directly from the survey list. This helps users find and launch feedback requests more reliably, while ensuring employee matching works even if email details have changed.
Original PR description
- Add demo data to make 360 Feedback entry to be shown - fix email field in the demo data to match the context matching - Add button to ask feedback in the surveys list view Task: 4373438
The Planning employee avatar card layout has been improved to better present details such as skills and roles. Clearer spacing and content separation make the card easier to read and less visually crowded for users reviewing staff information.
Original PR description
This PR reviews the layout of the avatar card in order to match all the use cases. - requires https://github.com/odoo/odoo/pull/188068 The employee avatar card recently received an update aiming to display skills and roles within its content. While this added extra information and value to the component, its layout wasn't really meant to contain that much information, which led to a crowded visual result. With this PR, we review the hierarchy of the card by adding clear separations to its content and reviewing the use of white space. | Master | This PR | |--------|--------| |  | <img width="402" alt="image" src="https://github.com/user-attachments/assets/6f4f7d6b-6e72-4cf6-b88f-e8e2e977e8b9"> | task-3810438
Payroll users can now see each employee's reference number directly in employee, contract, payslip, attendance, leave, and salary report lists. The label has also been standardized as "Employee Reference," making it easier to identify employees consistently across payroll screens.
Original PR description
- add the `registration_number` field to the employee, contract, and payslip list views - change the field label to `Employee Reference` to be consistant Task: 4491186
Payroll work entry type records are now protected from being overwritten during system migrations or upgrades, helping keep configured payroll behavior stable. The payroll setup data was also reorganized into smaller files to make future maintenance safer and clearer.
Original PR description
Work entry type data should not be updatable as it shoud not be erased at each migration/upgrade. This commits fixes this by changing all work entry type data to noupdate true. The hr_payroll data file has also been split into multiple files to follow the coding guidelines. task-4479965
Resolved issues and error corrections
The helpdesk stock ticket list no longer loads an unused product suitability field. This removes unnecessary background processing and should make ticket lists faster, especially when many tickets are shown.
Original PR description
Following odoo/enterprise@07954ea8b5bccd185dc4639c5e75d5dbab8b5499, `product_id` was removed from the list view. Therefor there is no more reason to have `suitable_product_ids` in the list view also, as the only reason it was present was because `product_id` had a domain that was depending on the `suitable_product_ids`. This should also lead to a significant performance improvement of the list view, as `suitable_product_ids` doesn't scale well with a larger collection of tickets than `1` which was the expected usage in the form view.