Original PR description

In an aggregation, when a 0-division happens in a formula, the result of the formula will be set to 0. This way of handling 0-division is counter-intuitive and could potentially create errors in the reports.

This commit takes the default 0-division safety off, which forces the dev to think about- and fix these issues. To enable the safety, a developer can enter 'ignore_zero_division' as a subformula on an aggregation.

The 'ignore_zero_division' subformula was added to existing reports and testcases to stay consistent with earlier versions.

task: 3774403

Original PR description

This improvement expands the functionality of the ageing reports by introducing a customizable aging report based on aging intervals. Previously, the aging intervals were fixed at 30 days, but with this PR, users can now input intervals greater than one, Also for intervals less than one an error is thrown.

Task-3669642

Original PR description

Issues:
The model hr.employee requires the group hr.group_hr_user for fields that are not accessible in the employee public profile. The new fields missed the groups.
https://runbot.odoo.com/web#id=61373&view_type=form&model=runbot.build.error&menu_id=405&cids=1

Fix:
Adds the missing groups on the fields
`l10n_au_super_account_ids,super_account_warning`
on h.employee.

Original PR description

Make the sequence ordered works in preparation display when starting a db

Original PR description

Steps to Reproduce:
----------
 - Install the planning module.
 - Navigate to the employee app.
 - Create an employee without a working calendar.
 - Navigate to the planning app.
 - Create a shift.
 - Try to group shifts by role.

Issue:
-------
   When trying to group shifts by role, a traceback occurs if an employee is without
  a working calendar.

Cause
-----
   The traceback arises due to the inability to find work intervals for resources without
    a working calendar.

Solution:
----------
   If a resource has a working calendar, the system retrieves work intervals; otherwise,
  it sets the intervals to 0.

task-3858539

Original PR description

- move many services function to record methods
- rename `Record._store` to `Record.store`, for consistency and
  reasurre it's fine to rely on store in code of models
- replace explicit `rpcWithEnv` to `mail.rpc` service. This is
  slightly easier to use and maintain in code, and is more exact
  to how HOOT works.

https://github.com/odoo/odoo/pull/160798

Original PR description

Discuss code is more complicated than it should. Part of it
comes from split in arbitrary services, which are both confusing
and very verbose.

This commit removes the `mail.message` service: related features
have been moved to the appropriate model.
For example:

```js
this.env.services["mail.message"].edit(message, "new-content");
// =>
message.edit("new-content");
```

https://github.com/odoo/odoo/pull/161255

Original PR description

Discuss code is more complicated than it should. Part of it
comes from split in arbitrary services, which are both confusing
and very verbose.

This commit removes the `mail.persona` service: related features
have been moved to the appropriate model.
For example:

```js
this.env.services["mail.persona"].updateGuestName(guest, newName);
// =>
guest.updateGuestName(newName);
```

Note: persona mixes partners & guests. This method only applies to
guests, hence keeping the "guest" word in method name.

https://github.com/odoo/odoo/pull/161266

Original PR description

Discuss code is more complicated than it should. Part of it
comes from split in arbitrary services, which are both confusing
and very verbose.

This commit removes the `mail.attachment` service: related features
have been moved to the appropriate model.
For example:

```js
this.env.services["mail.attachment"].remove(attachment);
// =>
attachment.delete();
```

Note: remove/delete wording in service was conflicting with core
model feature, e.g. "delete" means server-side deletion while
"remove" is basically record.delete(). To match wording with other
parts of code, their name have been inverted:
- server-side deletion is "remove"
- local deletion is "delete"

Original PR description

We are planning to upgrade the pylint version since ruff is now fully deployed. 

This will fix some of the issue that where not detected with the previous version

Note: `self.transaction_ids` could raise, this is why we have no garantee that  `existing_transactions` will be defined. But the try except does not look to manage this case, this is why it should be safe to move this line outside the try.

Forward-Port-Of: odoo/enterprise#60233

Original PR description

… the cart

-> 17.0

Steps to reproduce :
-> Add a rental product to your cart with a rental period -> Go to the cart
-> Remove one of the date from the rental period
(either pickup date or return date)

Issue :
-> Get this traceback

Cause:
-> when we remove the date from the cart we find a traceback of  'start_date'.

Solution:
-> Added the condition so if the we remove the start date or end date we not get the traceback.

opw-3638268

Forward-Port-Of: odoo/enterprise#58667

Original PR description

When a register payment is made with a writeoff in foreign currency
and when the user set manually an exchange difference account,
don't create a write-off. Instead, 2 cases to consider:
- When the payment is expressed in a foreign currency different than
the invoice's one, play with the rate between amount_currency and
balance and let odoo making an exchange difference accordingly.
That way, the payment has no write-off and the invoice is fully paid.
- When the payment is expressed in company currency but the invoice
has a foreign currency, force the exchange difference to use a rate
that will fully paid the invoice without creating any write-off line
on the payment.

task_id: 3717436

Forward-Port-Of: odoo/enterprise#58511