Tuesday, May 30, 2023
10 changes · master
Enhancements to existing features
The partner/reseller and customer website pages now have cleaner card-based layouts, better search and filter placement, and an improved mobile filtering experience. These updates make the pages easier to browse, more visually consistent with other website areas, and clearer for visitors using phones or desktops.
Original PR description
The goal of this PR is to improve the structure (alignments, font sizes...) of the two modules as it was clumsy and not appealing. A specific mobile view for the filters was implemented off canvas as the current one was not optimized. All these changes were made to make these modules more consistent with the rest of the front-end modules. task-3083706 upgrade pr : **https://github.com/odoo/upgrade/pull/4690**
The event booth booking flow now shows a clearer step-by-step progress indicator for booth selection, contact details, and confirmation or payment. Users can more easily go back to booth selection, keep their previous choices when returning, and see payment-focused wording when paid booths or cart totals are involved.
Original PR description
CHEVRONS Add chevrons to the event booth front-end process. A template is added to be called in booth choice and form views, and the one called from js is also updated with chevrons. The code is…
CHEVRONS Add chevrons to the event booth front-end process. A template is added to be called in booth choice and form views, and the one called from js is also updated with chevrons. The code is minimized, and fits for the three current steps only. - Booth Selection - Contact Details - Confirmed / Payment CLICKABLE + REMEMBER BOOTH CHOICE To ease the process of changing booth / booking another one, the "Booth Selection" chevron is clickable and highlighted on hovering. Also, it will keep booth_ids and booth_category_id url parameters. From that, the category will be selected and the booth_ids checked (if available), the first time the selection screen is loaded (once the user goes between booth categories, it will not remember booths any more and not preselect any) In order to do so, the arguments are added to the appropriate methods in controller (and overrides), with particular attention to match format. (string vs int...) SCSS Styling is added in website_event_booth.scss. Cautions are taken to ensure proper chevrons coloring even with edited theme colors. DYNAMIC WORDING Instead of 'confirmed', 'payment' is used in chevrons, and "Go to payment" instead of "Book my Booths" in the contact details form, if one of the following is true (~ new boolean value 'use_payment_step'): - In selection screen: at least one category is not free - In Contact Details screen: the chosen booth is not free - In both Selection and Contact screens: if cart has non null total amount. (this is the current logic used to redirect to payment) CONTROLLER REORGANIZATION In order to add the "use_payment_step" to the rendering values, the routes of those views now have their value preparation methods, making them easily overriden (done while maintaining guidelines) OTHER CHANGES - Some wording on the form - Hide sponsors in the booth booking flow - All views have the same space between chevrons and content (48px) - Tour is updated to match new wording. - New map icon and simple link button to display the map of booths. - No more justify content for display of booth categories - unglue the rows of booths vertically Task-2821962
Challenge goals are now refreshed based on actual user activity rather than only recent logins. This helps prevent stale gamification reports while avoiding unnecessary processing for inactive users, including better coverage for portal users.
Original PR description
*: base In the cron updating challenges goals, we were historically filtering in records of users that logged in since the last update. This doesn't work because sessions can last a long time, so users are active between cron runs but their goals are not updated and stale reports were sent. We temporarily fixed this in v14.0 by updating all goals for internal users, but this can lead to unnecessary computations too, and still misses goals of active portal users. Instead, we are here using the `bus.presence` records to track user activity, combining it with the session lifetime to avoid indefinitely fetching old goals that couldn't need an update. This works for both internal and portal users. Note: we update stale base comments in favor of exposing bus.presence to guide developers. Task-3148858
Discuss now has a more reusable viewer for opening and previewing shared content such as link previews and attachments. This creates a more consistent experience for users and makes future preview improvements easier to deliver.
Users can now open project, ticket, milestone, and timesheet actions from a sales order even when no related records exist yet. New records created from those views are automatically linked to the relevant sales order line, reducing manual navigation and setup work.
Original PR description
Description of the issue/feature this PR addresses: The goal of these changes is to make it easier for the user to manage their SO. They can create new tickets/timesheets/etc without being forced to leave the application to open the one they need, nor do they need to manually link the new record to the SO Current behavior before PR: the 'project', 'ticket', 'milestone' and 'hours recored' button are enabled only when record linked to SO already exists. Desired behavior after PR is merged: Those buttons are now enabled even if there are no record, and if the conditions are met: if at least one SOL has an invoice policy of type :prepaid, timesheet, milestone. The user is then redirected to the corresponding view and is able to create record that are automatically linked to the SOL with the lowest sequence. task 2954409 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Sales order users can now create related items such as helpdesk tickets and timesheets directly from the sales order view. This reduces switching between apps and automatically links the new records to the right sales order, making follow-up work faster and less error-prone.
Original PR description
Description of the issue/feature this PR addresses: The goal of these changes is to make it easier for the user to manage their SO. They can create new tickets/timesheets/etc without being forced to leave the application to open the one they need, nor do they need to manually link the new record to the SO modification to the ticket action view from the SO, to be consistent with the community PR community pr : https://github.com/odoo/odoo/pull/100300 task 2954409
Payroll salary attachments can now be linked more easily to recurring payslip inputs, including deductions or additions, and can be created for multiple employees at once. The update also improves payslip calculation details and streamlines payroll line information to reduce duplication.
The Documents app now prevents users from saving links that are not valid URLs. This helps keep shared document records reliable and reduces confusion caused by broken or malformed links.
Original PR description
Purpose ======= Do not allow to set invalid URLs. Task-3283452
The Gantt timeline views used for planning, HR work entries, payroll, projects, and forecasting have been rebuilt on Odoo's newer interface framework. This should make these scheduling screens easier to maintain and improve future reliability while preserving their business behavior.
Original PR description
Rewriting of the Gantt renderer to Owl. Community PR: https://github.com/odoo/odoo/pull/56954 Task [2329576](https://www.odoo.com/web#id=2329576&action=333&active_id=133&model=project.task&view_type=form&cids=1&menu_id=4720)
Resolved issues and error corrections
This update fixes several issues in inventory detail operations, especially when users select existing stock quantities to create or edit move lines. It makes the workflow clearer by showing the right stock records, filling quantities more accurately, hiding irrelevant fields, and preventing incorrect draft status changes.
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