Thursday, August 19, 2021
23 changes · master
Enhancements to existing features
The web interface now begins preparing screen data before a user clicks a menu item. This can make navigation feel quicker and reduce waiting time when opening common sections.
Original PR description
dirty implementation of the idea to record a preview
The website configurator now keeps bright colors from uploaded logos when generating a suggested color palette. This helps new websites better match a company's actual brand colors instead of automatically dulling or changing very bright tones.
Original PR description
The algorithm extracting primary and secondary colors from an image automatically mitigates too bright colors. A color component is considered as too bright if its value is above an arbitrary value. We re-use this algorithm in the website configurator to extract colors from logo and to generate a palette. In this particular case we don't want the mitigation to be applied. We therefore added the mitigation threshold as a parameter of 'extract_image_primary_secondary_colors' and avoided any mitigation by setting it to 255 in our case. task-2602521 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 moves Italy-specific electronic invoicing tax fields into the advanced tax settings and shows them only for Italian taxes. This keeps the tax form cleaner for other countries while still making the Italian compliance options available where needed.
Original PR description
The fields should be shown only for Italian taxes, and in the advanced settings. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Helpdesk app has been updated to make setup and day-to-day use easier for support teams. Related Helpdesk features such as field service, timesheets, website forms, forums, live chat, and eLearning are aligned to provide a smoother onboarding experience.
Original PR description
_* = helpdesk_fsm, helpdesk_timesheet, website_helpdesk_form, website_helpdesk_forum, website_helpdesk_livechat, website_helpdesk_slides The purpose of the commit is to improve the usability and onboarding of the helpdesk app. TaskID: 2531501
This update streamlines how several Odoo apps access messaging-related data behind the scenes. It helps make activity, attachment, approval, appraisal, follow-up, signing, and calling features more consistent and easier to maintain without changing the user workflow.
Original PR description
Part of task-2582313
The web client now begins loading menu data earlier, before the user opens the menu. This reduces waiting time when navigating and makes the interface feel more responsive.
Original PR description
see https://github.com/odoo/odoo/pull/74309
The Documents app now uses Odoo's own spreadsheet icon, giving spreadsheet files a more consistent and recognizable look. This is a small visual improvement that helps align the interface with Odoo branding without changing functionality.
Original PR description
PURPOSE: The purpose of this task is to use our own icon design for spreadsheets. SPECIFICATIONS: update spreadsheet icon to odoo's spreadsheet icon. LINKS: Task-2477155
Resolved issues and error corrections
New certifications created quickly from eLearning are now correctly marked as certifications from the start. This prevents them from being hidden from certification selection lists, making setup smoother for course managers.
Original PR description
PURPOSE
Make sure that when users "quick create" a certification, the survey we create is set as a certification.
Otherwise it is afterward excluded from the domain and not possible to find in eLearning.
SPECIFICATION:
Current
When user quick create a certification, then it will create record in survey but not with certification
equals to True. Due to which it will be excluded from domain and we will not able to find it in survey_id in elearning.
To Be:
Pass certification equals to true and scoring_type
equals to scoring_without_answers in context of survey_id. So now,
it will be not excluded in domain('certificate', '=', True) in elearning.
Task Id: 2621296
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prCode cleanup and technical improvements
This update simplifies how Odoo’s messaging services are accessed behind the scenes across Mail, HR, Live Chat, and related apps. It reduces internal complexity and improves maintainability without introducing major user-facing workflow changes.
Original PR description
Part of task-2582313
Miscellaneous changes
This reverts the following commits: - 164409b00106a5f91d8b84ac698f4cf2aebedb91 - f11c807217cccd96fa18fe24c0cbb436bb1830d1 - c92ebc91e261827dfafa602eae5408de2a072609 The fix we initially made did not cover every possible scenario, and applied to every fiscal position, which was not required. It requires a more in depth rework that is under way and will come in a future PR. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo
Original PR description
This reverts the following commits: - 164409b00106a5f91d8b84ac698f4cf2aebedb91 - f11c807217cccd96fa18fe24c0cbb436bb1830d1 - c92ebc91e261827dfafa602eae5408de2a072609 The fix we initially made did not cover every possible scenario, and applied to every fiscal position, which was not required. It requires a more in depth rework that is under way and will come in a future PR. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#75238 Forward-Port-Of: odoo/odoo#75175
This fixes an issue where users did not receive the correct warning when required Google image search settings were missing. The change restores the proper user-facing error, helping users understand what needs to be configured before fetching product images.
Original PR description
The UserError was inadvertently removed and replaced by `google_pse_id_is_set` variable, which is a boolean. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Optional products on sales orders now display discounts according to the selected price list's discount policy. This helps sales teams present consistent pricing and avoid confusion between quoted products and optional add-ons.
Original PR description
Purpose: Display discount as per 'discount policy' of pricelist on optional product of SO. task- 2180180 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 fix prevents calendar views from crashing when a user is not linked to an employee record for the selected company. It helps affected users open HR-related calendars reliably without needing technical workarounds.
Original PR description
When loading calendar views, the client tries to load 'unusual' days, linked to the employee of the current user. But it does not check that the current user is linked to an employee for that company. Task ID: 2628736
This fixes how default scheduled action trigger times are stored by removing milliseconds. It helps avoid tiny timing differences that can cause inconsistent scheduling behavior or unnecessary changes in system records.
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
When creating a new task the name field was not automatically focused. TaskID: 2585999 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 Forward-Port-Of: odoo/odoo#75024
Original PR description
When creating a new task the name field was not automatically focused. TaskID: 2585999 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 Forward-Port-Of: odoo/odoo#75024
If the prefix of the production sequence contains some dashes, it can lead to undesirable behaviors To reproduce the error: (Enable debug mode) 1. Settings > Technical > Sequences & Identifiers > Sequences, edit "San Francisco Sequence production": - Prefix: "WH-MO-" 2. Create a MO - Quantity: 2 3. Confirm, Edit: - Quantity: 1/2 4. (Keep MO's name in mind and) Validate + Create backorder Error: Backorder's name is "WH-MO-002" instead of "WH-MO-0000X-002". Going back
Original PR description
If the prefix of the production sequence contains some dashes, it can
lead to undesirable behaviors
To reproduce the error:
(Enable debug mode)
1. Settings > Technical > Sequences & Identifiers > Sequences, edit "San
Francisco Sequence production":
- Prefix: "WH-MO-"
2. Create a MO
- Quantity: 2
3. Confirm, Edit:
- Quantity: 1/2
4. (Keep MO's name in mind and) Validate + Create backorder
Error: Backorder's name is "WH-MO-002" instead of "WH-MO-0000X-002".
Going back to the initial MO, its name became "WH-MO-001" (was
"WH-MO-0000X")
Note: This commit does not fully fix the issue. For instance, on step
1, if the user updates the prefix with "WH-MO-" and set the sequence
size equals to `SIZE_BACK_ORDER_NUMERING`, the same issue will occur
again.
OPW-2618971
Forward-Port-Of: odoo/odoo#75130If the analytic account have not company then the analytic entrie would have the company of the account move 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 Forward-Port-Of: odoo/odoo#75031
Original PR description
If the analytic account have not company then the analytic entrie would have the company of the account move 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 Forward-Port-Of: odoo/odoo#75031
Had questions more than once about those. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#75299
Original PR description
Had questions more than once about those. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#75299
Slight inconsistency, you could have a view location type not update when the usage was changed to or from view (the hierarchy would be shown which should not be the case). opw-2619043 Forward-Port-Of: odoo/odoo#75285
Original PR description
Slight inconsistency, you could have a view location type not update when the usage was changed to or from view (the hierarchy would be shown which should not be the case). opw-2619043 Forward-Port-Of: odoo/odoo#75285
As the "impuesto unico a los trabajadores" must be paid, the sign must be inverted in order to get a correct sum at the end of the due amount. Forward-Port-Of: odoo/enterprise#20339 Forward-Port-Of: odoo/enterprise#20287
Original PR description
As the "impuesto unico a los trabajadores" must be paid, the sign must be inverted in order to get a correct sum at the end of the due amount. Forward-Port-Of: odoo/enterprise#20339 Forward-Port-Of: odoo/enterprise#20287
Since commit https://github.com/odoo/enterprise/commit/4fbb216a5d1f86cdf92823f8edffc658b3e8165e, we are using _lt function to translate only what we need, but we should convert the result into a string. opw-2627698 opw-2628193 Forward-Port-Of: odoo/enterprise#20332
Original PR description
Since commit https://github.com/odoo/enterprise/commit/4fbb216a5d1f86cdf92823f8edffc658b3e8165e, we are using _lt function to translate only what we need, but we should convert the result into a string. opw-2627698 opw-2628193 Forward-Port-Of: odoo/enterprise#20332
Issue : When creating a ticket via the command /helpdesk <ticket_name> in a discuss window with the module installed, the ticket created wasn't visible by the user that used the command Steps to reproduce: 1) Install Helpdesk Module 2) Helpdesk > Configuration > Helpdesk Teams 3) Enable Live chat for a team [Team A], Save 4) Live Chat > Channels > [Team A] 5) Edit and add a User [User A] to the operators, Save 6) Login with [User A] 7) Discuss > Open a Direct message with anothe
Original PR description
Issue : When creating a ticket via the command /helpdesk <ticket_name> in a discuss window with the module installed, the ticket created wasn't visible by the user that used the command Steps to reproduce: 1) Install Helpdesk Module 2) Helpdesk > Configuration > Helpdesk Teams 3) Enable Live chat for a team [Team A], Save 4) Live Chat > Channels > [Team A] 5) Edit and add a User [User A] to the operators, Save 6) Login with [User A] 7) Discuss > Open a Direct message with another User 8) Type the command `/helpdesk Test` 9) The ticket is created, click on the hyperlink in the message sent by OdooBot confirming the creation -> Bug, you can't see that ticket Why is that a bug: When creating a ticket for a client in live chat, or anywhere else really, the person making the command should be able to view the ticket created, also since the command caller is assigned to that ticket opw-2620284 Forward-Port-Of: odoo/enterprise#20144
Currently, go to helpdesk > configuration > helpdesk team > enable the 'help center' feature. create a ticket > add a description > share on the forum the html tags are display in forum post because previously the description field was text while now it's converted to the html. so while creating the forum post from the ticket do not convert the html description field data into html again using the plaintext2html. directly pass the html as it is as description field is now html field. Tas
Original PR description
Currently, go to helpdesk > configuration > helpdesk team > enable the 'help center' feature. create a ticket > add a description > share on the forum the html tags are display in forum post because previously the description field was text while now it's converted to the html. so while creating the forum post from the ticket do not convert the html description field data into html again using the plaintext2html. directly pass the html as it is as description field is now html field. TaskID: 2602591 Forward-Port-Of: odoo/enterprise#20180