Tuesday, September 5, 2023
6 changes · master
Resolved issues and error corrections
Credit notes will no longer try to reconcile with an original invoice or vendor bill that has been reset to draft. This prevents user errors when confirming a credit note again and keeps accounting workflows moving smoothly.
Original PR description
The aim of this commit is to prevent reconciliation with credit note to be triggered when a reversed move is reset to draft Context: reconciliation between credit note and invoice (same for vendor bill) Previous to this commit: Post invoice Create and post credit note Reset to draft both the invoice and the credit note Post (confirm) again the credit note -> User error due to attempt of reconciliation between credit note and draft invoice After this commit: The credit note is posted but not reconciled when the original move is in draft task-3492197
This fix makes an automated test for single notifications run consistently instead of failing at random. It helps keep the bus messaging component's quality checks reliable, reducing false failures during development and release validation.
Original PR description
Before this commit, the "subscribe to single notification" test failed in an undeterministic fashion. This commit solves this issue. fixes runbot-24033
When someone applies for a job that has no recruiter assigned, the applicant record will no longer automatically list the public website user as responsible. This keeps ownership fields accurate and avoids confusion for recruitment teams reviewing new applications.
Original PR description
Steps: - install hr_recruitment app - Create a job Positions without Recruiter - Published job Positions - Got To website and apply - Open applicant - Public user is set in applicant responsible Issue: public user is set if Recruiter is empty in job Position Fix: In this commit we have removed the default current user as the responsible applicant. task-3424017
This fixes a small usability issue in Odoo's web interface where search text stayed visible after selecting a record in avatar-style many-to-many tag fields. Users now get a cleaner input field after each selection, reducing confusion during data entry.
Original PR description
Before this commit, performing a search in a Many2manyTagsAvatarFields and selecting an element does not remove the search value from the input. Why not? The value passed to Autocomplete is the default ''. As this value never changes, onWillUpdateProps is never called and cannot empty the input. Solution: Use the resetOnSelect option to force the input to be reset at each select if props.value is the default value. 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
List and kanban views now use the right display limits when users switch between grouped and ungrouped data. This prevents too many or too few groups or records from appearing, making navigation and reporting views more consistent.
Original PR description
Be in an ungrouped list or kanban view. The "limit" number of records is displayed (by default 80). Apply a group by. The same limit is applied for the number of groups, whereas there's a specific parameter ("groups_limit") for the number of groups to fetch and display. The same problem occurs the other way around (going from grouped to ungrouped), as in this case the groups_limit is kept when the view is no longer grouped.
This commit fixes the issue by forcing a reset of the limit when we go from grouped to ungrouped and from ungrouped to grouped.
We also add a test to ensure that the "groups_limit" is taken into account even when there're multiple groupbys, which wasn't the case in previous versions, but which is working as expected with the new model.
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-prThe Knowledge share panel now immediately reflects changes when a user updates an article's workspace visibility. This avoids confusion from the selection snapping back and removes the need to reload the page to confirm the new setting.
Original PR description
Currently, the input selection controlling the visibility of the article in the workspace is not properly updated whenever the user selects a new value. The user has to reload the page to see the change. Steps to reproduce the error: 1. Create an article in "Workspace". 2. Open the share panel of the article you created. 3. Change the visibility of the article. => The input selection changes but returns to its initial state. TO BE: The input selection should be updated and reflect the new configuration of the article. task-3482257