Tuesday, December 24, 2024
14 changes · saas-17.4
Resolved issues and error corrections
The file selection button now updates its colors to match the selected website theme and input field styling. This prevents visual inconsistencies in forms and keeps the user interface looking polished across different color schemes.
Original PR description
This PR aims to improve the color of the file input field that did not change when the theme color or input color was updated. With this PR, the file input field color will now adjust according to the background color of the input field and the theme color. task-4174112
Web notifications now hide the underlying links created when users mention people or channels. This prevents confusing or cluttered notification text and gives recipients a cleaner message preview.
Original PR description
Current behavior before PR: When a user mentioned a channel or another user in a message, the web notification displayed the mention URL on the recipient’s side, causing a UI issue. Before / After <div style="display: flex;"> <img src="https://github.com/user-attachments/assets/3e8d381a-5d08-4f43-89f4-382d7b9bcca1" width="48%" style="margin-right: 4%;" /> <img src="https://github.com/user-attachments/assets/9abb168c-fe7d-4828-b55f-140219deb003" width="48%" /> </div> Desired behavior after PR is merged: This commit resolves the issue by hiding the mention URL in web notification when a user mentions a channel or another user in a message. Task-4295310 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The accounting dashboard now excludes already paid bill installments from the late bills count. This keeps dashboard totals accurate and helps teams avoid chasing payments that have already been settled.
Original PR description
**[FIX] account: Account Journal Late Bills Count** This fix mitigates an issue when a line of a Bill is paid but appears in the late Bills count in the dashboard. **Steps to reproduce:** 1. Create a payment term to pay in installemts. 2. Create a bill an X amount back in the past to have one installment as late. 3 - Pay the late installment **Issue**: The paid installment will still be counted as late in the dashboard. **Fix**: filter out line with residual amount different than zero. _opw-4327227_ --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Helpdesk onboarding tour now continues as expected after a user selects a customer or enters information. This prevents new users from getting stuck during setup and makes the first-time experience smoother.
Original PR description
Previously, when a customer was selected or input was entered, the onboarding tour failed to proceed to the next step. With this fix, the tour will correctly advance when the user provides input. Without demo data, the database does not have Deco, so I used admin. task-4372470
This fixes an issue where restaurant staff could hit an error when opening “More Options” from booking management in Point of Sale. The update adds the missing appointment-related assets so the booking form loads reliably.
Original PR description
Since the latest changes on https://github.com/odoo/enterprise/commit/6d49119281901e51910bb71e34300e414216123b, we use the gantt view as in appointments so when trying use the "More Options" from here, we will try to load the calendar form for which we will need to add the assets to not throw an error. Steps to reproduce: 1. Get a restaurant session in pos. 2. On the top right burguer menu, select Manage Bookings. 3. Then create a new one o select an existing one to open the dialog. 4. Click on "More Options". opw-4334444
Miscellaneous changes
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#191594
Original PR description
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#191594
Backport commit 454f861 by @svs-odoo. Versions affected: - 16.0 - 17.0 Before this commit, the `product.template` constrains `_check_sale_product_company` didn't work if the recordset contains products from different companies, causing a traceback. How to reproduce: - Create multiple products at once in different companies. For example, in the shell of a newly created DB: - company_b, company_a = self.env["res.company"].search([]) - products = self.env["product.product"].create([ {'n
Original PR description
Backport commit 454f861 by @svs-odoo.
Versions affected:
- 16.0
- 17.0
Before this commit, the `product.template` constrains `_check_sale_product_company` didn't work if the recordset contains products from different companies, causing a traceback.
How to reproduce:
- Create multiple products at once in different companies. For example, in the shell of a newly created DB: - company_b, company_a = self.env["res.company"].search([]) - products = self.env["product.product"].create([ {'name': "prod1", 'company_id': company_a.id}, {'name': "prod2", 'company_id': company_b.id}]) -> Traceback.
To fix this issue, this commit groups products by their company in `_check_sale_product_company`.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#191553
Forward-Port-Of: odoo/odoo#191522For an expense report paid by an employee, the bank account set on the employee form should be used to create the Journal Entry and as a default bank account in Register Payment Wizard. task-4379148 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191416 Forward-Port-Of: odoo/odoo#189967
Original PR description
For an expense report paid by an employee, the bank account set on the employee form should be used to create the Journal Entry and as a default bank account in Register Payment Wizard. task-4379148 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191416 Forward-Port-Of: odoo/odoo#189967
Steps to reproduce the bug: - Enable “Subcontracting” and “Expiration Date” in MRP settings. - Create a storable product “P1” with the following configurations: - tracked by: LOT - Expiration date: True - BoM: - BoM type: subcontracting - subcontractor: Azure interior - Create a lot “L1” with an expiration date set to 01-01-2026. - Expiration date: 01-01-2026 - Configure the operation type:: - Receipt: - use existing SN: True - Crea
Original PR description
Steps to reproduce the bug: - Enable “Subcontracting” and “Expiration Date” in MRP settings. - Create a storable product “P1” with the following configurations: - tracked by: LOT - Expiration date:…
Steps to reproduce the bug:
- Enable “Subcontracting” and “Expiration Date” in MRP settings.
- Create a storable product “P1” with the following configurations:
- tracked by: LOT
- Expiration date: True
- BoM:
- BoM type: subcontracting
- subcontractor: Azure interior
- Create a lot “L1” with an expiration date set to 01-01-2026.
- Expiration date: 01-01-2026
- Configure the operation type::
- Receipt:
- use existing SN: True
- Create a receipt:
- Receive from: Azure interior
- Product: one unit of P1
- Mark it as todo
- Open the detailed operation:
- Set the “L1”
- Record production
- Reopen the detailed operation
Problem:
The expiration date in the stock.move.line is set to today’s date instead of the lot’s expiration date.
Cause:
When marking the receipt as “To Do,” the SML is created. Since no lot_id is initially set, today’s date is assigned, thanks to the _compute_expiration_date method:
https://github.com/odoo/odoo/blob/9f1d555ac2d9b6e9d3d0d723d4f042eb44cf30b7/addons/product_expiry/models/stock_move_line.py#L37-L40
But When the lot_id is later set, the compute method is triggered again. However, since the SML already contains a date, the expiration date is not updated to match the lot’s expiration date.
opw-4394662
Forward-Port-Of: odoo/odoo#190747**Issue:** When printing a Purchase Order or Quotation in a company using the Indonesian tax chart, a tax code (Indonesian tax description) appears instead of the tax percentage. **Steps to Reproduce:** 1- Ensure the company uses the Indonesian chart of accounts. - Install the l10n_id module. - Go to Settings > Taxes and set the Fiscal Country to Indonesia. 2- Navigate to Purchase and create a Purchase Order. 3- Add a product line and select an Indonesian tax (ex: 11%). 4- Print the
Original PR description
**Issue:** When printing a Purchase Order or Quotation in a company using the Indonesian tax chart, a tax code (Indonesian tax description) appears instead of the tax percentage. **Steps to…
**Issue:** When printing a Purchase Order or Quotation in a company using the Indonesian tax chart, a tax code (Indonesian tax description) appears instead of the tax percentage. **Steps to Reproduce:** 1- Ensure the company uses the Indonesian chart of accounts. - Install the l10n_id module. - Go to Settings > Taxes and set the Fiscal Country to Indonesia. 2- Navigate to Purchase and create a Purchase Order. 3- Add a product line and select an Indonesian tax (ex: 11%). 4- Print the Purchase Order. The printed Purchase Order displays the tax code (description) instead of the tax percentage. The same behavior occurs in the Sales module regarding quotation printing (see screenshots attached) <img src ="https://github.com/user-attachments/assets/08dd6940-e07e-4e44-9f03-85f8ae2e8914" width=300 /> <img src ="https://github.com/user-attachments/assets/a8d16f6c-c6a0-441f-8c3f-3546387fb4e6" width=300 /> opw-4333143 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191367 Forward-Port-Of: odoo/odoo#187703
Also display lot/serial numbers products that are located in sub-locations. opw: 4415220 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#191054
Original PR description
Also display lot/serial numbers products that are located in sub-locations. opw: 4415220 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#191054
Steps to reproduce: --- - Install ``planning`` module - Give the demo user as ``administrator`` in planning. - Log in as Demo user > Go to planning - Click on ``New`` > click on the ``Resource`` field Traceback: --- ``IndexError: tuple index out of range`` The error occurs at [1] because we couldn't find an employee in ``avatar_per_employee_id``. This happens when a new resource is created in the first tab, but the ``employee_id`` is not found in the ``resource`` in the second tab
Original PR description
Steps to reproduce: --- - Install ``planning`` module - Give the demo user as ``administrator`` in planning. - Log in as Demo user > Go to planning - Click on ``New`` > click on the ``Resource`` field Traceback: --- ``IndexError: tuple index out of range`` The error occurs at [1] because we couldn't find an employee in ``avatar_per_employee_id``. This happens when a new resource is created in the first tab, but the ``employee_id`` is not found in the ``resource`` in the second tab. This commit resolves the above error by returning false if an employee is not present. [1]- https://github.com/odoo/odoo/blob/fb4d758ed78211a61ea797759e1fb3b02b51be60/addons/hr/models/resource.py#L34 sentry-5508268100, 6134007941 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#173598
Steps to reproduce: - Open Expenses. - Upload a sample expense pdf. The blue ribbon shows up saying “” - Do not click on the refresh button. Instead, put in some value for the amount and submit and approve the expense. - Go back to the expenses list view Issue: Notice this expense is at the top of the list and grayed out Cause: The order is determined by the extract_state_processed field: https://github.com/odoo/enterprise/blob/ba06e216ab73c73e3a67fd917623c6ad357b869f/hr_expense_ext
Original PR description
Steps to reproduce: - Open Expenses. - Upload a sample expense pdf. The blue ribbon shows up saying “” - Do not click on the refresh button. Instead, put in some value for the amount and submit and…
Steps to reproduce: - Open Expenses. - Upload a sample expense pdf. The blue ribbon shows up saying “” - Do not click on the refresh button. Instead, put in some value for the amount and submit and approve the expense. - Go back to the expenses list view Issue: Notice this expense is at the top of the list and grayed out Cause: The order is determined by the extract_state_processed field: https://github.com/odoo/enterprise/blob/ba06e216ab73c73e3a67fd917623c6ad357b869f/hr_expense_extract/models/hr_expense.py#L21 An expense is muted when this field is set to `True`: https://github.com/odoo/enterprise/blob/1df090289f3c45c200d133734989a6d9a8073145/hr_recruitment_extract/views/hr_applicant_views.xml#L67 Solution: We override `iap_extract` method https://github.com/odoo/enterprise/blob/2e3113562309bf4d440e12ab09eaf94d0b302f1f/iap_extract/models/extract_mixin.py#L69 If the expense is not in draft, it indicates that the process continued without waiting for the extraction process to complete (values were manually entered). To ensure a consistent extraction state, we extend the "Check OCR Status" logic to prevent an infinite waiting_extraction status. opw-4239404 Forward-Port-Of: odoo/enterprise#75202
Export from `account_batch_payment` to CBI's RIBA text file format, so that the customer can upload its requests for payment (bank receipts) to the bank. - New field: `l10n_it_sia_code`: Interbancary identifier given by SIA when signing a CBI contract to start doing Ri.Ba.s - New payment method: `RIBA` - Added the methods to read and write the Ri.Ba. text format, i.e. we are able to read an `example` created with FattureInCloud. - Implemented the flow by taking the data from payments and
Original PR description
Export from `account_batch_payment` to CBI's RIBA text file format, so that the customer can upload its requests for payment (bank receipts) to the bank. - New field: `l10n_it_sia_code`: Interbancary identifier given by SIA when signing a CBI contract to start doing Ri.Ba.s - New payment method: `RIBA` - Added the methods to read and write the Ri.Ba. text format, i.e. we are able to read an `example` created with FattureInCloud. - Implemented the flow by taking the data from payments and calling the export functions. - Built a test - Made some demo data - Added translation strings - Riba sequence number, it's created on export and persisted on the batch payment at the moment, so if you re-export, it won't change. It's not shown to the user though. Do we want that to be shown? Editable? Task [link](https://www.odoo.com/odoo/project/967/tasks/4254966) task-4254966 Forward-Port-Of: odoo/enterprise#76088 Forward-Port-Of: odoo/enterprise#74097