Friday, December 8, 2023
6 changes · master
Enhancements to existing features
Warehouse users can now change a package's location directly from the package form or by dragging it to another location. This improves inventory handling by grouping packages by location, showing clearer mobile package views, and recording package moves in the movement history.
Original PR description
This commit adds the ability to edit the location_id of a package by either changing the field in the form or by dragging the package to another location. The packages are now grouped by location by default and filtered by internal locations or empty locations. When a package is moved, a move is created for each of it quants to reflect in Moves History. Also, a kanban view is added to reflect package contents when on mobile as its better on the smaller screen. TaskId:3479578 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When adding new course content without choosing a section, it will now be placed at the bottom of the most recent section. The latest section is shown by default so users can clearly see where their content will be added before uploading.
Original PR description
- When no specific section is selected, the content will now be inserted at the bottom of the latest section. - For further user understanding and control, display the latest section by default, providing clear insight into where the content is going to land. Task-3452346
Appraisal surveys now open with sensible default settings and hide options that are not relevant to employee appraisals. This makes the appraisal setup page clearer for HR users and reduces the chance of choosing unsuitable survey settings.
Original PR description
Make the following changes when appraisal is selected 1. Provided default values for the following fields -> "access_mode" - "is_attempts_limited" - "users_can_go_back" 2. Hide the live session section and button 3. Make the following fields invisible -> "is_time_limited" - "scoring_type" - "certification" We also adapt the form/kanban inherited views for hr_appraisal by making them non-primary. As the invisibility rules they add are not specific to this module usage, we want them always applied. This makes the subsequent overrides more consistent and also allows for simplifying the act. window records. Task-3390319
Resolved issues and error corrections
Odoo now recognizes the port provided by a proxy server, so users accessing Odoo through a non-standard web port are no longer redirected to the wrong address. This improves reliability for companies hosting Odoo behind gateways such as Nginx.
Original PR description
Install nginx, setup it to listen on port 8080 instead of default 80
then setup a regular proxy_pass toward a local odoo listening on port
8069 with all the X-Forwarded- headers set:
listen 8080;
server_name mycompany.odoo.com;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header X-Real-IP $remote_addr;
location / {
proxy_pass http://127.0.0.1:8069;
}
Inside your browser, access "http://mycompany.odoo.com:8080" you are
wrongly redirected to "http://mycompany.odoo.com:80".
The `X-Forwarded-Port` header wasn't taken into account by Odoo.
Closes: #64643Fixed an issue where employee avatar cards could fail to open when the Skills app was installed without Planning. Employee skills now display reliably because the shared tag display support is available from the core HR app.
Original PR description
Steps ===== - Install module hr_skills (but not planning) - Open the avatar card of an employee with skills linked to it Issue ===== A traceback appears indicating: "OwlError: Cannot find the definition of component "TagsList", missing static components key in parent". Cause ===== The AvatarCardResourcePopover component was patched in planning to add the component TagsList to it. This component was also used by the patch applied on AvatarCardResourcePopover in hr_skills. However, when hr_skills is installed but not planning, the component TagsList is used (to display the skills of the employee) but no append to the AvatarCardResourcePopover (or the AvatarCardEmployeePopover that inherits from it). Fix === The component TagsList is added in hr instead of planning as this module is required by both planning and hr_skills.
This fixes crashes when opening employee or resource avatar cards in cases where related modules or access rights differ. Users can now view relevant avatar details without unexpected errors, including planning users who do not have HR permissions.
Original PR description
[FIX] planning: add TagsList component to avatar card in hr instead of planning =============================================================================== Steps ----- - Install module hr_skills…
[FIX] planning: add TagsList component to avatar card in hr instead of planning =============================================================================== Steps ----- - Install module hr_skills (but not planning) - Open the avatar card of an employee with skills linked to it Issue ----- A traceback appears indicating: "OwlError: Cannot find the definition of component "TagsList", missing static components key in parent". Cause ----- The AvatarCardResourcePopover component was patched in planning to add the component TagsList to it. This component was also used by the patch applied on AvatarCardResourcePopover in hr_skills. However, when hr_skills is installed but not planning, the component TagsList is used (to display the skills of the employee) but no append to the AvatarCardResourcePopover (or the AvatarCardEmployeePopover that inherits from it). Fix --- The component TagsList is added in hr instead of planning as this module is required by both planning and hr_skills. [FIX] planning: avoid traceback for non hr-user when opening avatar card ======================================================================== Steps ----- - Install planning - Log in as a planning user with no hr access - Open the planning app - Click on the avatar of a resource with roles linked to it Issue ----- An access right error message appears indicating that the current user can't access the default_role_id field of the resource. Cause ----- This field of the resource.resource model is protected to user with hr access rights. In the avatar card component it was read, whatever the rights of the current user were. Fix --- A check on the access rights of the current user is added in the component to avoid to read that field if it is not allowed.