Original PR description

make the time shown in the email sent to attendees
consistent with the time shown on the website confirmation
page in order to make sure that users don't get confused
when they see different times displayed.

Task-2451154
Related:
COM-PR: odoo/odoo#65729

Original PR description

These record rules were meant to restrict access to certain model
to create/write/unlink, but not read.
This was leading to issues when others models were trying to read
a template.
Unit test were also added to the sms module to ensure that a member
of group_user can always read a sms template.

task-2191254

Original PR description

Issue

	- Install 'Rental' module
	- Create a rental order
	- Select 'Meeting Room' as product
	- In wizard, select same day for pickup and return date
	  but different hours, then add it.

	Time displayed in product description for return date is wrong.

Cause

	'format_time' function should receive time already timezoned.

Solution

	Add timezone to datetime before format.

opw-2480692

Forward-Port-Of: odoo/enterprise#17272

Original PR description

delivery guide from Chile

Forward-Port-Of: odoo/enterprise#17147

Original PR description

Steps to follow to reproduce the bug:
- Go to app > install the “l10n_ca_check_printing” module
- In the accounting settings > under the "vendor payments" section, in the checks option select the canada check layout
- In accounting > configuration > journals
- Select “Bank” > Edit the form > Advanced Settings > uncheck the "Manual Numbering" field
- Go accounting > vendors >  payments > create a new payment
- Choose “send money” in payment type
- Choose any partner
- Select “Bank” in payment Journal and choose the “Checks” option
- Confirm the payment
- Click on print check
- Enter any valid number on “next check number” field

Problem:
The sequence_number appears on the top right of the check while it shouldn't be.
In the view, this field does not have the condition to check the value of 'manual_sequencing'. So it is always displayed in the check

opw-2455986

Forward-Port-Of: odoo/enterprise#17294

Original PR description

[FIX] l10n_ar_edi: avoid AFIP accesses in test mode

In test mode, we should not access to AFIP web service to get the last invoice number as the AFIP key may be not configured.
Instead of that, we should return a default value.

One reason is that during an upgrade, we check that all the menus/views have the same behaviour before and after the upgrade to check that not menus/views have been broken. During this check, when we access to the `menu account.menu_action_move_out_invoice_type`, `account.move.highest_name` is computed and, in its compute method, `account_journal._get_last_sequence_from_afip()`  is called, which leads to an error as the AFIP key is not configured.

The test mode is enabled only when `self.registry.enter_test_mode(cr)` is explicitely called. This is the case for upgrade tests for example, but not for `l10n_ar_edi` tests.

upg-4898
opw-2481780

Forward-Port-Of: odoo/enterprise#17290

Original PR description

…e current company and workorder company.

Refined search condition on the basis of company_id;
  - The company of the workorder,
  - Or the company is False.

Since, while upgrading the database of the customer, we observed that the team associated with the workorder gets changed as it was not satisfied in the previous domain.

Hence, appending this domain to the condition it would only fetch the records belonging to the same company, in other words, only the same company's team would be allowed to get associated in the record of the workorder.

upg - 9306

Forward-Port-Of: odoo/enterprise#17096

Original PR description

Making the module non-installable generates an error when updating a database where the module is installed.

opw-2454201

Forward-Port-Of: odoo/enterprise#17347