Thursday, May 19, 2022
8 changes · master
Enhancements to existing features
The Archive option is moved out of prominent form buttons and into the Actions menu, where archived records can be restored with a clearer Restore action. This reduces accidental archiving during onboarding and helps users understand where to recover records, with related updates so list and kanban views refresh correctly after archive-related actions.
Original PR description
In an onborading, poeple click on "Archive" -> they don't find the task anymore. Remove "Active" button from the stat bar and move it in the "Action" (only in form). The label is "Archive". When it is Archived, the button become "Restore" 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
Learners can now manually mark eligible course lessons as done or not done, giving them more control over their progress tracking. Quizzes and certifications remain completion-based to preserve assessment integrity, while course pages and fullscreen views behave more consistently.
Original PR description
Purpose ======= Allow the users to themselves mark their course as "done" or "not done" Specifications ============== When the course is a "Training" in fullscreen or in non-fullscreen, or when the course is a "Documentation" in fullscreen mode, allow the user to click on the "done" button in the sidebar. When the course is a "Documentation" in non-fullscreen mode, add a button "Mark Not Done" when the slide is done. The quiz and the certification cannot be marked as done manually, the user has to complete the questions for that. A certification cannot be marked as "Not Done" (but a quiz can). Technical ========= As the fullscreen view and the non-fullscreen view will share a lot of code, make a common class to avoid redundancy. Task-2604792
The mailing list Kanban view has been redesigned to make ungrouped lists easier to scan in a full-width, list-style layout. Users also get faster actions to import contacts or send mailings directly from the list, while grouped views keep the familiar card layout.
Original PR description
Purpose ======= Replace the current "card style" Kanban design by a "list style" design. When the Kanban view is grouped, we use the old "card design". Task-2737782
The online shop now uses smaller product images in grid layouts when they are visually sufficient. This helps pages load faster and reduces bandwidth use without noticeably affecting image quality.
Original PR description
This should improve the page loading time. Now, setting 2 columns per line will use the 1024px picture 3 or more : 512px If the picture is set bigger (2x1 or more, the 1024px version will be used) task-id : 2823110 related : https://github.com/odoo/odoo/pull/86294 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves everyday usability in the Project app with clearer examples, better defaults, cleaner task views, and a new way to find tasks due today. It helps teams create project records faster, keep task accounting aligned, and navigate project information more easily.
Original PR description
Purpose of this commit to improve generic usage of project app. So, in this commit done following changes: -change the placeholder of the name to 'e.g. Monthly review' in project_update_view_form…
Purpose of this commit to improve generic usage of project app. So, in this commit done following changes: -change the placeholder of the name to 'e.g. Monthly review' in project_update_view_form -set the 'analytic account' of the project on the tasks by default -change the placeholder to 'e.g. Product Launch' in project_milestone_view_form -the 'cabinets' milestone should be linked to a milestone service, not a manual one so change data to milestone in demo data -rename the 'rating' stat button into 'last rating' in view_task_form2 -set another employee than Mitchell for the 'customer care (prepaid hours)' SOL field in sale_service_demo_data -display a separator on the right of the stat button so remove unwanted properties in project_rightpanel.scss -add the 'name' field to the 'fields to export' when 'i want to update data' is set to true -remove the 'Getting Things Done (GTD)' example from kanban examples wizard -add a 'tasks due today' filter that should return tasks whose deadline falls on today's date in view_task_search_form task-2809188
Payroll reporting is improved with cleaner country-specific measures, more grouping options, and support for custom measures. Belgian payroll gains new employer tax redistribution rules, CO2 payroll reporting additions, and better collaboration tracking on payslip batches.
Odoo Studio now handles removed view elements more safely by hiding standard elements instead of deleting them outright. This makes it easier to preserve core view structure and avoid difficult-to-reverse customizations, while still allowing Studio-created elements to be removed.
Original PR description
[IMP] web_studio: hide non-studio elements instead of removing them When removing elements from views through Studio, the behavior was to create an xpath node with the attribute `position` set to `replace`. Removing elements this way can be problematic for non-custom, basic elements and the removed elements can't be reset easily, only by resetting the whole view. After this commit, the elements will be differentiated: - if they were previously created through Studio, they can be removed - if they are non-studio elements, they should be hidden
New spreadsheet pivot and list tables now include useful context in their names, such as the first grouping or sorting field. This helps users distinguish similar tables more easily and reduces confusion when several reports are inserted from the same menu.
Original PR description
### Description When inserting a new pivot/list in a spreadsheet, the name of the new table is only build according to the menu the table in included from, leading us to multiple list/pivot with the same name. The idea of this commit is to add some more information in the name, leading us to this kind of structure : 1. PIVOT VIEW: `<action name>` -> `<action name> by <first grouping>`, where 'first grouping' is the field label of the first group, giving priority to column over row 2. LIST VIEW: `<action name>` -> `<action name by <first sorting>`, where 'first sorting' is the field label of the first sorting ### Related Task - task-2832690