Nested gettexts aren't exported. This commit solves the problem by moving the inner gettext outside of the arguments of the first gettext. Forward-Port-Of: odoo/odoo#149921

Nested gettexts aren't exported. This commit solves the problem by moving the inner gettext outside of the arguments of the first gettext.

Forward-Port-Of: odoo/odoo#149921

*: hr_expense Strings within inline templates are not translatable, so we convert these templates into standard templates so that they can be. Task-3761551 enterprise pr: https://github.com/odoo/enterprise/pull/59877 Forward-Port-Of: odoo/odoo#160768 Forward-Port-Of: odoo/odoo#159892

*: hr_expense

Strings within inline templates are not translatable, so we convert these templates into standard templates so that they can be.

Task-3761551

enterprise pr: https://github.com/odoo/enterprise/pull/59877

Forward-Port-Of: odoo/odoo#160768
Forward-Port-Of: odoo/odoo#159892

Create a SO with the following lines: 1. Price Unit 10000, tax 20% 2. Price Unit 10000, tax 20% 3. Price Unit 10000, tax 20% 4. Price Unit 50, tax 20% Confirm, Create a downpayment of 840.0 Check the downpayment Issue: Amount will be 840.01 This occurs because we compute the downpayment values aggregating so line amounts line by line, each time multiplying for the downpayment percentage and rounding the result. Over multiple lines this mechanism may accumulate a rounding error.

Create a SO with the following lines:
1. Price Unit 10000, tax 20%
2. Price Unit 10000, tax 20%
3. Price Unit 10000, tax 20%
4. Price Unit    50, tax 20%
Confirm, Create a downpayment of 840.0
Check the downpayment

Issue: Amount will be 840.01
This occurs because we compute the downpayment values aggregating so line amounts line by line, each time multiplying for the downpayment percentage and rounding the result.
Over multiple lines this mechanism may accumulate a rounding error.

opw-3812925

Forward-Port-Of: odoo/odoo#160662
Forward-Port-Of: odoo/odoo#160521

Before this commit, we didn't correctly detect when to prefix the value of an url field for the href of its link. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160623 Forward-Port-Of: odoo/odoo#160536

Before this commit, we didn't correctly detect when to prefix the value of an url field for the href of its link.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#160623
Forward-Port-Of: odoo/odoo#160536

Current behavior: --- Cannot send SMS to a partner that has a mobile phone number from Panama. Steps to reproduce: --- ```python # 6198 5462 is a valid phone number parsed = phonenumbers.parse('6198 5462', region='PA') is_valid = phonenumbers.is_valid_number(parsed) is_valid == False ``` Cause of the issue: --- Old versions of phonenumbers (external library) are not updated to Panamas mobile phone numbers system change. Fix: --- Monkey patched the library Similar as: ht

Current behavior:
---
Cannot send SMS to a partner that has a mobile phone number from Panama.

Steps to reproduce:
---
```python
# 6198 5462 is a valid phone number
parsed = phonenumbers.parse('6198 5462', region='PA') 
is_valid = phonenumbers.is_valid_number(parsed)
is_valid == False
```

Cause of the issue:
---
Old versions of phonenumbers (external library) are not updated 
to Panamas mobile phone numbers system change.

Fix:
---
Monkey patched the library
Similar as: https://github.com/odoo/odoo/commit/b21df8797141dac9f2cf0315658a08a238849f5b

opw-3682631

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#159970
Forward-Port-Of: odoo/odoo#156969

It should not be common, but through custo or in debug mode, one can create a menu without an URL since it's not required on the model. Through regular flows, it won't be possible since our UI won't let you go through when creating a menu if you don't set a URL. Followup of https://github.com/odoo/odoo/commit/948235079f002794f9837d3cf91e2d20e3254e20 Forward-Port-Of: odoo/odoo#160546 Forward-Port-Of: odoo/odoo#160457

It should not be common, but through custo or in debug mode, one can
create a menu without an URL since it's not required on the model.
Through regular flows, it won't be possible since our UI won't let you
go through when creating a menu if you don't set a URL.

Followup of https://github.com/odoo/odoo/commit/948235079f002794f9837d3cf91e2d20e3254e20

Forward-Port-Of: odoo/odoo#160546
Forward-Port-Of: odoo/odoo#160457

