Adds Australian payroll localisation for Odoo, enabling compliant payroll processing, payslip reporting, superannuation file generation, and PAYEVENT file preparation. This helps Australian employers run payroll workflows in Odoo while supporting key local tax and termination schedules for the V17 launch.

Australian Payroll localization for V17 launch.
Phase 1 objectives:
- Implementation of all the necessary schedules excluding very specific cases like death of an employee or payments 
  made far in the past for a complete payroll workflow:
    - withholding ( schedules 1, 4, 8, 15 )
    - termination ( schedules 7, 11 )
- Compliant payslip report structure
- Generation of SAFF files for purposes of super stream
- Generation of PAYEVENT file, which will be used with the governement's connector in phase 2

Rental products added through quotation templates in the Rental app are now treated as rentals instead of sales on sales orders. The product catalog also shows correct rental prices and availability, helping sales teams prepare accurate rental quotations faster.

Before these commits, rental products added with a quotation template were added as 'sold' on a Sales Order, due to the complexity in Rental. Since the restriction of a single rental period per SO, the inclusion of rental products is easier. Also, the catalog was showing a wrong price for rental products.

After these commits, a rental product added to a quotation template through the Rental App will be 'rented' on the Sales Order, and the catalog correctly displays rental product and prices.

task-id: 3076912

See also:
- https://github.com/odoo/odoo/pull/135811

All Colombian electronic invoicing taxes now receive the correct tax category when loaded. This improves consistency in tax setup and helps reduce issues when preparing compliant Colombian electronic invoices.

Currently only some of the CO taxes have the `l10n_co_edi_type` populated when the taxes are loaded. This commit adds the tax type for every tax in l10n_co.

task-3475793

The field service sales flow now uses clearer wording when an extra quotation is created from a task. This reduces confusion between additional quotations and the main sales order generated from the task, while removing an unnecessary tooltip from the New Quotation button.

Before these PR we can see a create new quotation tooltip on 'new quotation' button and after creating new quotation we can see Quotation created in chatter which make the confusion between extra quotations and the SO generated from the task.
Improvements:
Remove the create new quotations tooltip from the new quotation button and and Rename the Quotation created string to Extra Quotation created to avoid the confusion.

task-3476799

The barcode transfer screen now labels its print action more accurately as "Print Barcodes" because it can print both PDF and ZPL formats. Barcode scanning also now respects the companies a user is allowed to access, helping avoid selecting the wrong product when barcodes overlap across companies.

Rename "Print Barcodes PDF" to "Print Barcodes"

The button is visible in Barcode/Operations, in the details of a transfer. It opens a menu to print both PDF and ZPL barcodes, so putting "PDF" in the name was incorrect.

Task: 3290154
COM PR: https://github.com/odoo/odoo/pull/122511

The time off form now shows the payslip status label description that was previously hidden. This makes payroll-related leave information clearer for HR users when reviewing employee time off.

Description :
payslip state label description was not visible inside form view of timeoff

Improvement:
after adding widget payslip state label description is made visible.

taskID:3475416

The Studio button box dialog now shows the proper label for related fields. This helps users choose the right field more confidently and avoids confusion when configuring forms.

The value displayed for the related field in the new button box dialog was not the correct one.

A new automated check confirms that spreadsheet images using access tokens can be deleted correctly. This helps prevent regressions that could leave unwanted images behind in spreadsheet records.

This commit adds a test to ensure image with tokens can be properly deleted.

This fixes an automated bank reconciliation tour that could fail when a tax column appeared and the validate button was not ready yet. The update waits until the button is clickable, reducing false test failures and improving confidence in accounting workflows.

The tour may sometimes fail, because the column of taxes appear, 
and the tour tries to click on the button validate before it's available.
We just add a step so the button is clickable before clicking on it.

Linked to runbot error 24954

This change removes the standalone worksheet option from Field Service when Studio is not available, reducing complexity and avoiding support for two separate worksheet setups. It also reorganizes related reporting code to make the Field Service report components easier to maintain.

## [MOV] industry_fsm_report: split python file

## [REV] industry_fsm*: revert worksheet without Studio

Purpose: Without studio, worksheets have little use and it complicates
the implementation as we have to support two different possible scenarios.

task-3186423

This update removes an obsolete template marker that is no longer needed now that templates are loaded through the modern app framework. It is an internal cleanup intended to simplify maintenance without changing day-to-day user workflows.

As all the templates are now imported in the owl app, there is not need anymore to specify the owl="1" attribute in the templates.

Ref-https://github.com/odoo/odoo/pull/130467

task-3508331

The online bank synchronization area was updated to stop relying on old cookie helper code. This keeps the connector code simpler and better aligned with current platform behavior, with no expected change for day-to-day users.

This update removes a fixed expected query count from an enterprise discussion performance test and calculates it from all related extensions instead. This makes the test easier to maintain and reduces false failures when other modules extend the same behavior.

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

This update simplifies how automated tests check for multiple items in mail-related screens. It helps keep the test suite easier to maintain without changing how users interact with the product.

\* = account_online_synchronization, whatsapp

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

Point of Sale now uses one shared warning popup instead of two nearly identical versions. This reduces duplication behind the scenes while preserving the same user experience, including control over whether an alert sound plays.

The AlertPopup component is identical to the ErrorPopup component, aside from the fact that the ErrorPopup also plays a sound. We thus add a new prop to the ErrorPopup that allows the consumer to decide to have the sound played or not and replace all occurences of the AlertPopup with ErrorPopup.

Task: 3522638

sale_intrastat is missing on Transifex. This commit updates the Transifex config to add it Forward-Port-Of: odoo/enterprise#48106

sale_intrastat is missing on Transifex. This commit updates the Transifex config to add it

Forward-Port-Of: odoo/enterprise#48106

The sign report on a fsm task for a prepaid service does not represent the true amount and hours. Because the service is prepaid/fixed price, it should make calculations according to ordered qty, not the delivered qty. Streps to reproduce: 1. Configure a product type service as prepaid/fixed price to create a task in a field service project  2. Add the product to a SO with quantity 1 and price 100  3. Confirm the SO 4. Go to the task and timesheet 3 hours 5. Click on Sign report Curre

The sign report on a fsm task for a prepaid service does not represent the true amount and hours. Because the service is prepaid/fixed price, it should make calculations according to ordered qty, not the delivered qty.

Streps to reproduce:
1. Configure a product type service as prepaid/fixed price to create a task in a field service project 
2. Add the product to a SO with quantity 1 and price 100 
3. Confirm the SO
4. Go to the task and timesheet 3 hours
5. Click on Sign report

Current Behavior:
The report will show the amount 300 instead of 100.

Expected Behavior:
The amount should be 100, as calculated by the ordered qty.

OPW-3449841

Forward-Port-Of: odoo/enterprise#47493
Forward-Port-Of: odoo/enterprise#45545

Steps to reproduce: ------------------- - create a commission plan (e.g. 10% on everything); - assign this commission plan to a partner level; - create a customer; - create a partner and add the partner level; - create a product; - create an SO with the created product and the created partner as the referrer; - create and validate the invoice; - register the payment which will create a RFQ for the commission of 10%; - go back to the invoice and create a credit note and confirm it;

Steps to reproduce:
-------------------
- create a commission plan (e.g. 10% on everything);
- assign this commission plan to a partner level;
- create a customer;
- create a partner and add the partner level;

- create a product;
- create an SO with the created product and the created partner as the referrer;
- create and validate the invoice;
- register the payment which will create a RFQ for the commission of 10%;

- go back to the invoice and create a credit note and confirm it;
- on the invoice, unreconcile the journal entries;
- add the outstanding credit of the reversal;

- checking the RFQ, an order line was added due to the created credit note (RFQ is now 0);

- go back to the credit note and reset it to draft to edit parts of it;
- edit part (or not);
- confirm it and add the outstanding debit to the related invoice;

Issue:
------
A second negative order line as added to the RFQ.
The amount on the RFQ is negative.

Cause:
------
Validating a refund on an invoice with commission creates a purchase order line with the refund data.

Unfortunately, put this refund in draft does not update the sale order. And when we re-confirm the sale order,
we will create a new purchase order line.

Solution:
---------
Add a message in the chatter to warn the user and keep track of refunds that may be duplicated.

opw-3377288

Forward-Port-Of: odoo/enterprise#47719
Forward-Port-Of: odoo/enterprise#47510

Steps to reproduce ================== - Edit some views with studio - Save and exit studio - Go to the home menu - Open studio - On the top left, click on Customizations > Export - Import the downloaded zip ```SQL bad query: INSERT INTO ir_model_data (module,name,model,res_id,noupdate,studio) VALUES ('studio_customization','odoo_studio_res_part_f3c7daa6-d3f8-4dca-a7c4-dea2796ebfe0','ir.ui.view',431,false,t) ON CONFLICT (module, name)

Steps to reproduce
==================

- Edit some views with studio
- Save and exit studio
- Go to the home menu
- Open studio
- On the top left, click on Customizations > Export
- Import the downloaded zip

```SQL
bad query:
            INSERT INTO ir_model_data (module,name,model,res_id,noupdate,studio)
            VALUES
('studio_customization','odoo_studio_res_part_f3c7daa6-d3f8-4dca-a7c4-dea2796ebfe0','ir.ui.view',431,false,t)
            ON CONFLICT (module, name)
            DO UPDATE SET (model, res_id, write_date) =
                (EXCLUDED.model, EXCLUDED.res_id, now() at time zone 'UTC')
                WHERE (ir_model_data.res_id != EXCLUDED.res_id OR ir_model_data.model != EXCLUDED.model) AND NOT
ir_model_data.noupdate
            RETURNING module, name, model, res_id, create_date, write_date

ERROR: column "t" does not exist
LINE 3: ...7daa6-d3f8-4dca-a7c4-dea2796ebfe0','ir.ui.view',431,false,t)
```

opw-3514268

Forward-Port-Of: odoo/enterprise#48009

To reproduce: Create an activity without setting activity_type, then try to display the record where the activity was set -> traceback Before PR: When creating an activity, you are not always required to set a activity_type, resulting in tracebacks when trying to format it for display. After PR: We don't assume the activity_type is always set, preventing the traceback opw-3438313 Forward-Port-Of: odoo/enterprise#47989

To reproduce:
Create an activity without setting activity_type, then try to display the record where the activity was set -> traceback

Before PR:
When creating an activity, you are not always required to set a activity_type, resulting in tracebacks when trying to format it for display.

After PR:
We don't assume the activity_type is always set, preventing the traceback

opw-3438313

Forward-Port-Of: odoo/enterprise#47989

When doing a comparison between multiple periods with values carried over to them, auditing the carryover values (through the dedicated button in the popup, in debug mode) always opened the latest period. This was due to the fact the main options of the report were directly used, instead of the ones corresponding to the column group owning the value. Forward-Port-Of: odoo/enterprise#47937 Forward-Port-Of: odoo/enterprise#47476

When doing a comparison between multiple periods with values carried over to them, auditing the carryover values (through the dedicated button in the popup, in debug mode) always opened the latest period.

This was due to the fact the main options of the report were directly used, instead of the ones corresponding to the column group owning the value.

Forward-Port-Of: odoo/enterprise#47937
Forward-Port-Of: odoo/enterprise#47476

Before commit: The client is able to use Worldline payment terminal if Ingenico payment terminal is not active in the PoS settings. If Ingenico payment terminal is activated the worldine payment terminal become invisible to the user in the payment method. After commit: The client is able to choose the payment method between Worldline and Ingenico if both of them are activated in the PoS settings. OPW-3501334 Forward-Port-Of: odoo/enterprise#47819

Before commit:
The client is able to use Worldline payment terminal if Ingenico payment terminal is not active in the PoS settings. If Ingenico payment terminal is activated the worldine payment terminal become invisible to the user in the payment method.

After commit:
The client is able to choose the payment method between Worldline and Ingenico if both of them are activated in the PoS settings.

OPW-3501334

Forward-Port-Of: odoo/enterprise#47819

Current behavior: If a PoS had a different currency than the company currency, the total due was not converted in the PoS currency. So when you paid the total due it was not the correct amount. Fix: The total due is now converted in the PoS currency when the PoS is loading the data. We also had to change the refreshTotalDueOfPartner to retrieve the total due in the PoS currency. Steps to reproduce: - Create a PoS that uses a different currency than the company currency (change th

Current behavior:
If a PoS had a different currency than the company currency, the total
due was not converted in the PoS currency. So when you paid the total
due it was not the correct amount.

Fix:
The total due is now converted in the PoS currency when the PoS is
loading the data. We also had to change the refreshTotalDueOfPartner to
retrieve the total due in the PoS currency.

Steps to reproduce:
- Create a PoS that uses a different currency than the company currency
  (change the journal, pricelist and payment method)
- Make some payments with this PoS using the customer account
- Check the total due of the customer account in the PoS, it's not the
  correct value.
- Try to pay the total due, it's not the correct value either.

opw-3469682

Forward-Port-Of: odoo/enterprise#47760
Forward-Port-Of: odoo/enterprise#46718

This traceback appears when user removes timezone from preferences and when user tries to plan existing task in Gantt view. Steps to reproduce: 1) Create a `new DB` and Click on `Settings` > `Users & Companies` > `Users`. 2) Click on `Mitchell Admin` and in form view, open `Preferences` page. 3) Set the `Timezone` field as empty. 4) Install `project_enterprise` module. 5) Open `Project` > click on `My Tasks` > open `Gantt` view. 6) Now, in Mitchell Admin column, hover to any task a

This traceback appears when user removes timezone from preferences and when user 
tries to plan existing task in Gantt view.

Steps to reproduce:
1) Create a `new DB` and Click on `Settings` > `Users & Companies` > `Users`. 
2) Click on `Mitchell Admin` and in form view, open `Preferences` page. 
3) Set the `Timezone` field as empty.
4) Install `project_enterprise` module.
5) Open `Project` > click on `My Tasks` > open `Gantt` view. 
6) Now, in Mitchell Admin column, hover to any task and then click on
   magnifying glass(plan existing).
7) Now click on any task having value of project other than private.

See the traceback:

```
AttributeError: 'bool' object has no attribute 'upper'
  File "odoo/http.py", line 2123, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1699, in _serve_db
    return service_model.retrying(self._serve_ir_http, self.env)
  File "odoo/service/model.py", line 133, in retrying
    result = func()
  File "odoo/http.py", line 1726, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1927, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "addons/website/models/ir_http.py", line 234, in _dispatch
    response = super()._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 190, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 716, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/web/controllers/dataset.py", line 30, in call_kw
    return self._call_kw(model, method, args, kwargs)
  File "addons/web/controllers/dataset.py", line 26, in _call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "odoo/api.py", line 461, in call_kw
    result = _call_kw_multi(method, model, args, kwargs)
  File "odoo/api.py", line 448, in _call_kw_multi
    result = method(recs, *args, **kwargs)
  File "home/odoo/src/enterprise/saas-16.3/project_enterprise/models/project_task.py", line 408, in schedule_tasks
    max_date_start = datetime.strptime(self.env.context.get('last_date_view'), '%Y-%m-%d %H:%M:%S').astimezone(timezone(tz_info))
  File "__init__.py", line 183, in timezone
    if zone.upper() == 'UTC':
```

When user removes the `tz` from preferences, the value of `tz_info` becomes `False`.

See:
https://github.com/odoo/enterprise/blob/cb520b0bf404d5829b2daab2519958213215bbf4/project_enterprise/models/project_task.py#L348-L350

So, when it tries to use `upper` method from `timezone` for value `False`

See:
https://github.com/odoo/enterprise/blob/cb520b0bf404d5829b2daab2519958213215bbf4/project_enterprise/models/project_task.py#L360

this error is being generated.

sentry-4344775086

Forward-Port-Of: odoo/enterprise#45858

1. Prevent user to insert a video via the odoo editor powerbox command. 2. Block blur event when a modal is open. When the user open a link modal in the odoo editor (via the power box command) a blur event is triggered and force the save and reload of the editor. We block the blur event if a modal is open, to be sure the user can add a link without issue. When the link modal closes, the focus is put back in the editor, ensuring the blur event will be triggered next time the us

1. Prevent user to insert a video via the
odoo editor powerbox command.

2. Block blur event when a modal is open.

When the user open a link modal in the odoo editor
(via the power box command) a blur event is triggered
and force the save and reload of the  editor.

We block the blur event if a modal is open,
to be sure the user can add a link without issue.

When the link modal closes, the focus is put back
in the editor, ensuring the blur event will be triggered
next time the user leave the editable document.

task-3058355

Forward-Port-Of: odoo/enterprise#47878
Forward-Port-Of: odoo/enterprise#44260

The Balance Sheet was reworked in https://github.com/odoo/enterprise/pull/35238 ; however, several issues cause it to be unbalanced: - many accounts seem to be referenced with the wrong sign in the Balance Sheet and Profit & Loss; - some account codes (103, 123, 124, 224, 301, 302) are missing from the Balance Sheet; and - the Retained Earnings and Current Year Earnings sections of the Balance Sheet do not reference the income and expense accounts, meaning that they will be incorrect while

The Balance Sheet was reworked in https://github.com/odoo/enterprise/pull/35238 ; however, several issues cause it to be unbalanced:

- many accounts seem to be referenced with the wrong sign in the Balance Sheet and Profit & Loss;
- some account codes (103, 123, 124, 224, 301, 302) are missing from the Balance Sheet; and
- the Retained Earnings and Current Year Earnings sections of the Balance Sheet do not reference the income and expense accounts, meaning that they will be incorrect while the FY is not closed.

This commit solves these problems as follows:
- the wrong signs have been fixed, and the account_codes_formula have been replaced with aggregation_formula where appropriate, to improve performances;
- the missing account codes have been added in appropriate places; and
- the Retained and Current Year Earnings have been made to reference all income and expense accounts (without using a cross_report, due to the incomplete nature of the Profit & Loss at the moment).

I have verified that with these changes, the Balance Sheet is now balanced regardless of the balances in the accounts.

In addition, an incorrect section name has been fixed ('Other Receivables' should be 'Trade Receivables').

taskid:3493555

Forward-Port-Of: odoo/enterprise#47859
Forward-Port-Of: odoo/enterprise#46951

Open General Ledger Write in search bar 'tax' Quick switch period to 'quarter' or something else Export XLSX Issue: lines will be unfiltered From saas-16.3 we don't clear the search bar filter after the date change so we should always keep the `filter_search_bar` option opw-3509427 Forward-Port-Of: odoo/enterprise#47936 Forward-Port-Of: odoo/enterprise#47669

Open General Ledger
Write in search bar 'tax'
Quick switch period to 'quarter' or something else
Export XLSX

Issue: lines will be unfiltered

From saas-16.3 we don't clear the search bar filter after the date change
so we should always keep the `filter_search_bar` option

opw-3509427

Forward-Port-Of: odoo/enterprise#47936
Forward-Port-Of: odoo/enterprise#47669

- Install website_sale_renting - Set taxes included in website settings - Go to /shop - Search for Projector - Total price is taxe included while pricing table is not opw-3484833 Forward-Port-Of: odoo/enterprise#47952 Forward-Port-Of: odoo/enterprise#47340

- Install website_sale_renting
- Set taxes included in website settings
- Go to /shop
- Search for Projector
- Total price is taxe included while pricing table is not

opw-3484833

Forward-Port-Of: odoo/enterprise#47952
Forward-Port-Of: odoo/enterprise#47340

The 10-minute delay isn't needed; testing confirmed it. Focus on quality, and expected messages to avoid user annoyance and maintain ratings. WhatsApp's guidelines allow for scaling to hundreds of thousands of initiated conversations per week. Limiting API calls after 500 messages in 10 minutes isn't practical with such scaling. Task - 3515955 Forward-Port-Of: odoo/enterprise#47528

The 10-minute delay isn't needed; testing confirmed it. Focus on quality, and
expected messages to avoid user annoyance and maintain ratings. WhatsApp's
guidelines allow for scaling to hundreds of thousands of initiated conversations
per week. Limiting API calls after 500 messages in 10 minutes isn't practical
with such scaling.

Task - 3515955

Forward-Port-Of: odoo/enterprise#47528

Since https://github.com/odoo/odoo/pull/122085, `display_name` on `res.partner` is no longer stored, and therefore can't be used in a search domain. This commit replaces occurrences of `display_name` in search domains with `complete_name`, which is now the correct field to use. Task-3518197 Forward-Port-Of: odoo/enterprise#47927

Since https://github.com/odoo/odoo/pull/122085, `display_name` on `res.partner` is no longer stored, and therefore can't be used in a search domain.

This commit replaces occurrences of `display_name` in search domains with `complete_name`, which is now the correct field to use.

Task-3518197

Forward-Port-Of: odoo/enterprise#47927

Description of the issue/feature this PR addresses: In portal user, when any tickets are share then time spent in list view for portal user is not visible. Current behavior before PR: Time spent is not visible in list view for portal user. Desired behavior after PR is merged: Time spent is visible in list view for portal user. Fix: As portal user don't have access rights for timesheet due to which time spent field is not visible. So we have use sudo() to get id from timesheet and u

Description of the issue/feature this PR addresses: 
In portal user, when any tickets are share then time spent in list view for portal user is not visible.

Current behavior before PR:
Time spent is not visible in list view for portal user.

Desired behavior after PR is merged:
Time spent is visible in list view for portal user.

Fix:
As portal user don't have access rights for timesheet due to which time spent field is not visible. So we have use sudo() to get id from timesheet and user can see time spent fields.

task-3346509

Forward-Port-Of: odoo/enterprise#47916
Forward-Port-Of: odoo/enterprise#42774

When using a 'link to record' workspace action accessible_model_ids is not set by default and never computed. This means it's impossible to select any model if none is set on the action itself. task-3487592 Forward-Port-Of: odoo/enterprise#46595

When using a 'link to record' workspace action
accessible_model_ids is not set by default and never computed.

This means it's impossible to select any model if none is set on the action itself.

task-3487592

Forward-Port-Of: odoo/enterprise#46595

[FIX] account_reports: warnings z-index There was an issue with the z-index of 'warnings' and 'btn_group'. To make the 'warnings' be in front of '.o_view_nocontent', we forced it to have a 'z-index' of 999. This worked, but it made a very strange side effect. Sometimes, we couldn't click on the dropdown items on the control panel of a report. The issue was that 'btn-group' forced a 'z-index' of 2 so what actually happened is that the dropdown was behind (even if not visibly) 'warnings'

[FIX] account_reports: warnings z-index

There was an issue with the z-index of 'warnings' and 'btn_group'.

To make the 'warnings' be in front of '.o_view_nocontent', we forced it to have a 'z-index' of 999. This worked, but it made a very strange side effect. Sometimes, we couldn't click on the dropdown items on the control panel of a report.

The issue was that 'btn-group' forced a 'z-index' of 2 so what actually happened is that the dropdown was behind (even if not visibly) 'warnings' so the click was actually being done on it and not the dropdown items.

To fix that we move '.o_view_nocontent' back with the 'z-index' of -1.

Forward-Port-Of: #47909

This pull request (PR) is centered around the newly enacted resolution Resolución 000190-2022/Sunat, which brings modifications to the electronic sales and purchase reports. These reports were initially introduced in a prior PR available at https://github.com/odoo/enterprise/pull/37382, but they have now been superseded by this latest PR. While the core content of these reports remains the same, there are notable alterations in the downloadable TXT file. This includes the addition of ne

This pull request (PR) is centered around the newly enacted resolution Resolución 000190-2022/Sunat,
which brings modifications to the electronic sales and purchase reports.

These reports were initially introduced in a prior PR available at
https://github.com/odoo/enterprise/pull/37382, but they have now been superseded by this latest PR.

While the core content of these reports remains the same, there are notable alterations in the
downloadable TXT file. This includes the addition of new columns and a change in the column order.
All the required data already exists within Odoo; the key task here is to ensure its accurate
inclusion in the updated TXT file.

Here are the specific annexes for each report:

1. Report 14.4: You can access it here - https://drive.google.com/file/d/1HOAhlIx3ba_wtFvg9kufuCA6273KTVEy/view?usp=drive_link.

2. Report 8.4: The relevant document can be found at this link - https://drive.google.com/file/d/11WFdWHTY12DQKy8yxLzdwRl2zifTE8gD/view?usp=drive_link.

3. Report 8.5: You can view this report by following this link - https://drive.google.com/file/d/1_5dz44MUOryRgtAWTUWn3phmRTMexl4I/view?usp=drive_link.

Forward-Port-Of: odoo/enterprise#47881
Forward-Port-Of: odoo/enterprise#47195

Steps to reproduce: - Install Accounting - Go to "Accounting / Accounting / Management / Analytic Items" - Create an analytic item with a date that is not the first day of a month (e.g. 09/09/2023) - Go back to "Accounting / Accounting / Management / Analytic Items" - Switch to Grid view and select "YEAR" as range The analytic item doesn't appear if its date is not set on the first day of a month. Cause: The fetched data should be grouped by month (instead of day) when the range is "YE

Steps to reproduce:
- Install Accounting
- Go to "Accounting / Accounting / Management / Analytic Items"
- Create an analytic item with a date that is not the first day of a month (e.g. 09/09/2023)
- Go back to "Accounting / Accounting / Management / Analytic Items"
- Switch to Grid view and select "YEAR" as range
The analytic item doesn't appear if its date is not set on the first day of a month.

Cause:
The fetched data should be grouped by month (instead of day) when the range is "YEAR".

opw-3413306

Forward-Port-Of: odoo/enterprise#47338

Steps: > first go to the timesheet_grid module > next go to static folder in which there is views folder > then in timesheet_kanban & timesheet_list Issue: the 'start' button of the timer should have the focus by default instead of the search view in the list and kanban views as well. Fix: focus on start button in kanban view & list view. task-3474577 Forward-Port-Of: odoo/enterprise#46074

Steps:

   > first go to the timesheet_grid module
   > next go to static folder in which there is views folder
   > then in timesheet_kanban & timesheet_list

Issue:
    the 'start' button of the timer should have the focus by default instead of the search view in the list and kanban views as well.

Fix:
   focus on start button in kanban view & list view.

task-3474577

Forward-Port-Of: odoo/enterprise#46074

Description of the issue/feature this PR addresses: -Open the helpdesk team view and select the time recorded stat button then you can edit the days/hours spent field from the tree and form view but not in the grid view Current behavior before PR: -Can edit the days/hours spent field in the form and tree view Desired behavior after PR is merged: -Adding the attributes for keeping it a read-only field task-3269548 Forward-Port-Of: odoo/enterprise#40875

Description of the issue/feature this PR addresses:
-Open the helpdesk team view and select the time recorded stat button then you
can edit the days/hours spent field from the tree and form view but not in the
grid view

Current behavior before PR:
-Can edit the days/hours spent field in the form and tree view

Desired behavior after PR is merged:
-Adding the attributes for keeping it a read-only field

task-3269548

Forward-Port-Of: odoo/enterprise#40875

Issue : In planning when we click on new button it opens wizard where space is missing between save as template and checklist Fix : We have added a bootstrap class for adding space between save as template and checklist task-3302412 Forward-Port-Of: odoo/enterprise#41538

Issue :
In planning when we click on new button it opens wizard where space is missing between save as template and checklist

Fix :
We have added a bootstrap class for adding space between save as template and checklist

task-3302412

Forward-Port-Of: odoo/enterprise#41538

Issue : whenever the automatic assignmeent is enabled in helpdesk team form view the team members tooltip is overlapping with the team members field Fix : As we have removed 'o_row'and 'mt8' class due to this now team members tooltip is not overlapping with the team members field task-3302412 Forward-Port-Of: odoo/enterprise#41623

Issue :
whenever the automatic assignmeent is enabled in helpdesk team form view the team members tooltip is overlapping with the team members field

Fix :
As we have removed 'o_row'and 'mt8' class due to this now team members tooltip is not overlapping with the team members field

task-3302412

Forward-Port-Of: odoo/enterprise#41623

Several accounts were missing from the Balance Sheet: - `520000 Short-term financial instruments` was represented only in the case where it is a debit; - `45625 Partners/associates - Capital called up, unpaid` was represented twice in the case where it is a credit; - `4453 VAT due on imports (reverse charge)` and `44531 VAT due on non-EU supplies` were not represented in the case where they are credits. This has now been fixed, and ensures that the Balance Sheet is balanced. This is par

Several accounts were missing from the Balance Sheet:
- `520000 Short-term financial instruments` was represented only in the case where it is a debit;
- `45625 Partners/associates - Capital called up, unpaid` was represented twice in the case where it is a credit;
- `4453 VAT due on imports (reverse charge)` and `44531 VAT due on non-EU supplies` were not represented in the case where they are credits.

This has now been fixed, and ensures that the Balance Sheet is balanced.

This is part of the wider task of re-balancing the Balance Sheets.

taskid:3060790

Forward-Port-Of: odoo/enterprise#47610

In the planning Gantt view, the progress bar percentage is showing incorrectly. Issue: For example, if 17 hours are spent from the allocated 40 hours, the percentage should be 43%, but instead, it is showing 0%. Cause: In the above case, 'row.progressBar.ratio' is returning 42.5. In the current scenario, it is first divided by 100 and then rounded off. As a result, it returns 0%. However, we want to round it off first, so its value becomes 43, and then divide it by 100 to obtain the

In the planning Gantt view, the progress bar percentage is showing incorrectly.

Issue:
For example, if 17 hours are spent from the allocated 40 hours, the percentage
should be 43%, but instead, it is showing 0%.

Cause:
In the above case, 'row.progressBar.ratio' is returning 42.5. In the current
scenario, it is first divided by 100 and then rounded off. As a result,
it returns 0%. However, we want to round it off first, so its value becomes 43,
and then divide it by 100 to obtain the required percentage.

Fix:
'row.progressBar.ratio' is now rounded off first and then divided by 100 to
get the required percentage.

Task: 3346509

Forward-Port-Of: odoo/enterprise#42771