Thursday, February 20, 2025
6 changes · 17.0
Resolved issues and error corrections
Confirmed manufacturing orders now show component availability with the correct color instead of incorrectly warning about overconsumption. This helps manufacturing users quickly see whether required materials are properly reserved before production starts.
Original PR description
Follow-up to #190162 Steps to reproduce: - Create a new Manufacturing Order - Set a product that is in stock as component with a quantity of 1 - Confirm the Manufacturing Order Issue: The component will be displayed in yellow (i.e. overconsumption), as the condition checks always on `should_consume_qty`, which is the quantity that should be used for that amount of `qty_producing`. But that quantity will *always* be 0 for confirmed MOs, as the `qty_producing` will be 0 at the time. Instead, while the MO isn't started yet, we can simply compare to the demand to see if there's enough reservation. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When creating a new project, Odoo now keeps the project stage chosen by the user instead of resetting it to the default stage. This prevents confusion and ensures new projects start in the intended workflow position.
Original PR description
Before this commit, when the user creates a project in the form and select a stage to directly put it in another stage then the first one given as default value. The stage is changed to set again the project in the default stage instead of keeping the choice made by the user. This commit makes sure the stage chosen by the user is still kept once the project is created. Steps to reproduce: ------------------ 1. Install project 2. Go to Project > Configuration > Settings 3. Enable the Project Stage feature 4. Go to Project > Configuration > Projects 5. Click on new button to create a new project 6. Set the project name and click on the second project stage Current Behavior: ---------------- The project goes back to the default stage instead of staying in the stage selected by the user. Expected Behavior: ----------------- The project should be in the stage selected.
The package transfer screen now hides a confusing Done checkbox when product-level validation is not shown. This makes internal transfer workflows more consistent and reduces uncertainty for warehouse users handling entire packages.
Original PR description
## Versions: 17.0+ ## Steps to reproduce: *In `Settings` app, check packages* *In `Operation Types`, in `Internal Transfers`, check the `Move Entire Packages` box* Create an internal transfer with 2 units of `Product A`: - Click `Mark as Todo`; - Click `Put in Pack`; - Validate; Create an new internal transfer with 1 unit of `Product B`; - Add the newly created package; - Click `Mark as Todo`. ## Issue: It is currently unclear for the customer why there is a checkbox to validate packages picking as the box for product picking is hidden. Both should either be displayed or hidden ## Fix: *Discussed with CRL and LASE* Hide the packages' `Done` checkbox as it is the most confusing flow. opw-4380897
This fixes an issue where popover dialog windows could be positioned partly off-screen on very small viewports. Users should now be able to see and interact with these windows reliably, such as when using reception report details from a sales order line.
Original PR description
Depending of viewport size and popover content, the dialog window may get cut off. For example, an extremely small viewport size clicking on the reception report icon while adding a product to a sale order line. Having 0 as the minimum for position values prevents the cutoff. opw-4018341
This change restores the ability to manually edit duration days on working schedule attendance lines. It reverses a prior change that unintentionally blocked edits because of an internal dependency cycle, helping administrators keep schedules accurate.
Original PR description
Revert of commit ca1fa38815070325e3b998efcc0ec0d663b2f3b8 The fix introduced the impossibility of manually editing the duration days of attendances due to a depends cycle. The duration days of attendance should be manually editable.
Payroll managers and billing users can now see and use the option to refund an expense directly through a payslip. This removes an access mismatch and helps authorized staff complete payroll-related expense refunds without workarounds.
Original PR description
In the expense app, a button enables to refund an expense directly in the payslip. This button is however not visible for payroll manager, while the action behind is. This commit solves the issue. task-4570975