Thursday, May 15, 2025
9 changes · 17.0
Resolved issues and error corrections
The Peppol status footer in email templates was updated with clearer wording and more compatible colors. Tracking was also removed, making the footer simpler and less intrusive for recipients.
Original PR description
Better phrasing, better compatilibity of the colors. Removal of tracking. task-4782004
This fixes a rounding issue that could slightly understate working hours for employees with shifts crossing midnight. Payslips now show cleaner, accurate hour totals instead of fractional values caused by tiny time-calculation differences.
Original PR description
To reproduce: ============= - have an employee with a working schedule of night shifts like 18:00 to 00:00 break to 01:00 then continue to 03:00 - create payslip for this employee for January 2025 - print the payslip, the working hours will be 183.9936 The problem: ============ 00:00 is represented as 23:59:59.99999 in python, that missing microsecond impacts the computation of the duration of the work entry. The solution: ============= round the total seconds opw-4702410 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes Jordanian electronic invoicing handle incomplete draft data more safely during automated checks. It reduces the risk of avoidable crashes in internal validation scenarios without changing normal invoicing behavior for users.
Original PR description
Ensure `_get_payment_method_code` and invoice name handling in `_export_invoice_vals` work safely with incomplete records during this test `test_computed_fields_without_dependencies`. This test creates unsaved records where required fields like `company_id.l10n_jo_edi_taxpayer_type` and `invoice.name` are missing they are intialized in module testsuite . Attempting to access these directly led to a `KeyError` (due to missing taxpayer type) and an `AttributeError` when calling `.replace()` on a boolean. These failures do not occur in the module test suite because records are fully populated, but for test robustness and future-proofing, we now handle missing or falsy values gracefully. build_error-161152
The payment page now keeps the QR code area from shrinking when a payment message contains a very long line. This prevents cropped QR codes, helping customers complete payments reliably.
Original PR description
__Current behavior before commit:__ The QR code on the payment page is cropped when the Pending Message of the payment provider has a long line. __Description of the fix:__ Set `flex-shrink-0` to the QR code card so it doesn't shrink. __Steps to show the cropped QR code:__ 1. Install sale_management and website 2. Set company currency to EUR 3. Enable QR Codes under Customer Payments in Settings 4. Enable Online Payment (and disable Online Signature) under Quotations & Orders 5. In Payment Providers, install SEPA Direct Debit. Select Test mode, check Enable QR Codes, and publish it. 6. **In Messages tab, put a very long line as Pending Message** 7. Go to the Journal "Bank" and set a random IBAN as Account number 8. Create a new Quote with a non 0 price and click on Preview and pay the order 9. The QR code is cropped opw-4735003
Shared project Kanban views now show different progress bar colors for tasks in Done and Approved stages. This makes it easier for portal users to quickly understand task status when viewing shared projects.
Original PR description
### Issue
In project sharing, tasks in the "Done" and "Approved" stages were not shown with distinct progress in the Kanban progress bar. As a result, users were unable to identify the task status easily.
### Reason:
The color class was set incorrectly.
### Fix:
We have updated the color class in this commit to correctly reflect the task stages.
issue-https://github.com/odoo/odoo/commit/1a44b849970d3e39111a99ea35db5b586b184dd3
### Steps to Reproduce:
- Create a project with 2 tasks:
- Task 1 in the "Done" stage
- Task 2 in the "Approved" stage
- Share the project with a portal user
- Open the project in the portal
- Navigate to the project sharing Kanban view and check the progress bar
task-4551177Automated actions now have access to the dynamic date and context values they need when checking their conditions. This prevents rules that depend on values like today's date from failing or behaving incorrectly, improving reliability for scheduled and automated business processes.
Original PR description
Similar to: odoo/odoo#204172 This commit makes sure base.automation evaluated domains have all the dynamic elements they need, such as `context_today`, which is defined in `py_builtin.js` and dynamically retrieves the current date. Task id: opw-4737292
The Swiss payroll configuration menu has been restored so payroll administrators can access salary journal settings and rule parameters again. This helps ensure required payroll setup options are available without workarounds.
Original PR description
To be able to configure salary journals and access rule parameters, we reintroduce back the salary menu in configuration
The Spanish Mod 347 BOE export no longer includes partners who only have cash payments below the reporting threshold. This prevents misleading zero-value lines in the tax file and helps businesses submit cleaner, more accurate reports.
Original PR description
Fix a bug where account moves paid with cash appears in a line with full 0 in the boe export of mod347 tax report. But it shouldn't create a line at all, so this commit remove the lines in this case. task-4613012
This update disables or adjusts failing automated checks related to bank statement imports and expense extraction. It helps keep the development validation process stable while the affected tests are reviewed, with no direct change expected for end users.