Thursday, February 29, 2024
7 changes · 17.0
New functionality added to Odoo
This update adds support for Jordan's administrative divisions (states/provinces) to the Odoo system. Users in Jordan can now select their state when entering address information, improving data accuracy and localization for Jordanian businesses and customers.
Original PR description
Description of the issue/feature this PR addresses: Add country states for Jordan Current behavior before PR: No country states are imported by default for Jordan Desired behavior after PR is merged: Country states are imported by default for Jordan --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
This update adds missing French translations for tax rounding terms in the French localization reports module. The translation files have been reorganized to prevent translations from being marked as obsolete during future updates, making the system more maintainable and ensuring consistent French terminology for tax reporting features.
Original PR description
### [I18N] l10n_fr_reports: add tax rounding terms A few of translations relating to 03ce6ce were not included with the original commit. This commit adds the terms to the l10n_fr_reports.pot file, and the translations to the fr.po file. Thank you Antoine (andu) for the Frenchification of the terms. task-id: 3717388 ### [I18N] l10n_fr_reports: restructure po/pot files Add the missing terms to the pot file. When the terms are missing from the pot file, but present in the po file, they get marked as "obsolete". This happens during the merge function that is called within tools/translate.py. In order to avoid this, the pot and po files have been re-generated and restructured in order to make future additions easier to merge. Forward-Port-Of: odoo/enterprise#56590
Resolved issues and error corrections
The date range picker interface has been improved to better align the apply button and add a cancel button for easier dismissal. Users can now close the date picker by clicking a cancel button, in addition to pressing ESC or clicking outside the popup, making the interface more intuitive and user-friendly.
Original PR description
Current behaviour - when we access the daterange picker, it was observed that the `apply` button appeared flatter and was not vertically centered. Expected behaviour - add h-100 on buttons container to ensure they are vertically centered and no longer appear flatter - add cancel button in which action is similar to pressing ESC or clicking outside the popover Task-3624556 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
- Issue addressed by this commit: Before this commit, a leave that was completely covered by a public time off would not be handled correctly if the public time off was deleted. That led to errors being raised while it shouldn't. The dates used for the comparison were also wrong leading to some edge case issues. - How to reproduce the issue: 1. Create a public time off over one week 2. Create a paid time off for an employee in one the middle of that week 3. (Create a paid time off o
Original PR description
- Issue addressed by this commit: Before this commit, a leave that was completely covered by a public time off would not be handled correctly if the public time off was deleted. That led to errors…
- Issue addressed by this commit: Before this commit, a leave that was completely covered by a public time off would not be handled correctly if the public time off was deleted. That led to errors being raised while it shouldn't. The dates used for the comparison were also wrong leading to some edge case issues. - How to reproduce the issue: 1. Create a public time off over one week 2. Create a paid time off for an employee in one the middle of that week 3. (Create a paid time off outside that period that would use all the remaining leaves allocated) 4. Delete the public time off - Behaviour before this commit: - With step 3: An error is raised stating that the remaining allocation is not sufficient. - Without step 3: The time off stays and its duration made unavailable to the employee. - Expected behaviour: In both cases, the leave should be archived with a reason stating that it was covered by a public leave which has been removed. We don't want the employee to have deducted time off as he might not be aware that he had a leave covered by a public time off. opw-3740941 Forward-Port-Of: odoo/odoo#155455 Forward-Port-Of: odoo/odoo#155067
This update improves how the system creates attachments when generating PDF reports. A new technical hook has been added that allows customization of attachment details during report generation, making the system more flexible for projects with specific attachment requirements. No changes to how reports work from a user perspective.
Original PR description
Description of the issue/feature this PR addresses: Previously, an `ir_actions_report` refactor landed on: - [ ] https://github.com/odoo/odoo/pull/85150 It totally makes sense to create `ir.attachment` from the streams if needed during PDF generation. For some of the projects we still need to override attachment values. This PR provides a hook to prepare attachment values needed for attachments creation during the pdf report generation. Nothing changes in the sense of business logic. Ping @smetl @xmo-odoo --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#153086 Forward-Port-Of: odoo/odoo#138159
This update fixes a test failure that occurs on February 29th in leap years. When calculating inventory dates for items without a specific cyclic inventory location, the system defaults to the company's annual inventory date. On leap years, this calculation incorrectly adjusts February 29th to February 28th of the next year, causing the test to fail. This fix ensures the test properly handles this edge case.
Original PR description
For a quant without a cyclic inventory location, the inventory date is defaulted to the company's annual inventory date. In these test, this date is set to today, which means that the quant inventory date will be computed to next year, taking into account leap years. This means that on the 29th of february, the inventory date would be computed to the 28th of february of the next year. This causes the test to fail since it compares the inventory date day with the company's annual inventory date day, which in this specific use case will not match. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update addresses an intermittent timing problem in the messaging module's call testing suite. The fix applies a standard correction to ensure tests run more reliably by properly using the updated test helper. While the issue is difficult to reproduce consistently, this change follows established best practices to prevent similar timing-related test failures.
Original PR description
Not a guaranteed fix (not reproducible 1500 attempts), but applying standard fix for `step` failing to use the new step helper. runbot-54560