Daily updates from Odoo
Tuesday, September 6, 2022
4 changes · master
Enhancements to existing features
The reconciliation matching button now opens the related reconciled journal items when a payment or adjustment match exists, making it easier for accounting users to review what was reconciled. The change also fixes invisible zero-amount lines in manual reconciliation and cleans up duplicate code from earlier reconciliation widget work.
Original PR description
The matching button, which shows either "MATCH", "P", "Ax" or nothing
now directs to the list of the reconciled ("P" or "Ax") journal items
of that reconciliation. This is a temporary fix, as it should open
the reconciled items in the manual reconciliation view instead, but
something needs to be done for v16.
It also corrects 2 bugs:
- the amounts of the lines in the manual reconciliation were = 0
(and therefore also invisible).
- with the refactoring for the new bank reconciliation widget,
some duplicated methods were present in the same file.
Moves a reconciliation scss file from community to enterprise.
task-2959808Project teams can now use a cohort view for tasks to spot work items that remain in the same stage for too long. This helps managers identify bottlenecks in kanban-style project workflows and take action sooner.
Original PR description
With kanban PM approach it is usefeul to see which tasks are stuck for too long using cohort view.
This update makes modules explicitly include the payment option they rely on, avoiding missing payment methods in tests and data setup. It also improves Cash on Delivery for UPS delivery so availability better respects company, country, and status settings, including when multiple payment providers are configured.
Original PR description
See the individual commits for more details. task-2853489 See also: - https://github.com/odoo/odoo/pull/99400 - https://github.com/odoo/upgrade/pull/3847
Odoo Discuss now determines access from the conversation type and whether someone is a member, instead of using a separate public/private setting. This makes chats and groups consistently private while channels remain public, reducing confusion and improving access consistency.
Original PR description
Access right should be based on channel type and membership instead. Chat always private, group always private, channel private should disapear and be a group. Channels are always public. task-2632861