In the cart, customers can edit the quantity, add or remove products, and redeem promo codes, coupons, etc. The express checkout form handles only the quantity change, but the buttons are still shown even with a free cart (e.g. coupon for a free desk). When the customers use them, an error is thrown. Now, if a user has free cart after his modification, it will make express checkout button disappear. task-3568644 Forward-Port-Of: odoo/odoo#160386 Forward-Port-Of: odoo/odoo#149565

In the cart, customers can edit the quantity, add or remove products, and redeem promo codes, coupons, etc. The express checkout form handles only the quantity change, but the buttons are still shown even with a free cart (e.g. coupon for a free desk). When the customers use them, an error is thrown.

Now, if a user has free cart after his modification, it will make express checkout button disappear.

task-3568644

Forward-Port-Of: odoo/odoo#160386
Forward-Port-Of: odoo/odoo#149565

### Steps to reproduce: - Activate Subcontracting in the settings. - Create a storable product - Create a BOM of type "subcontracting" where the subcontractor is a Portal user (e.g. Joel Willis) for that product. - Log out and connect as your portal user. - Go to the website shop and search your product. ### Expected behavior: The portal user should only be able to see the published products. ### Current behavior: The portal user sees unpublished products for which he is subco

### Steps to reproduce:

- Activate Subcontracting in the settings.
- Create a storable product
- Create a BOM of type "subcontracting" where the subcontractor is a Portal user (e.g. Joel Willis) for that product.
- Log out and connect as your portal user.
- Go to the website shop and search your product.

### Expected behavior:

The portal user should only be able to see the published products.

### Current behavior:

The portal user sees unpublished products for which he is subcontractor.

### Cause of the issue:

The commit 99b56ec has introduced a subcontracting portal. In order for portal users to be able to interact with product templates, the following rule was added to the "base.group_portal": https://github.com/odoo/odoo/blame/f0a0d596ab716c96de38a5c0f837da2924338d7b/addons/mrp_subcontracting/security/mrp_subcontracting_security.xml#L120-L131 
When you go to the website shop, the records displayed in the shop will be computed here:
https://github.com/odoo/odoo/blob/1c321cd1fe0aabd9cd92c13cd1eae604e5817ae0/addons/website_sale/controllers/main.py#L348 https://github.com/odoo/odoo/blob/f0a0d596ab716c96de38a5c0f837da2924338d7b/addons/website/models/mixins.py#L353-L357 However, during this call, the "ir.rule" added for portal users will be added to the SQL query here:
https://github.com/odoo/odoo/blob/1c321cd1fe0aabd9cd92c13cd1eae604e5817ae0/odoo/models.py#L4682 As such, products (enven if unpublished) for which the portal user is a subcontractor will be fetched and displayed in the shop.

### Fix:

Since the "ir.rule" can not be changed only for flows involving the `website_sale` application, we propose to make a change similar to commit b1f6171 whose purpose is to hide unpublished products for non internal users:
https://github.com/odoo/odoo/blob/1c321cd1fe0aabd9cd92c13cd1eae604e5817ae0/addons/website_sale/models/product_template.py#L105-L108

opw-3768845

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#159420

Don't show HSN value for sale.order not linked to this localization. Before this commit, if you have multi company with multi localization, you see this field whatever the current localization. It uses the same condition than other report: purchase/invoice/... Forward-Port-Of: odoo/odoo#160766

Don't show HSN value for sale.order not linked to this localization.

Before this commit, if you have multi company with multi localization, you see this field whatever the current localization. It uses the same condition than other report: purchase/invoice/...

Forward-Port-Of: odoo/odoo#160766

Related to previous commit: a9a9d2f12740b02c025f992d62c0d4f5feeaab1d From initial PR: #158843 Improve Regexp to match double slugs /blog/blog-1/post-2 or /blog/1/2 Ignore param order: `?a=<param>&b=<param>` == `?b=<param>&a=<param>` Remove trailing / from base url when querystring is present Ignore '/en' url instead of '/en_US' since the default url_code has been updated meanwhile (269aa594111a152ad4b7714856ea745bfef57155). Add a new test to check that urls are cleaned as expected Remo

Related to previous commit: a9a9d2f12740b02c025f992d62c0d4f5feeaab1d
From initial PR: #158843

