Daily updates from Odoo
Navigate
Branch
Sunday, January 26, 2025
5 changes
3 changes
Miscellaneous changes
Partial revert of https://github.com/odoo/enterprise/pull/67111. Some users rely on the structure of the export format (column order). The order is most frequently code, then name. And code is a required field. Those reasons made us want to re-adapt the behavior. We also want the amounts to be formatted with thousands separator and to always have 2 decimals (even if .00) task-4399107 Forward-Port-Of: odoo/enterprise#77825 Forward-Port-Of: odoo/enterprise#75740
Original PR description
Partial revert of https://github.com/odoo/enterprise/pull/67111. Some users rely on the structure of the export format (column order). The order is most frequently code, then name. And code is a required field. Those reasons made us want to re-adapt the behavior. We also want the amounts to be formatted with thousands separator and to always have 2 decimals (even if .00) task-4399107 Forward-Port-Of: odoo/enterprise#77825 Forward-Port-Of: odoo/enterprise#75740
Since this commit:https://github.com/odoo/enterprise/commit/7bfeb39f64bfecde2960c6f6678062ac515589cb it wasn't possible to export in xml a batch payment. no-task-id Forward-Port-Of: odoo/enterprise#77758
Original PR description
Since this commit:https://github.com/odoo/enterprise/commit/7bfeb39f64bfecde2960c6f6678062ac515589cb it wasn't possible to export in xml a batch payment. no-task-id Forward-Port-Of: odoo/enterprise#77758
#### Issue: - When an employee is assigned a resource calendar with the `flexible_hours` option enabled, the daily/weekly overtime on the timesheet calendar is not calculated based on the 'Average Hour per Day' that we set for the flexible resource, it is instead being calculated based on the specific work intervals. #### Steps to reproduce: 1. Assign a resource calendar with `flexible_hours` enabled to an employee. 2. Ensure the calendar has a defined `hours_per_day` value. 3. Verify
Original PR description
#### Issue: - When an employee is assigned a resource calendar with the `flexible_hours` option enabled, the daily/weekly overtime on the timesheet calendar is not calculated based on the 'Average…
#### Issue: - When an employee is assigned a resource calendar with the `flexible_hours` option enabled, the daily/weekly overtime on the timesheet calendar is not calculated based on the 'Average Hour per Day' that we set for the flexible resource, it is instead being calculated based on the specific work intervals. #### Steps to reproduce: 1. Assign a resource calendar with `flexible_hours` enabled to an employee. 2. Ensure the calendar has a defined `hours_per_day` value. 3. Verify that the timesheet grid correctly shows the daily/weekly overtime hours as per `hours_per_day`. 4. Test with non-flexible schedules to confirm existing behavior remains unchanged. #### Solution: - In the frontend, the method `fetchDailyWorkingHours` retrieves daily working hours data by calling the backend method `get_daily_working_hours`. - This method computes working hours based on the employee's `resource_calendar_id` and its associated work intervals. However, It does not check if the `flexible_hours` flag is enabled on the `resource_calendar_id`. For employees with flexible schedules, the backend still calculates working hours based on detailed intervals instead of simply using the `hours_per_day` value defined in the `resource_calendar`. - To fix this I ensure we respect flexible schedules by using `hours_per_day` directly when `flexible_hours` is enabled. opw-4407910 Forward-Port-Of: odoo/enterprise#77315
2 changes
Resolved issues and error corrections
This fix ensures that mention suggestions inside restricted channel threads only show people allowed by the parent channel's access rules. It prevents users from seeing or selecting inappropriate contacts in threaded discussions, keeping collaboration lists consistent with channel visibility settings.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/176758 Commit above adds elligible partners in `@` mention suggestions, when the channel is restricted. However, channel threads could mention anyone,…
Follow-up of https://github.com/odoo/odoo/pull/176758 Commit above adds elligible partners in `@` mention suggestions, when the channel is restricted. However, channel threads could mention anyone, which is unintended. Steps to reproduce: - open a restricted channel, e.g. `#general` - open or make a sub-thread on this channel - type `@` in composer => non-internal users are shows in suggestion list. This happens because when the channel is restricted, this limits the amount of partners in the mention list. Problem is that channel threads do not set their `group_public_id`, and instead the parent value should be checked. This was not taken into account, which lead to unrestricted list of suggestions in these channels. This commit fixes the issue by checking the parent channel `group_public_id` for listing the elligible people that can be mentioned. Before  After 
Miscellaneous changes
**Description of the issue/feature this PR addresses:** When a custom module (e.g., [OCA/social#1536](https://github.com/OCA/social/pull/1536)) adds a new message action using `callComponent`, it is not invoked in certain scenarios. **Current behavior before PR:** Odoo only invokes `callComponent` for `quick actions` (2 or 3 actions). For remaining actions rendered as `DropdownItem`, the `callComponent` is not invoked. **Desired behavior after PR is merged:** This commit ensures con
Original PR description
**Description of the issue/feature this PR addresses:** When a custom module (e.g., [OCA/social#1536](https://github.com/OCA/social/pull/1536)) adds a new message action using `callComponent`, it is not invoked in certain scenarios. **Current behavior before PR:** Odoo only invokes `callComponent` for `quick actions` (2 or 3 actions). For remaining actions rendered as `DropdownItem`, the `callComponent` is not invoked. **Desired behavior after PR is merged:** This commit ensures consistent rendering behavior, invoking the `callComponent` for all actions, whether quick actions or dropdown items. Complementary to: https://github.com/odoo/odoo/pull/131426 @phenix-factory @alexkuhn coud you please review this? CC @pedrobaeza @chienandalu --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#194751 Forward-Port-Of: odoo/odoo#194643