Tuesday, November 19, 2024
12 changes
5 changes
Enhancements to existing features
This update aligns the HR Referral applicant area with improved checks for whether users can access specific fields. It helps ensure the application respects field visibility rules more consistently, reducing the risk of users seeing or interacting with information they should not access.
Original PR description
task-4331116 odoo/odoo#186908
US regular payroll calculations can now include employee bonuses and approved expenses directly in payslips. Bonuses are treated as taxable income before taxes, while expenses are added after taxes, helping payroll teams handle these common payments more accurately.
Original PR description
Add `Bonus` input type to `United States Regular Pay Salary Structure`.
Use `Expenses` and `Bonus` input types in the computation of payslips.
* Expenses:
* Allows users to include expenses (added automatically from the Expenses app) into the salary calculation when using the Structure Type "United States: Regular Pay". The rule is placed post taxes in the structure.
* Bonus:
* Add an Input type in "hr.payslip.input.type" called `Bonus`.
* "Bonus" allows users to add an extra source of income for employees that have associated the "United States: Regular Pay" Structure type in their payslip. The rule is placed pre-taxes in the structure, it is a taxable amount.
task-4097635Spreadsheet cell data is now saved in a simpler format, reducing exported file sizes significantly. This can make spreadsheet dashboards and document-related spreadsheet operations faster and lighter to store or transfer.
Payroll now shows warnings for untrusted employee bank accounts directly in the standard payroll app instead of only in the SEPA payroll extension. This helps all payroll localizations spot potentially unsafe payment details before processing salaries.
Original PR description
This will move the warning for untrusted bank accounts from the sepa module to standard payroll so that it's available for all localisations. Task: 4023575
The referral module now includes a reward report that helps review rewards earned by employees for successful referrals. This gives businesses clearer visibility into referral program performance and employee incentives.
Original PR description
This PR improves the referral module's report by adding a reward report that evaluates the data of rewards earned by employees for successful referrals. task-3946561
6 changes
Enhancements to existing features
The Discuss app has been visually softened to reduce harsh contrast, especially in dark mode. This makes conversations easier on the eyes with gentler colors, lighter separators, fewer borders, and more comfortable sidebar spacing.
Original PR description
Especially in dark theme, UI had too much contrast, which makes using Discuss more exhausting than it should. PR makes the following improvements to make Discuss look more pleasing: - Dark theme:…
1 change
Enhancements to existing features
This update enhances the Gantt chart's usability by introducing a dynamic range toggle and a quarter view option. This allows users to switch between static and dynamic views, providing greater flexibility for managing projects with varying task durations, particularly on longer-term initiatives.
Original PR description
This PR is meant to use the standard dynamic range option in gantt view and allow one to go from static to dynamic view by ticking only one button and selecting a date. This PR adds quarter scale in gantt view to add granularity between month and year view. Since year view is very static and based on month-step, the view is not really useful for tasks with heterogeneous durations on long-term projects. The quarter view, added to the dynamic toggle option gives a more smooth experience of the gantt view. Forward-port of https://github.com/odoo/enterprise/pull/50340
Especially in dark theme, UI had too much contrast, which makes using Discuss more exhausting than it should. PR makes the following improvements to make Discuss look more pleasing: - Dark theme: selected item is greyish rather than greenish - Discuss app borders and composer have half reduced opacity - Dark theme: background of conversation is slightly less dark - Message bubbles no longer have borders - White theme: date separator is slightly less visible - Discuss sidebar channel items have more vertical spacing Before (white)  After (white)  Before (dark)  After (dark) 
The point of sale IoT box image is being updated to a newer Raspberry Pi operating system release. This should prevent startup hangs related to display initialization and fix a log rotation configuration issue that could stop a service from starting.
Original PR description
Backport of #187206. For the next IoT box image, we will upgrade to the latest version of RPi OS Lite. This fixes an issue on bootup where the display is not initalised (hangs waiting on `dev-dri-card0/start`). Also removes the `wtmp` and `btmp` paths from `logrotate.conf`. These paths were duplicated from existing logrotate config files, causing the service to fail to start. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Orders paid with the on-site payment option are now confirmed automatically instead of remaining pending. This ensures related delivery or collection steps are created promptly, reducing manual follow-up and improving the customer experience.
Original PR description
As on_site payment provider is a custom one, transaction is created as pending. Therefore, SO is not confirmed and picking is not created which is not convenient for the customer. task-4267776
The code upgrade command is now easier to automate, with cleaner output, clearer required options, and better handling of progress and dirty files. This helps developers and release teams run upgrade preparation more safely and predictably.
Original PR description
Moved the logs/progress on stderr so it is possible to silent them using a shell redirection `2>/dev/null`. Simplified what is written on stdout so it is scriptable. Moved `sys.stdout.isatty()`…
Moved the logs/progress on stderr so it is possible to silent them using a shell redirection `2>/dev/null`. Simplified what is written on stdout so it is scriptable. Moved `sys.stdout.isatty()` outside of `print_progress` so the function is evaluated once, and not everytime we print a progress. Should speedup the scripts a bit on runbot. Moved the `print_progress` in scripts inside the loop, so it doesn't try to `print_progress(..., 0)` and crash on a division by 0. The runner now takes care of logging 0% and 100%, along with the script name. Changed `-t/--test` for `--dry-run`, for consistency with other posix commands such as rsync. Made so it exits 1 when there are dirty files. Added a `--script` option to run a single script. Useful in development when we want to test a single script and not run all the scripts of a given version. Removed the default of `--from`, we couldn't agree on a sensitive default value. `--from` (or `--script`) is now required. Used mature `parse_version` from the tools, which is suitable to parse odoo versions. Added a long text that describes what "code upgrade" is. It is used as the module docstring and the --help description. Used cross-plateform \r instead of unix specific \033. Skipped `__pycache__` folders, not strickly necessary as `.pyc` files would nevertheless be skipped via `AVAILABLE_EXT`. Replaced some string manipulation on paths by pathlib.
Subscription billing now better coordinates invoice creation and payment processing to reduce conflicting updates during automated runs. This helps high-volume systems process recurring invoices and payments more reliably, with fewer interruptions from database conflicts.
Original PR description
Before this commit, amount_to_invoice was computed in the cron when the invoice was created as it depends on qty_invoiced. Unfortunately, the compute would be triggered and the ORM would try to write on the sale.order record at the same time than the cron would continue his job. it would end up with concurrent updates. This commit ensure that the compute method is inhibited during the cron and is triggered at the end of it. task 4216148
Salary configurator dropdowns such as company car, company bike, and spouse income can no longer be cleared to an empty value. This helps ensure compensation configurations remain complete and avoids missing information during salary package setup.
Original PR description
Problem ---------- Dropdown fields in the salary configurator (like company car, company bike or spouse income) can be set to null with the red cross Objective ---------- Set these fields non-nullable : remove the cross Solution ---------- Add the "is_required" field for benefits like in personal infos. Remove the not hidden condition for the personal info drop down. task-4188242