Daily updates from Odoo
Monday, September 2, 2024
4 changes · master
Resolved issues and error corrections
Planning schedules now better reflect employee contract status when showing available and unavailable working periods. This helps planners see more accurate availability around draft, active, expired, or cancelled contracts, reducing scheduling mistakes.
Original PR description
In this commit we have made some changes regarding how contracts affect the planning schedule and added some test cases in HOOT. task:3815229
The Partner Ledger partner filter now excludes contact-only partner records, so users see only relevant accounting partners. This reduces confusion when selecting partners for accounting reports and helps avoid misleading report filters.
Original PR description
Steps to reproduce: - Go to Partner Ledger report - Open partner filtering dropdown list Current behaviour: - Show all partners include contact partners Expected behaviour: - Should not show contact partners Explanation: Based on the discussion on discord, https://discord.com/channels/678381219515465750/1099994955830796348/1268492839575093291 We should not display contact partners filtering for accounting report.
Payroll batches now return to the confirmed state when payslips are regenerated for the same employees after being set back to draft. Users with batch accounting enabled also get easier access to the related journal entry, reducing confusion and extra navigation.
Original PR description
-steps to reproduce: create a batch, generate the payslips, set the batch back to draft, regenerate the payslips (with the same employees). -what is the bug: the state of the batch is not set to 'confirmed' after the second generation of payslips. -expected behaviour: the batch should be in confirmed state. -fix: if regenerating with the same employees, nothing is actually done, it should at least set the batch in confirmed state. Also add a button to get to the journal entry if the setting 'Batch Account Move Lines' is enabled. Task: 3975654
This fix makes the Philippine tax reporting logic return accounting entries in a consistent order. It prevents occasional test failures caused by unpredictable ordering, helping keep the module stable without changing user-facing behavior.
Original PR description
Since the moves query didn't specify the ordering, sometimes unit test will failed since the order of the moves are different. x-origin-commit: f25f362