Tuesday, September 26, 2023
10 changes · master
New functionality added to Odoo
Spreadsheet users can now remove duplicate rows directly from the data menu, making it easier to clean selected data without manual review. Notifications were also adjusted so messages can better control whether they stay visible or disappear automatically.
Original PR description
[IMP] remove duplicate: add the remove duplicate functionality Add a new feature in the data menu allowing to remove duplicate rows in the selection part of task 2984935 Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> [REF/IMP] notify: change behavior Currently the payload allowing to notify the user is composed of a text and a tag. The tag, when it is the same, avoids renotifying the user. We believe that it is the responsibility of the notifying element to relaunch a notification or not. So we remove this tag in this commit. Also we add in the payload a "sticky" attribute indicating if the notification should or should not clear itself after some time part of task 2984935 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now add images directly over spreadsheet cells from the interface, using files from their computer. Images are saved in Odoo and can be resized proportionally, copied, cut, pasted, reset, or deleted, making spreadsheets more flexible for visual content.
Original PR description
Description of the issue/feature this PR addresses: Add the insertion of image in spreadsheet. Desired behavior after PR is merged: Can insert an image over cells from the UI. The resize of image from a corner anchor keep his ratio. The user can choose an image from his computer. FileUploader save the image in Odoo. Can copy cut paste reset_size and delete images. Figure of image don't have border. Odoo task ID: [2955759](https://www.odoo.com/web#id=2955759&cids=1&model=project.task&view_type=form) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
This update makes employee time off dates and durations more consistent by using the requested leave dates as the main source and calculating the final duration automatically. It also improves multi-company access checks and reduces unexpected changes when company-wide days off are edited, helping HR teams manage leave more reliably.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
Chat channel changes are now sent to users through live notifications, so updates appear promptly without relying on slower refresh behavior. This improves responsiveness in Odoo Discuss and helps users see conversation changes more reliably.
Original PR description
Before this PR, channel update where not sent via bus notifications. Part of task-2821415
Recruitment can now ignore configured email addresses when creating applicants from incoming emails. This helps prevent unwanted provider or automated email addresses from being copied into applicant and contact records, while keeping valid applicant emails synchronized for communication.
Original PR description
- Create a system parameter called "blacklisted_emails" and holding all emails that we want to consider separated by a , - When an applicant is generated from an email, if the email is present on the system_parameter, don't create a partner automatically + don't use the blacklisted email on the field email either - When the field email is updated on the contact, or on the applicant and that the new value is not present in the blacklist, synchronize both records. (as long as we are obliged to use the partner to send the email, we need to keep it synchronized with applicant) - Display the used email on this screen task-id: 3358086 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo spreadsheets now better follow each user's locale, including formatting differences for numbers, dates, formulas, charts, lists, pivots, and accounting values. This makes spreadsheet reports easier to read and reduces mistakes for teams working across different languages and regions.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: Task: [3222401](https://www.odoo.com/web#id=3222401&menu_id=4720&cids=1&action=333&active_id=2328&model=project.task&view_type=form) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Contact merges now include company-specific fields, helping ensure important company-dependent information is preserved when duplicate partners are combined. This reduces the risk of missing or inconsistent business data after cleanup.
Original PR description
Merge company_dependent fields when merginf base_partner task-id: 3103035 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Helpdesk onboarding flow is now smoother by removing an unnecessary save step. Field service actions are clearer with the button renamed to "Plan Intervention", and demo data now better supports customer sales scenarios.
Original PR description
**=helpdesk_fsm, helpdesk_sale_timesheet
Before this commit :
-> in onboarding tour there was a step asking users to save the record
-> button whose name was Create Task was there
-> no demo data for My Customers whose SOL is not linked
IMP:
-> removed the tour step asking users to save the record
-> button name renamed to Plan Intervention
-> added demo data for My Customers whose SOL is not linked and salesperson is
set as mitchell admin
taskId:3459985The data merge tool now handles fields whose values can differ by company. This helps keep merged records accurate across multi-company setups and reduces manual cleanup after deduplication.
Original PR description
Merge company_dependent fields with data merge
Time off requests now rely on the employee's requested dates as the main input, with system dates calculated automatically using work schedules and time zones. This reduces inconsistent leave calculations and makes payroll, planning, timesheets, documents, projects, and helpdesk integrations easier to maintain.
Original PR description
The idea of current date_{from,to} computations is as follows: The user selects the request_date_{from,end} (and optionally request_hour_{from,to} and these inputs are then processed into a…
The idea of current date_{from,to} computations is as follows:
The user selects the request_date_{from,end} (and optionally request_hour_{from,to} and these inputs are then processed into a date_{to,from}, taking into account the type of leave, the work schedule (resource_calendar) and time zone (since date_{to,from} are saved in UTC while the request_dates are stored in the user's timezone.
However, in practice this computation is very messy, resulting in date_{to,from} needing to be specified in all demo data and test cases, even though it should be derived from the request dates. Various superfluous or poorly named methods also exist in this flow (eg _get_start_or_end_from_attendance which really performs a timezone conversion, the logic of which resource calendar to use is scattered across the whole model etc).
date_{to,from} are used many times as inputs throughout the code, with code being present te inverse compute request_date_{from,to} from these values. However in reality this is not possible to do consistently.
Therefore with this commit, we restore request_date_{from,to} as the sole possible inputs, with date_{from,to} being derived from them. In addition, the timezone and resource calendar are consolidated into their own fields, with a single computation method computing them.
task-3081565