Monday, October 4, 2021
7 changes · master
Enhancements to existing features
This change makes it easier for country-specific or custom modules to adjust information when creating stock return transfers. It helps businesses adapt return workflows to local or specialized requirements with less custom development effort.
Original PR description
Description of the issue/feature this PR addresses: On some country or custom modules is need pass values before create picking, this PR has as objective facilite inheritance 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 change makes the expense payment process easier for developers to extend when creating payments from expenses. It helps businesses adapt expense payment workflows to specific needs with lower customization effort and reduced maintenance risk.
Original PR description
Description of the issue/feature this PR addresses: similar to payment create on https://github.com/odoo/odoo/blob/master/addons/hr_expense/wizard/hr_expense_sheet_register_payment.py#L112 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 adds automated validation to ensure recurring project subtasks are copied correctly. It helps protect future changes to task recurrence logic by confirming deep subtask structures and recurrence settings behave as expected.
Original PR description
This commit adds a test in order to strengthen the behaviour of recurring subtasks. This test asserts that child with depth > 3 are not copied in a recurrence, that recurrent subtask are well copied with the recurrence correctly set. This commit prepares the recurrence refactoring. task-2660756 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
The payment form now supports receipt payments where no customer or vendor is selected. This prevents an error when opening payment details or related statistics, making the accounting workflow more flexible for cases where a partner is not needed.
Original PR description
- Create a payment without a partner for a receipt - Go to the form view - Click on the stats button. => Error, 'partner_id' is required In some cases, having the partner not required on the view is needed. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The CRM lead form now shows the Customer field when a customer is already linked, while keeping it hidden for typical unassigned leads unless debug mode is active. This helps users understand when lead contact details may also update the linked customer record, reducing confusion during lead management.
Original PR description
PURPOSE To display partner_id when it has value in lead form view. SPECIFICATION Current: It show partner_id in debug mode only. To be: It should display partner_id when its value is set and also display in debug mode if value is not set. Task id: 2596955 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website accordion snippet now offers additional visual styles and more control over where the expand or collapse icon appears. This gives website editors more flexibility to match accordion sections, such as FAQs, to their page design without custom development.
Original PR description
task-2457232
Users now receive clear explanations when they try to delete event questions or answer options that attendees have already used. This helps prevent confusion while protecting historical attendee response data from becoming incomplete.
Original PR description
PURPOSE If we try to delete an answer which is already been selected by attendees, odoo will throw a validation error "There must be suggested value or text value", it is because the attendees with those answers are "broken" by this change since their answer disappears. Same thing happens if we try to delete a question which is already answered. SPECIFICATION There is no way we could let the user do delete that because all "historic" attendees need to refer to this answer/question record (or they would be empty) , But we should at the very least catch this and provide a clearer error message. So in this commit we will updated the error message as "You cannot delete an answer that has already been selected by attendees." if they try to delete answer and "You cannot delete a question that has already been answered by attendees." if they try to delete questions. LINKS PR #76265 Task 2635599