Improve Regexp to match double slugs /blog/blog-1/post-2 or /blog/1/2 Ignore param order: `?a=<param>&b=<param>` == `?b=<param>&a=<param>` Remove trailing / from base url when querystring is present Ignore '/en' url instead of '/en_US' since the default url_code has been updated meanwhile (269aa594111a152ad4b7714856ea745bfef57155).

Add a new test to check that urls are cleaned as expected

Remove crawl as admin, since the demo user already have all groups and so we will check the same urls. The overlap is important for a really low value.



_**after** this pr https://github.com/odoo/odoo/pull/159370_
public crawled 68 urls in 6.44s 3167 queries, 0.095s 46.57q per request
demo crawled 271 urls in 21.93s 13365 queries, 0.081s 49.32q per request

_**currently**_
public crawled 92 urls in 8.74s 4233 queries, 0.095s 46.01q per request
demo crawled 819 urls in 68.03s 36603 queries, 0.083s 44.69q per request
admin crawled 813 urls in 67.46s 36441 queries, 0.083s 44.82q per request

_**before** pr https://github.com/odoo/odoo/pull/158843_
public crawled 185 urls in 12.62s 7526 queries, 0.068s 40.68q per request
demo crawled 6691 urls in 443.84s 342327 queries, 0.066s 51.16q per request
admin crawled 6605 urls in 417.36s 336151 queries, 0.063s 50.89q per request

So, it should reduce the crawling from 872" => 27" for the v16.

Forward-Port-Of: odoo/odoo#160409
Forward-Port-Of: odoo/odoo#159370

… india Configure the group of taxes 5% GST to be price_included and apply it on 295. Both children taxes must have the exact same amount. However, this is not the case. In this example, we get 7.02 for one tax (correct) but 7.20 for the other. This is because both taxes are "include_base_amount". opw-3758458 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160541 Forward-Port-Of: odoo/odoo#157890

… india

Configure the group of taxes 5% GST to be price_included and apply it on 295. Both children taxes must have the exact same amount. However, this is not the case. In this example, we get 7.02 for one tax (correct) but 7.20 for the other. This is because both taxes are "include_base_amount".

opw-3758458

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#160541
Forward-Port-Of: odoo/odoo#157890

Currently, when you copy the viva wallet webhook to configure it in your account, you have to select it manually. With this commit we add a “CopyClipboardChar” widget which does this automatically. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160516

Currently, when you copy the viva wallet webhook to configure it in your account, you have to select it manually. With this commit we add a “CopyClipboardChar” widget which does this automatically.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#160516

Create an expired loyalty program with code Open POS session Add product Apply code Issue: code is applied even if expired opw-3624670 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#145609

Create an expired loyalty program with code
Open POS session
Add product
Apply code

Issue: code is applied even if expired

opw-3624670

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#145609

The conditionnal `isinstance(exc, NotFound)` is shadowed by the conditionnal `isinstance(exc, HTTPException)` two lines above. Nobody ever complained that the warning for NotFound error was gone. Since werkzeug 1.0.0, the status code in the response log is colored, 404 is colored yellow which should catch the eye. The explicit warning line isn't really necessary. Forward-Port-Of: odoo/odoo#159665

The conditionnal `isinstance(exc, NotFound)` is shadowed by the conditionnal `isinstance(exc, HTTPException)` two lines above. Nobody ever complained that the warning for NotFound error was gone. Since werkzeug 1.0.0, the status code in the response log is colored, 404 is colored yellow which should catch the eye. The explicit warning line isn't really necessary.

Forward-Port-Of: odoo/odoo#159665

… portal Steps to reproduce: - Open project share any project which has task. - My account > project > open that project you can see task . - Open any task and add new sub-task you can see once the sub-task is saved 'task view' button is displayed. Issue: - Sub-tasks notebook > add a line > 'view task' is displayed at the creation but is then hidden once the task is saved. Solution: - Correct the attrs and change the condition in able to invisible 'view task' once the sub-task is s

… portal

Steps to reproduce:
- Open project share any project which has task.
- My account > project > open that project you can see task .
- Open any task and add new sub-task you can see once the sub-task is saved 'task view' button is displayed.

Issue:
- Sub-tasks notebook > add a line > 'view task' is displayed at the creation but is then hidden once the task is saved.

Solution:
- Correct the attrs and change the condition in able to invisible 'view task' once the sub-task is saved

task-3602610

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#160117
Forward-Port-Of: odoo/odoo#145214

If user had less than 1 point, which is equivalent to 1 quantity of set currency, on gift card and eWallet, they could not use it due to not enough point on Gift Card and eWallet for claiming reward. opw-3667934 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159984 Forward-Port-Of: odoo/odoo#155161

If user had less than 1 point, which is equivalent to 1 quantity of set currency, on gift card and eWallet, they could not use it due to not enough point on Gift Card and eWallet for claiming reward.

opw-3667934



---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#159984
Forward-Port-Of: odoo/odoo#155161

Current behavior before PR: The cursor kept on flickering when attempting to enter a space at the end of label text field of a link resulting in not being able to add space at all. Desired behavior after PR is merged: Now, it's possible to add spaces at the end of a link label. task-3820250 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160661 Forward-Port-Of: odoo/odoo#160060

Current behavior before PR:

The cursor kept on flickering when attempting to enter a space at the end of label text field of a link resulting in not being able to add space at all.

Desired behavior after PR is merged:

Now, it's possible to add  spaces at the end of a link label.

task-3820250

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#160661
Forward-Port-Of: odoo/odoo#160060

