Original PR description

Steps:

- Create a task inside any project.
- Create a sub-task under that parent task.
- Open the sub-task and remove the project (clear the project field).
- Look at the status bar at the top of the form view.

Issue:

- The status bar is displayed twice (both the Project stages and Personal stages
- are visible simultaneously).

Cause:

- When the project field is cleared from a sub-task in the UI, conflicting
  visibility rules or residual stage data can cause the status bar widget to
  render twice.

Fix:

- To resolve this, an `onchange` event is added to the `project_id` field. If the 
  user removes the project from a sub-task, the system now instantly falls back to
  the parent task's project and sets `display_in_project = False`. This syncs the
  frontend UI with the intended backend behavior, preventing the interface from
  entering the broken state and removing the duplicate status bars.

task-6033970

Forward-Port-Of: odoo/odoo#255319

Original PR description

We now use `soft_reload` instead of a hard refresh to update the data after validating and printing.

see odoo/enterprise#116210

Original PR description

## Steps to reproduce:
	- Install project_timesheet_forecast module
	- Create a public holiday in one company
	- In another company create a planning slot for an employee that overlaps with the holiday
	- Go to Timesheets/Planning analysis report
	- Notice the report is not showing planned hours for the employee on the day of the public holiday

## Cause:
When filtering the resource_calendar_leaves we don't check for the company so any public holiday in any company will be taken into account even if it doesn't affect the employee

## Fix:
Exclude holidays that has different company than the planning slot

opw-5027070

Forward-Port-Of: odoo/enterprise#116263

Original PR description

Issue:
---

### Steps to reproduce:
1- Create a `Discount Code` program.
2- In SO, use `Coupon Code` wizard and use the code.
3- After available rewards are shown, discard the wizard.
4- Re-apply the code.

Validation Error: The promo code is already applied.

As the reward is not applied, this is functionally confusing. At this point We can see the reward only inside the rewards wizard view.

If we allow re-apply the code in case no reward line is created for the `rule.program_id`, we can still see the reward by re-applying the same code, without any side effects.

opw-6164198

Forward-Port-Of: odoo/odoo#261950

Original PR description

Description of the issue/feature this PR addresses:
Portal crashes with Internal Server Error if the assigned salesperson does not have an email address.

Current behavior before PR:
When opening /my/home with a portal user linked to a salesperson without an email, the view portal.portal_contact tries to concatenate a False value with a string while building the mailto: link. This raises a TypeError: can only concatenate str (not "bool") to str.

Desired behavior after PR is merged:
Portal pages should render normally even if the salesperson has no email address. The link is only generated when the field is available, avoiding the crashink, preventing the crash and ensuring portal pages remain accessible even if a salesperson does not have an email.

Fixes #223677

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

Forward-Port-Of: odoo/odoo#223968

Original PR description

[IMP] hr_contract_salary: fix contract_type_id definition

The definitions of the contract_type_id in hr_contract_salary_offer and l10n_be_hr_contract_salary/hr_contract_salary_offer should be same

I converted the definition of contract_type_id in the base module to the Belgium one.

Also, the contract_type_id was inserted to the view in Belgium one as well, I deleted that part to prevent double appearance.

**This task is only for version 18.0 -> 19.2, the forward porting should be stopped in master. (It shouldn't be forwarded to master).**

task - 6101717

Original PR description

The `button_mark_done` method called through the ORM returns a client action (`do_multi_print`) that should be called by the js code.

This is useful in the case of automatic printing of product labels for example.

The action call was missing, this commit adds it.

opw-5388271

Original PR description

When running the test, `button_validate()` was called twice in succession.
- Once explicitly
- Once through `process_cancel_backorder()`

The first time it is called though, it's not through the restricted user that we want to test, allowing some access rights checks to run smoothly.
The second time it's called with the restricted user, the cache still contains some data that should be no longer accessible, allowing the test to run even though it shouldn't.

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

Original PR description

Steps to Reproduce :
- Go to To-Do → Create New and add a Table of Content block
- Type text → in new line create /h1  → it appears in ToC
- Place cursor before /h1 and press Backspace → it merges with paragraph

Description of the issue:
Table of Content block does not update accordingly

Cause:
After the heading is merged with the previous paragraph, `delayedUpdateTableOfContents` is triggered, but at that time no heading is available in the editable area. As a result, instead of updating the Table of Contents, it returns without making any changes.

Solution:
If Table of content already contains heading, then update regardless of whether editable contains heading elements or not.

task-6150579

Original PR description

Before this commit, creating an invoice with an Early Payment Discount (EPD) as a payment term could cause the schematron validation of the generated invoice to fail when an invoice line had a 0% tax.

The issue was caused by generating two TaxSubtotal nodes for the same TaxCategory (0%, exemption code 'E'):
- one for the 0% VAT
- one for the EPD discount applied to the total amount

However, Peppol requires a single VAT breakdown (TaxSubtotal) per VAT category (in this case: E)

Additionally, when VAT was set to 0%, the allowance charge TaxSubtotal incorrectly used 'S' as a hardcoded tax category code.

This commit fixes both issues.

task-5900496

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

Forward-Port-Of: odoo/odoo#254199

Original PR description

Here is few fixes added to the swedish iso 20022 XML:

- CdtrAgt seems to be always mandatory, change the condition in `_skip_CdtrAgt`
  to always use the CdtrAgt if payment_method is iso20022_se
- The `_is_se_bban` is too restrictive, this should be always True
  when payment method is swedish iso
- The `FinInstnId` node can either contain BIC or ClrSysMmbId. But as
  ClrSysMmbId seems to change from one bank to another, it's more
  relevant to always use the BIC.

opw-5395736

Original PR description

**Purpose**:
A user with planning manager rights but no access to employee and contract
 records should be able to copy and movea planning slot to an employee with
  a flexible resource_calendar without getting an access rights error.

**Before this commit:**
When copying a planning slot, the system tries to compute the working hours
 over the period of the slot. This will raise an access rights error if the
  user doesn't have access to employee and contract records when the slot is
   moved to a flexible resource_calendar.

**After this commit:**
The user can copy a planning slot without access rights error with only planning manager rights, even if the slot is moved to a flexible resource_calendar.

**Steps to reproduce:**
1.Install Planning and Planning Contract modules.
2.Create a user with only planning manager rights and no access to employee and contract records.
3.Copy a planning slot to an employee with a flexible resource_calendar.

opw-6166557

Original PR description

runbot-243298

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