Monday, March 11, 2024
12 changes · master
Enhancements to existing features
Project screens no longer allow users to create new company records directly from company fields. This helps keep company creation controlled through the proper setup process and reduces accidental or duplicate company entries.
Original PR description
Disable on the fly creation for companies in the view:
- `project.project.form`: random Project > Settings
- `project.project.stage.view.form`:
Project > Configuration > Project Stages
- `project.project.stage.view.tree`:
Project > Configuration > Project Stages
- `project.task.view.tree.main.base`:
Project > All/My Tasks
task-3507965
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update removes outdated module markers from JavaScript files where they are no longer needed. It does not change business features or user workflows, but keeps the codebase cleaner and easier to maintain.
Original PR description
As the /* odoo-module */ statement isn't required anymore in both `static/src` and `static/tests` folders we can remove them.
CRM lead forms now only suggest sales teams that are configured to manage opportunities. This helps users pick the right team faster and reduces mistakes when assigning leads.
Original PR description
Task : https://www.odoo.com/web#id=1939293&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.3ea95940c687028046d8f125fd609f69 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Custom filters on followers by channel or partner now give a clear error when using unsupported negative options such as “doesn’t contain” or “is not set.” This prevents users from running filters that would not produce useful results and could be costly to process.
Original PR description
Task: https://www.odoo.com/web?#id=1971489&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.b854f12056c6809ade936d9037bba037 There was a generic issue that on custom filter trying to apply filter 'follower(channels)', ' follower(partner)' with 'doesn't contain', 'is not equal to', 'is not set' were not working. By this commit, this issue has been resolved.
Creating a new user will no longer automatically mark their related contact as a customer. This keeps customer lists cleaner and avoids confusing internal users with actual customers.
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
The search panel now places expand and collapse arrows to the left of each item label. This small layout improvement makes navigation clearer and more consistent when users browse grouped information.
Original PR description
PURPOSE it is better to have the arrows to the left of the item being unfolded. SPECIFICATIONS move searchpanel's caret to the leftside of label. task 2258508 closes https://github.com/odoo/odoo/pull/51384 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change stops automatically linting certain tooling files so routine formatting updates do not obscure meaningful work. It helps keep change history clearer and makes future maintenance and code reviews easier.
Original PR description
Rationale: do not automatically lint files as it
* breaks history by creating useless steps when blaming (which is already
complicated enough in odoo files);
* breaks forward ports;
* hide real changes as we have to guess what is the change inside changed
lines;
* add no value for reading / understanding files;
Our position is that lint should be applied only on modified lines, not on
files.
See https://github.com/odoo/enterprise/pull/57968#discussion_r1516093604The mail composer now shows @mention suggestions next to the text being typed instead of fixed at the top or bottom of the message box. This makes it easier for users to select the right person without losing context while writing messages.
Original PR description
Description of the issue/feature this PR addresses: Attach the @mention dropdown to the text instead of the bottom of the box. Current behavior before PR: mention dropdown is showing at the top or bottom of the composer. Desired behavior after PR is merged: mention dropdown will be shown with the typing text. Task: https://www.odoo.com/web#id=2115453&action=327&model=project.task&view_type=form&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves how Odoo tracks changes in mail-related records, especially around computed fields. It adds performance checks to help ensure these tracking operations remain efficient and prepares for further optimization work.
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
This update removes obsolete internal module markers from JavaScript files in accounting-related frontend code and tests. It does not change product behavior, but keeps the codebase cleaner and easier to maintain.
Original PR description
As the /* odoo-module */ statement isn't required anymore in both `static/src` and `static/tests` folders we can remove them.
Users can no longer create new company records directly from selected Planning and Helpdesk screens. This helps prevent accidental or duplicate company setup by requiring company creation through the proper process.
Original PR description
Disable on the fly creation for companies in some views: - `planning.slot.form`: Planning > List View > View Button - `helpdesk.team.form`: Helpdesk > Configuration > Helpdesk Teams > New - `resource.resource.tree`: Planing > Configuration > Materials task-3507965
The calendar event form now hides the appointment type field when it is not already set. This encourages users to configure appointment details through the dedicated Appointment Types flow, helping avoid confusing or inconsistent event setup.
Original PR description
While creating a calendar event record, different field duration, reminders, etc are expected to be filled with values **(when we select appointment type in the form view)** same manner as we create appointment type records via the front end. It's more effective to fill such field values directly from the Appointment Types (via the front end). so the appointment_type_id field is hidden when we create a calendar event record via form view. Task-3768152