How to reproduce: - Install website_slides with demo data - Log in from localhost - Log in from dev.localhost - Switch to localhost - (The system property web.base.url is http://dev.localhost:8069 but we are on localhost) - Go to a course in the back end and click on “Go to website” button You are redirected to the frontend website home page instead of the course home page. This fix solves the problem. Afer correcting this error for the courses (slide.channel), we have found the s

How to reproduce:
- Install website_slides with demo data
- Log in from localhost
- Log in from dev.localhost
- Switch to localhost
- (The system property web.base.url is http://dev.localhost:8069 but we are on localhost)
- Go to a course in the back end and click on “Go to website” button

You are redirected to the frontend website home page instead of the course home page.

This fix solves the problem.

Afer correcting this error for the courses (slide.channel), we have found the same problem for:
- event.sponsor
- event.meeting.room
- slide.slide
So we apply the same correction for them.

Technical note: the button "Go to website" uses the open_website_url method of WebsitePublishedMultiMixin that relies on website_url. That method expects a relative URL in the computed field website_url and not an absolute one
(actually, the method already handle adding the website domain, so it expect the relative part). The problem is that the compute method for the field website_url of channel compute an absolute URL. The consequence is that the
user is redirected to the home page instead of the course page (by WebsitePreview, see get path method). In stable, we cannot change easily website_url to make it relative as it is used in other of places (ex.: if we make it relative the share link in the sidebar on the frontend is relative which is not correct and in mail template, the URL might not be correct as the mail system append the default domain for relative URLs). So instead, we override open_website_url to use a relative URL when the website is not defined. If the website is defined on the course, we call the super implementation because a domain change might be required. Note that by doing that, we duplicate the code of _compute_website_url in open_website_url but making the URL relative instead of absolute. So we should clean that in master.

Task-3635856

Forward-Port-Of: odoo/odoo#160114
Forward-Port-Of: odoo/odoo#148103

Description of the issue/feature this PR addresses: Commit [1] resolved an issue related to the behavior of small font sizes, which caused 'NaN' to appear in the font-size dropdown within the floating toolbar. This occurred due to the removal of a variable definition, resulting in the inability to compute the font size. This commit rectifies the problem by reintroducing the variable in the SCSS file to ensure correct rendering. [1]: https://github.com/odoo/odoo/commit/7931d1a14a3e4e65463cc

Description of the issue/feature this PR addresses:

Commit [1] resolved an issue related to the behavior of small font sizes, which caused 'NaN' to appear in the font-size dropdown within the floating toolbar. This occurred due to the removal of a variable definition, resulting in the inability to compute the font size. This commit rectifies the problem by reintroducing the variable in the SCSS file to ensure correct rendering.

[1]: https://github.com/odoo/odoo/commit/7931d1a14a3e4e65463cc101536061fa259b615d

task-3801894

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#158811

**Description of the issue/feature this PR addresses:** **Before this PR:** When disabling the submenu for events, it would show a 404 Page Not Found error. **After this PR:** Now, the current behavior is that when the submenu is disabled, it redirects to the /register page of the event. task-3658380 Forward-Port-Of: odoo/odoo#160544 Forward-Port-Of: odoo/odoo#152409

**Description of the issue/feature this PR addresses:**

**Before this PR:**
When disabling the submenu for events, it would show a 404 Page Not Found error. 

**After this PR:**
Now, the current behavior is that when the submenu is disabled, it redirects to the /register page of the event.

task-3658380

Forward-Port-Of: odoo/odoo#160544
Forward-Port-Of: odoo/odoo#152409

Steps to reproduce: - create a new spreadsheet - edit a few cells to create a few history revisions - click on menu File > Add to dashboard - close the dialog (you don't even need to actually create the dashboard) - open the history: File > See version history => all the history is gone Task: 3850102 Forward-Port-Of: odoo/enterprise#60063

Steps to reproduce:

- create a new spreadsheet
- edit a few cells to create a few history revisions
- click on menu File > Add to dashboard
- close the dialog (you don't even need to actually create the dashboard)
- open the history: File > See version history => all the history is gone

Task: 3850102

Forward-Port-Of: odoo/enterprise#60063

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. This will be merged in 17.2 with 60233 to allow a faster forward-port and adaptation of the

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.


This will be merged in 17.2 with 60233 to allow a faster forward-port and adaptation of the docker image

Forward-Port-Of: odoo/enterprise#60236

*: hr_payroll_holidays Strings within inline templates are not translatable, so we convert these templates into standard templates so that they can be. Task-3761551 community pr: https://github.com/odoo/odoo/pull/159892 Forward-Port-Of: odoo/enterprise#60185 Forward-Port-Of: odoo/enterprise#59877

*: hr_payroll_holidays

Strings within inline templates are not translatable, so we convert these templates into standard templates so that they can be.

Task-3761551

community pr: https://github.com/odoo/odoo/pull/159892

Forward-Port-Of: odoo/enterprise#60185
Forward-Port-Of: odoo/enterprise#59877

Before this commit the Whatsapp Sent Count (located in the Communication tab of the event view) wasn't including messages sent to the attendees who weren't confirmed. ### [This commit changes] Event mail scheduler will include seats_uncofirmed into calculation of the mail_count_done which is the count of emails sent. This is reflecting the actual number of messages sent. ### [Reproduce] - Install whatsapp_event - Create event E starting in time T (Events/Events) - Add an "Unconfirmed"

Before this commit the Whatsapp Sent Count (located in the Communication tab of the event view) wasn't including messages sent to the attendees who weren't confirmed.

### [This commit changes]
Event mail scheduler will include seats_uncofirmed into calculation of the mail_count_done which is the count of emails sent. This is reflecting the actual number of messages sent.

### [Reproduce]
- Install whatsapp_event
- Create event E starting in time T (Events/Events)
- Add an "Unconfirmed" attendee
- Add an E-Mail in the Communication tab of the event E
	- Set Interval time > T,
	- Template: "Email Reminder"
	- Trigger "Before the event"
- Run scheduled Action sending whatsapp (Scheduled Actions / Event: Mail Scheduler)
- BUG: message sent, but not included in the sent count in the communication tab of the event E

Related to the commit in the odoo community called: [FIX] event: Include unregistered attendee emails in total sent count

# Related PRs in odoo Community
This Pr is a part of fix/test bundle. For more details check out the here Community PR: https://github.com/odoo/odoo/pull/153795

opw-3693626

Forward-Port-Of: odoo/enterprise#60065
Forward-Port-Of: odoo/enterprise#58428

## Issue: - When trying to select any new email template on follow up reports, it will only display the current template (the one configured in the followup level that the customer is currently in), and if you delete it, it's impossible to select one again. ## Steps To Reproduce: - accounting > Follow-up reports. - On a report click on FOLLOW UP. - Notice missing templates in Content Template. ## Solution: - The template_id field's domain is defined as `domain="[('model', '=',

## Issue:

 - When trying to select any new email template on follow up reports, it will only display the current template (the one configured in the followup level that the customer is currently in), and if you delete it, it's impossible to select one again.
 
## Steps To Reproduce:
 - accounting > Follow-up reports.
 - On a report click on FOLLOW UP.
 - Notice missing templates in Content Template.

## Solution:
- The template_id field's domain is defined as `domain="[('model', '=', render_model)]"`, which filters based on render_model. However, it was not functioning correctly because the computation for `render_model` was not being triggered.
- To resolve this issue, I set 'res.partner' as the default render_model in the `default_get`.

opw-3776312

Forward-Port-Of: odoo/enterprise#58400

Previously, testing HMRC features with dummy credentials required manually changing variables within the code. This commit introduces a more user-friendly approach by adding a new configuration parameter. The new configuration parameter defaults to "production" to maintain existing behavior. However, users can switch to a "demo" or other values to transition the APIs to a sandbox environment for testing with mock credentials. task-3820114 Forward-Port-Of: odoo/enterprise#59152

Previously, testing HMRC features with dummy credentials required manually changing variables within the code. This commit introduces a more user-friendly approach by adding a new configuration parameter. The new configuration parameter defaults to "production" to maintain existing behavior. However, users can switch to a "demo" or other values to transition the APIs to a sandbox environment for testing with mock credentials.

task-3820114

Forward-Port-Of: odoo/enterprise#59152

The templates are used to create a report that will be sent to the fiscal authorities of the Netherlands. They have updated to a newer version of the template. Forward-Port-Of: odoo/enterprise#59907

The templates are used to create a report that will be sent to the fiscal authorities of the Netherlands. They have updated to a newer version of the template.

Forward-Port-Of: odoo/enterprise#59907

Some MUA allow users to group messages 'by thread', so that all emails that share some specific headers are bundled together in a 'conversation' view. In general, using the 'References' header to point to the original message in the thread is enough for most MUAs to properly group emails together. This is not the case for Outlook, which also wants the title to somewhat match the original title - some changes are accepted (typically at the start of the subject header) but others aren't.

Some MUA allow users to group messages 'by thread', so that all emails that share some specific headers are bundled together in a 'conversation' view.

In general, using the 'References' header to point to the original message in the thread is enough for most MUAs to properly group emails together.

This is not the case for Outlook, which also wants the title to somewhat match the original title - some changes are accepted (typically at the start of the subject header) but others aren't.

For example, if a ticket is submitted by email alias with the title 'Important issue', then replies with titles like 'Re: Important issue' or '(#123) Important issue' are recognized as being from the same thread, but others like 'Important issue (#123)' are not.

Since the helpdesk override of the display name is mostly there for the backend and not for email communications, this commit forces the helpdesk app to send emails with the exact same title as the initial ticket instead of including the ticket reference in the reply's title.

The ticket reference is still included in the mail body for the customer so no information is lost.

opw-3748509

Forward-Port-Of: odoo/enterprise#60150

The tax closing in France did an override of `_postprocess_vat_closing_entry_results` to be able to compute and compensate (by creating a move) difference from rounding taxes. As this functionality starts to be needed in other countries, we extract that method to `account_generic_tax_report` and made it generic. task-3691312 Forward-Port-Of: odoo/enterprise#59173 Forward-Port-Of: odoo/enterprise#56510

The tax closing in France did an override of `_postprocess_vat_closing_entry_results` to be able to compute and compensate (by creating a move) difference from rounding taxes.

As this functionality starts to be needed in other countries, we extract that method to `account_generic_tax_report` and made it generic.

task-3691312

Forward-Port-Of: odoo/enterprise#59173
Forward-Port-Of: odoo/enterprise#56510

Issue: If a customer was using `round globally` and at some point wanted to export its date, he could not do it because of this rounding parameter. The reason of the fix in the first place is not strong enough (occasional 1 cent rounding issue) to justify blocking such an important flow original pr: https://github.com/odoo/enterprise/pull/34560 opw-3848827 Forward-Port-Of: odoo/enterprise#60026

Issue:
If a customer was using `round globally` and at some point wanted to export its date, he could not do it because of this rounding parameter.

The reason of the fix in the first place is not strong enough (occasional 1 cent rounding issue) to justify blocking such an important flow

original pr: https://github.com/odoo/enterprise/pull/34560
opw-3848827

Forward-Port-Of: odoo/enterprise#60026