Monday, May 30, 2022
5 changes · master
Enhancements to existing features
The Mass Mailing screen now avoids showing an empty favorites dropdown when no saved filters exist. Users instead see either no unnecessary menu or a clear prompt to save the current filter, reducing confusion and making the workflow easier to understand.
Original PR description
If you do not have favorite filters in the mass mailing UI, they will show an empty drop down. It generates confusion when we don't have any filters yet, so why the meaning of the empty drop down? This commit can solve the above problem and also make some improvements to the following changes in UX related to favorite filter: 1. If we do not have any filters related to the current mailing model, it shows a custom message instead of an empty drop down. 2. Once saved, the favorite filter, then drop down menu is visible. In this commit we can use a new variable `mailing_filter_count`, whose value changes the behavior of the layout. task-2711258 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 refreshes parts of the dashboard experience and fixes several interaction issues in forms, kanban views, and many-to-one fields. It should make everyday work in Odoo smoother by reducing small workflow interruptions and improving reliability in common record editing scenarios.
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
Marketing automation campaigns now handle saved favorite filters more smoothly, matching the experience already available in mass mailing. When users change the target model, the previous filter is cleared automatically to help prevent confusing or incorrect selections.
Original PR description
This commit improves the behavior of the favorite filter in marketing automation. This has been done in mass mailing, and we globally re-use that mechanism here through the same model and widgets. In this commit, we can use a new field `mailing_filter_count`, whose value changes the behavior of the favorite filter layout, and also in `mailing_filter_id` , we added a compute method that sets the `mailing_filter` as `false` every time when `model_id` is changed. For more details see linked community PR odoo/odoo#87673 Task-2711258
Resolved issues and error corrections
This fixes an issue where a project's allocated hours could incorrectly reset to zero after adding an employee-related sales order line in the invoicing tab. Businesses can rely on project hour allocations remaining accurate when sales or pricing details are updated.
Original PR description
This commit fix the computation of allocated_hours field when there is origin id instead of id of project. task-2788878 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 fixes a missing alert when a purchase order created from a sales order is cancelled for make-to-order buy products. Sales teams will now be notified that the original sales order may be impacted, helping them react before customer fulfillment is disrupted.
Original PR description
Description of the issue/feature this PR addresses: This should fix cancelling PO originating from SO for Buy/MTO products not currently in stock. Current behavior before PR: Create and confirm Sale Order with a product that is marked as MTO and Buy and none is in stock. Purchase Order is created automatically. If you cancel SO, notification of exception is brought to PO. But if you cancel PO no notification of exception is brought to SO even the code to do so is there in sale_purchase module in PurchaseOrder's _activity_cancel_on_sale but purchase_line.sale_line_id is not present so it doesn't get to the point of notifying the SO. Desired behavior after PR is merged: It should work both ways - i.e. if PO is cancelled SO should be notified as well. I guess this concerns PR #43366 so maybe @ryv-odoo or @sle-odoo could have something to say. Thank you. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr