Tuesday, April 2, 2024
47 changes
22 changes
Resolved issues and error corrections
This update tidies how the website editor manages link preview behavior and event cleanup. It reduces the risk of editor actions interfering with other page behavior, helping keep editing more reliable without changing visible features.
Original PR description
In preparation of https://github.com/odoo/odoo/pull/98429
This fixes an internal test issue affecting analytic reporting when accounting permissions are present. It ensures the test uses the right access group when available, helping keep validation reliable without changing normal user behavior.
Original PR description
The fields debit and credit are shown in analytic. They are hidden when account is installed if you don't have the group, which is the default. When account_accountant is installed, then the group is given by default. To fix the test on debit and credit, we just give the group if it exists. Linked to runbot error 61019 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an internal timing issue that could make live chat-related automated tests fail unpredictably. It helps maintain confidence in the quality checks without changing how users experience the product.
Original PR description
missing last_interest_dt of channel member can lead to unwanted unpinned channel in test due to race condition. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
1 change
Resolved issues and error corrections
This update resolves an issue where users couldn't modify or remove products from the catalog view when multiple line items were added. The fix adds a necessary condition to allow updates and removals, ensuring a smoother user experience when managing multiple items within the catalog.
Original PR description
**Before this PR:** When more than 1 line item is added, users are unable to update or remove products from the catalog view. **Technical Reason:** There is a function _is_readonly() that returns True if there are multiple line items, and because of this, the value of props.readOnly becomes True which prevents users from updating the products in catalog view. **Solution:** Adding one more condition in account_move_line to satisfy the desired behavior. **After this PR:** The users can update or remove the products from the catalog view if there are multiple line items. **Task**-3806509
16 changes
Enhancements to existing features
The SEPA Direct Debit payment setup screens were updated to align with recent payment app changes. Configuration sections and message fields that are no longer managed this way are now hidden, reducing clutter and keeping the setup experience consistent.
Original PR description
Following the removal of explicit view configuration fields and the _compute_view_configuration_fields method in the payment module, this commit updates the payment_sepa_direct_debit module using xpaths to hide : - `credentials` page - `allow_tokenization` fields - `pre_msg` fields - `done_msg` fields - `cancel_msg` fields task-3679393 See odoo/odoo#152517 See odoo/upgrade#5667 See odoo/documentation#7686
8 changes
Enhancements to existing features
The HR Holidays dashboard has been improved to provide a better user experience. Warning messages about half-day leave requests are now positioned at the bottom of the screen to prevent them from overlapping with the ribbon, and unnecessary scroll bars have been removed from dialog windows to make the interface cleaner and easier to read.
Original PR description
The warning message when you have a half-day off confirmed while the duration of this leave's type is daily is moved towards the bottom of the sheet to avoid overlap between this message and the ribbon. And to improve the readibility of the dialog view, the scroll bar is removed when it's not needed. task: 3820211 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
when you install point_of_sale and after install l10n_* then it's not auto install l10n_*_pos after this commit it's installed --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#153385
Original PR description
when you install point_of_sale and after install l10n_* then it's not auto install l10n_*_pos after this commit it's installed --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#153385
Fix a bug introduced by 67901a4429c69fbba96c32af5d8f58aff54f0be5 When an expense is submitted and for the steps after, there is no need to recompute the product_cost as it may be confusing or generate discrepancies with the account move by changing the totals. task-3580004 Forward-Port-Of: odoo/odoo#155487 Forward-Port-Of: odoo/odoo#141400
Original PR description
Fix a bug introduced by 67901a4429c69fbba96c32af5d8f58aff54f0be5 When an expense is submitted and for the steps after, there is no need to recompute the product_cost as it may be confusing or generate discrepancies with the account move by changing the totals. task-3580004 Forward-Port-Of: odoo/odoo#155487 Forward-Port-Of: odoo/odoo#141400
Follow-up of [1]. Commit [2] refactored the way we check if an option update needs to trigger a page reload: if the option is marked as a page option (`data-page-options="true"` on the option's main `<div>`), then it will reload whatever the method used if there is a `reload` parameter. Note that this `reload` parameter does not make much sense anymore, it should be reviewed/removed in master. Problem: [2] made a mistake in its implementation, pushing an array instead of concatenating it. Thi
Original PR description
Follow-up of [1]. Commit [2] refactored the way we check if an option update needs to trigger a page reload: if the option is marked as a page option (`data-page-options="true"` on the option's main…
Follow-up of [1]. Commit [2] refactored the way we check if an option update needs to trigger a page reload: if the option is marked as a page option (`data-page-options="true"` on the option's main `<div>`), then it will reload whatever the method used if there is a `reload` parameter. Note that this `reload` parameter does not make much sense anymore, it should be reviewed/removed in master. Problem: [2] made a mistake in its implementation, pushing an array instead of concatenating it. This worked by chance, as instead of asking "does this option method requires a reload", it was asking "does this set of option methods requires a reload"... and in that case, the code is fallbacking on retrieving common parameters, which `reload` likely is without custo. This could have been fixed in master only. Given the very low risk of breaking anything critical updating this code, it was chosen to prevent a potential crash in custo (which could occur as we give a wrong parameter type to a main method) and allow overrides to make `reload` a specific parameter for a specific method without the need of `data-reload` added in the DOM. [1]: https://github.com/odoo/odoo/commit/556ae457b02e9c077d09fa9c3f9f1e6c6e26b345 [2]: https://github.com/odoo/odoo/commit/03c552690b15cbf2e7d6b7812386ac64042219af#diff-70f7fe38208aa7fe678f18e329d3c11b70065dee723921352b6005774e8bab53R456 Forward-Port-Of: odoo/odoo#159640
The numpad in the PoS was sometimes handling events when it was not supposed to, leading to unexpected behavior. This was due to the fact we did not check if there was a buffer holder for the numpad before triggering the event handler. The check is now done by adding a check in the _onKeyboardInput method. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159619
Original PR description
The numpad in the PoS was sometimes handling events when it was not supposed to, leading to unexpected behavior. This was due to the fact we did not check if there was a buffer holder for the numpad before triggering the event handler. The check is now done by adding a check in the _onKeyboardInput method. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159619
## Before this commit: Modifying a location from/to a scrap location should be restricted when there are move lines with reservation. However, starting from Odoo 17, the quantity field indicates the reserved quantity only when the move line's state is different from done. ## After this commit: Only check if there are reservation lines (move lines not in done) in the location when changing from/to a scrap location to match the behaviour before Odoo 17. opw-3815275 Forward-Port-Of: o
Original PR description
## Before this commit: Modifying a location from/to a scrap location should be restricted when there are move lines with reservation. However, starting from Odoo 17, the quantity field indicates the reserved quantity only when the move line's state is different from done. ## After this commit: Only check if there are reservation lines (move lines not in done) in the location when changing from/to a scrap location to match the behaviour before Odoo 17. opw-3815275 Forward-Port-Of: odoo/odoo#159376
The `videocall_location` was accidentally unset when synch from Google, which is not expected ### Step to reproduce 1. From from calendar view of calendar.event, click to open the form view 2. click `Add Odoo meeting` to set discuss videocall location 3. save to create new calendar.event record 4. wait for synch to be done 5. recheck the field `videocall_location` to find its value False ### After this PR The discuss videocall location is no longer overriden with False --- I
Original PR description
The `videocall_location` was accidentally unset when synch from Google, which is not expected ### Step to reproduce 1. From from calendar view of calendar.event, click to open the form view 2. click `Add Odoo meeting` to set discuss videocall location 3. save to create new calendar.event record 4. wait for synch to be done 5. recheck the field `videocall_location` to find its value False ### After this PR The discuss videocall location is no longer overriden with False --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157939
When a background video and an animation coming from the left or the right are on a page at the same time, there sometimes is a horizontal scrollbar that appears for no reason. It can happen at any screen size but more frequently near 1000px and below. This issue seems to happen on Chrome only. It seems to be a race condition between the calls to the `_adjustIframe` function in the `backgroundVideo` public widget. Indeed, this function is called when the video is added in the DOM and each tim
Original PR description
When a background video and an animation coming from the left or the right are on a page at the same time, there sometimes is a horizontal scrollbar that appears for no reason. It can happen at any…
When a background video and an animation coming from the left or the right are on a page at the same time, there sometimes is a horizontal scrollbar that appears for no reason. It can happen at any screen size but more frequently near 1000px and below. This issue seems to happen on Chrome only. It seems to be a race condition between the calls to the `_adjustIframe` function in the `backgroundVideo` public widget. Indeed, this function is called when the video is added in the DOM and each time the screen is resized. When an animation is played, it triggers a resize of the window when it is over, which therefore calls `_adjustIframe`. When the animation comes from the right/left of the screen, the animated element is translated from outside the page; the page width is therefore bigger but its overflow is prevented. When the video is loaded, the loading placeholder is removed. Depending on the time it takes to it to fully load, if the animation ends before it, the iframe is adjusted before the placeholder removal, leaving the iframe wrongly adjusted when it is finally removed. Note that it is hypothetical, as everything refreshes when inspecting the DOM, making the scrollbar disappear. But this proves that no element is really overflowing, so it seems to be a value refreshing issue. This commit adds a call to `_adjustIframe` when the video has loaded, to make sure its dimensions are recomputed/refreshed, preventing the scrollbar to appear. Steps to reproduce: - Drop a "Text-Image" snippet. - Set a background video to it. - Add the "Fade In-Right" animation to the image column. - Save and then resize down the screen to 1000px or below. - Refresh. => When the video is loaded, a horizontal scrollbar may appear. If not, refresh until it does. opw-3487117 Forward-Port-Of: odoo/odoo#159193
In Settings>Inventory>Operations enable "Batch Transfers" Create a [NonTrackedProd] product: - Product Type: Storable Product - Tracking: No tracking Create a [TrackedProd] product: - Product Type: Storable Product - Tracking: By Lot Create and confirm two POs with: - Prod [NonTrackedProd] qty 1 - Prod [TrackedProd] qty 1 Open Barcode Scanning app Select "Batch Transfers" Create a new batch with the incoming transfers from the POs Set only the [NonTrackedProd] lines as done an
Original PR description
In Settings>Inventory>Operations enable "Batch Transfers" Create a [NonTrackedProd] product: - Product Type: Storable Product - Tracking: No tracking Create a [TrackedProd] product: - Product Type: Storable Product - Tracking: By Lot Create and confirm two POs with: - Prod [NonTrackedProd] qty 1 - Prod [TrackedProd] qty 1 Open Barcode Scanning app Select "Batch Transfers" Create a new batch with the incoming transfers from the POs Set only the [NonTrackedProd] lines as done and validate Issue: Error will block validation "You need to supply a Lot/Serial number for products" The system should let the user validate the operation and create a backorder instead of blocking the user opw-3777701 Forward-Port-Of: odoo/odoo#158330
Activate "Reception Report" feature Create a SO for a storable product, confirm. Create a PO for the same product. Confirm the PO and check the delivery, open the "Allocation" report Assign the Product to the delivery of the SO. Go back to the PO and cancel the order, delivery of the SO will be cancelled. Issue: Currently the user cannot modify this behavior as the `propagate_cancel` checkbox is unaccessible opw-3733512 Forward-Port-Of: odoo/odoo#159782 Forward-Port-Of: odoo/odoo#15
Original PR description
Activate "Reception Report" feature Create a SO for a storable product, confirm. Create a PO for the same product. Confirm the PO and check the delivery, open the "Allocation" report Assign the Product to the delivery of the SO. Go back to the PO and cancel the order, delivery of the SO will be cancelled. Issue: Currently the user cannot modify this behavior as the `propagate_cancel` checkbox is unaccessible opw-3733512 Forward-Port-Of: odoo/odoo#159782 Forward-Port-Of: odoo/odoo#158587
**Current behavior before PR:** An extra 'on' indicator was incorrectly displayed in chatter while creating a new record, leading to UI display issues. **Desired behavior after PR is merged:** Resolved the issue where the extra 'on' indicator was not properly displayed during new record creation. Task-3826569 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159606
Original PR description
**Current behavior before PR:** An extra 'on' indicator was incorrectly displayed in chatter while creating a new record, leading to UI display issues. **Desired behavior after PR is merged:** Resolved the issue where the extra 'on' indicator was not properly displayed during new record creation. Task-3826569 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159606
Versions: ------------ saas-16.4 Steps to Reproduce: --------------- - open project - create a project and allow timesheet - open timesheet and change encoding method to days/half days - create a task in the project and set allocated time - open portal view of the task Issue: ------------ - There is no label for allocated time. Cause: ---------- - Condition was added in this commit 82a85d42c86cffcd6e96b0712c8ff9a221f25d87 to show the label if encoding method is not in days.
Original PR description
Versions: ------------ saas-16.4 Steps to Reproduce: --------------- - open project - create a project and allow timesheet - open timesheet and change encoding method to days/half days - create a task in the project and set allocated time - open portal view of the task Issue: ------------ - There is no label for allocated time. Cause: ---------- - Condition was added in this commit 82a85d42c86cffcd6e96b0712c8ff9a221f25d87 to show the label if encoding method is not in days. Fix: -------- - We apply the label for both encoding method of timesheet. task-3761269 Forward-Port-Of: odoo/odoo#159939 Forward-Port-Of: odoo/odoo#156449
Current behavior: After this refactor https://github.com/odoo/odoo/pull/142566 the use_proxy became undefined. And so the pos is not able to connect to the proxy and use the printer connected to the IoT Box. Steps to reproduce: - Install the PoS IoT module - Configure the IoT Box with a printer - Select the printer from the IoT Box in the PoS configuration - Try to print a receipt - Nothing happens, it only try to print via the browser print popups Note: There was also an issue in t
Original PR description
Current behavior: After this refactor https://github.com/odoo/odoo/pull/142566 the use_proxy became undefined. And so the pos is not able to connect to the proxy and use the printer connected to the IoT Box. Steps to reproduce: - Install the PoS IoT module - Configure the IoT Box with a printer - Select the printer from the IoT Box in the PoS configuration - Try to print a receipt - Nothing happens, it only try to print via the browser print popups Note: There was also an issue in the StatusLoop that was not correctly getting the ids of the devices. This was fixed in the same commit. opw-3800437 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159298
When using the "Conditional Visibility" option for blocks that are inside a popup, you can end up with an empty popup. This was has been a limitation of the Conditional Visibility option for a while, but there is a real use case for wanting to only show a popup under certain circumstances. Adapting the option to take into account Popup seemed not stable enough as a lot of code is responsible for showing and hiding content that can be invisible, in edit mode. Therefore, a simpler solution w
Original PR description
When using the "Conditional Visibility" option for blocks that are inside a popup, you can end up with an empty popup. This was has been a limitation of the Conditional Visibility option for a while, but there is a real use case for wanting to only show a popup under certain circumstances. Adapting the option to take into account Popup seemed not stable enough as a lot of code is responsible for showing and hiding content that can be invisible, in edit mode. Therefore, a simpler solution was found. If the all children of the .oe_structure of a popup are in conditional visibility and are all hidden, then the popup will remain hidden. This change is done starting saas-16.3 as this is the version the OPW was opened with. opw-3734501 Forward-Port-Of: odoo/odoo#158303 Forward-Port-Of: odoo/odoo#157518
Versions: --------- saas-16.3 Steps to Reproduce: ------------- - open project - open project settings and mark task dependencies - open task Issue: ------ - The title is super far from the left. Cause: -------- - Every field have the same width. Fix: -------- - We fix the width of priority and state. task-3761269 Forward-Port-Of: odoo/odoo#156441
Original PR description
Versions: --------- saas-16.3 Steps to Reproduce: ------------- - open project - open project settings and mark task dependencies - open task Issue: ------ - The title is super far from the left. Cause: -------- - Every field have the same width. Fix: -------- - We fix the width of priority and state. task-3761269 Forward-Port-Of: odoo/odoo#156441
Description of the issue/feature this PR addresses: Current behavior before PR: formatsSpecs object isn't heritable, which prevents developers from adding new options to the editor --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159293 Forward-Port-Of: odoo/odoo#158703
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: formatsSpecs object isn't heritable, which prevents developers from adding new options to the editor --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159293 Forward-Port-Of: odoo/odoo#158703
Description of the issue/feature this PR addresses: In case we want to search on other fields than name or default_code, or eventually on the descriptions, we need to reverse the domain that is built using AND and OR operators from osv.expression which is something we would prefer to avoid anytime. By adding hooks to add custom domains, it allows to search on whatever extra fields we would like to search on. Current behavior before PR: Impossible to search efficiently on specific fie
Original PR description
Description of the issue/feature this PR addresses: In case we want to search on other fields than name or default_code, or eventually on the descriptions, we need to reverse the domain that is built using AND and OR operators from osv.expression which is something we would prefer to avoid anytime. By adding hooks to add custom domains, it allows to search on whatever extra fields we would like to search on. Current behavior before PR: Impossible to search efficiently on specific fields Desired behavior after PR is merged: Easy to extend the domain to search efficiently on specific fields --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159340 Forward-Port-Of: odoo/odoo#147865
**Steps to reproduce:** **OS:** Ubuntu 20.04.4 LTS with nautilus **Browser:** Google Chrome Version 123.0.6312.58 - type /file command in knowledge - select a folder and click on open - traceback occurs **Current behavior before PR:** When a user attempts to upload a folder using /file command, the processing begins, but the folder is not uploaded because the `getDataURLFromFile` return promise is not fulfilled. Additionally, there is no indication of any warnings or errors during
Original PR description
**Steps to reproduce:** **OS:** Ubuntu 20.04.4 LTS with nautilus **Browser:** Google Chrome Version 123.0.6312.58 - type /file command in knowledge - select a folder and click on open - traceback occurs **Current behavior before PR:** When a user attempts to upload a folder using /file command, the processing begins, but the folder is not uploaded because the `getDataURLFromFile` return promise is not fulfilled. Additionally, there is no indication of any warnings or errors during the folder upload process. **Desired behavior after PR is merged:** If a user attempts to upload a folder instead of a file using the /file command, it results in an error message in the toaster notification. task-3690847 Forward-Port-Of: odoo/odoo#159755 Forward-Port-Of: odoo/odoo#151755
**Current behavior before PR:** Long user names in direct messaging search are not wrapped, leading to UI display issues. **Desired behavior after PR is merged:** Resolved the issue where long user names were not properly wrapped in direct messaging search. Now, when a user name exceeds the allotted space, it is truncated. Task-3748791 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#158769
Original PR description
**Current behavior before PR:** Long user names in direct messaging search are not wrapped, leading to UI display issues. **Desired behavior after PR is merged:** Resolved the issue where long user names were not properly wrapped in direct messaging search. Now, when a user name exceeds the allotted space, it is truncated. Task-3748791 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#158769
Adds Mauritius localization, includes: - Chart of accounts - Taxes - Fiscal positions - Default settings, including invoice customization. task-3631730 Forward-Port-Of: odoo/odoo#156888
Original PR description
Adds Mauritius localization, includes:
- Chart of accounts
- Taxes
- Fiscal positions
- Default settings, including invoice customization.
task-3631730
Forward-Port-Of: odoo/odoo#156888Resolved issues and error corrections
This change corrects spreadsheet dashboard and template files where pivot function names had been renamed unnecessarily or incorrectly. It helps keep dashboards working as expected while relying on the existing client-side upgrade process to handle function name updates automatically.
Original PR description
Partial revert of a6d2b0dc in which pivot functions were renamed. However, some were badly renamed in dashboard json files. It turns out we didn't even had to rename the functions in json files as the (client-side) upgrade script already takes care of that. Task: 3837323
Spreadsheet formulas now handle empty cells more consistently by storing them as empty values instead of text. This reduces the risk of incorrect formula behavior and makes spreadsheet data processing more reliable.
Original PR description
In previous commits we were able to change the structure of the formula evaluation payload so that the structure corresponds to the structure of an evaluated cell. This change greatly simplifies the reading of data from a cell when a formula need it. However, the data read from the cells is in some cases modified before being used by the formulas: This is particularly the case for empty cells which are saved as an empty string value, while the value is transformed into null during evaluation. This commit corrects this by directly recording the null value on empty cells. Task: 3685074
Miscellaneous changes
…when opening journal statements When opening journal, a check is done to update the bank sync state It is not possible to update the state without accounting manager access rights Introducing a skip for non account managers to allow opening the journal. Furthermore, non-managers can't see the online sync anyway so we don't update it until a manager opens the journal. opw-3800147 Forward-Port-Of: odoo/enterprise#59706
Original PR description
…when opening journal statements When opening journal, a check is done to update the bank sync state It is not possible to update the state without accounting manager access rights Introducing a skip for non account managers to allow opening the journal. Furthermore, non-managers can't see the online sync anyway so we don't update it until a manager opens the journal. opw-3800147 Forward-Port-Of: odoo/enterprise#59706
Expect value for test without demo data wasn't changed in this PR :odoo/enterprise#50794 Fixed with this commit. task: 3837296 Forward-Port-Of: odoo/enterprise#59659
Original PR description
Expect value for test without demo data wasn't changed in this PR :odoo/enterprise#50794 Fixed with this commit. task: 3837296 Forward-Port-Of: odoo/enterprise#59659
When trying to import a bill that sometimes did not had TasaOCuota attribute. This resulted in a crash of a failed float parse Now when this happens, a message in the chatter is created and the tax_id is ignored task:3777664 Forward-Port-Of: odoo/enterprise#59572 Forward-Port-Of: odoo/enterprise#58812
Original PR description
When trying to import a bill that sometimes did not had TasaOCuota attribute. This resulted in a crash of a failed float parse Now when this happens, a message in the chatter is created and the tax_id is ignored task:3777664 Forward-Port-Of: odoo/enterprise#59572 Forward-Port-Of: odoo/enterprise#58812
Input type and salary attachment type should match the rule name task-3835119 Forward-Port-Of: odoo/enterprise#59616 Forward-Port-Of: odoo/enterprise#59569
Original PR description
Input type and salary attachment type should match the rule name task-3835119 Forward-Port-Of: odoo/enterprise#59616 Forward-Port-Of: odoo/enterprise#59569
With an Ecuador company setup Create a bill adding: - Ecuador partner - Bill Date - Document Number (ex. 001-001-123456789) - Payment Method - a bill line with tax "12% 510 01" Post the bill Hit 'Add witholding' In the witholding widget: - Add a line with tax "10% WH" - Add a second line with tax "10% WH" Issue: second line base amount will be same as first, while it should use the remaining withholding base amount opw-3763838 Forward-Port-Of: odoo/enterprise#57605
Original PR description
With an Ecuador company setup Create a bill adding: - Ecuador partner - Bill Date - Document Number (ex. 001-001-123456789) - Payment Method - a bill line with tax "12% 510 01" Post the bill Hit 'Add witholding' In the witholding widget: - Add a line with tax "10% WH" - Add a second line with tax "10% WH" Issue: second line base amount will be same as first, while it should use the remaining withholding base amount opw-3763838 Forward-Port-Of: odoo/enterprise#57605
* With no demo data, the current user does not have a timezone set. As the default value of appointment_tz is based on that, it leads to an error. We now set manually the appointment_tz for the appointment type created. * Remove the use of demo data (Mitchell Admin and Joe Willis) for test tour. Forward-Port-Of: odoo/enterprise#59739
Original PR description
* With no demo data, the current user does not have a timezone set. As the default value of appointment_tz is based on that, it leads to an error. We now set manually the appointment_tz for the appointment type created. * Remove the use of demo data (Mitchell Admin and Joe Willis) for test tour. Forward-Port-Of: odoo/enterprise#59739
In [1], dropdowns were updated and it impacted the properties field edition: - the field type images in dark mode were not properly colored anymore (too dark). This commit fixes the issue by adding a class on the field type selection popover. [1]: https://github.com/odoo/odoo/commit/7b7a2613901de20791d111a8efc8e98c226f39ad task-3834506 Forward-Port-Of: odoo/enterprise#59566
Original PR description
In [1], dropdowns were updated and it impacted the properties field edition: - the field type images in dark mode were not properly colored anymore (too dark). This commit fixes the issue by adding a class on the field type selection popover. [1]: https://github.com/odoo/odoo/commit/7b7a2613901de20791d111a8efc8e98c226f39ad task-3834506 Forward-Port-Of: odoo/enterprise#59566
This ensures the Balance Sheet is balanced. taskid: 3060790 Forward-Port-Of: odoo/enterprise#59140
Original PR description
This ensures the Balance Sheet is balanced. taskid: 3060790 Forward-Port-Of: odoo/enterprise#59140
- saas-16.3 ### Steps to reproduce: -install the project and timesheet app. -open the project app, create a project, and add a task to it. -add a timesheet a week before from current date in the created task. -now open the timesheet app in grid view. -the created project and task are in italic font. -the last letter of the project and task is slightly cut. ### Issue: The last letter of the string is slightly cut in grid view. ### Cause: The dedicated space allowed for normal t
Original PR description
- saas-16.3 ### Steps to reproduce: -install the project and timesheet app. -open the project app, create a project, and add a task to it. -add a timesheet a week before from current date in the created task. -now open the timesheet app in grid view. -the created project and task are in italic font. -the last letter of the project and task is slightly cut. ### Issue: The last letter of the string is slightly cut in grid view. ### Cause: The dedicated space allowed for normal text is not sufficient for the Italic so the last letter was slightly cut. ### Solution: Provide enough space for italic string. Task-3749072 Forward-Port-Of: odoo/enterprise#59802 Forward-Port-Of: odoo/enterprise#57000
Before this commit, scanning a source location then update a product's line by pressing the +1 qty button will update the quant's location. The issue is: we can't edit source of an existing quant. How to reproduce: - Activate storage locations settings; - Oo to Inventory > Opterations > Physical Inventory; - Select all lines and press "Request a count" assigned to mitchel admin; - Go to Barcode in Inventory Adjustments; - Scan shelf1 (barcode is 2601892); - Click on existing line from
Original PR description
Before this commit, scanning a source location then update a product's line by pressing the +1 qty button will update the quant's location. The issue is: we can't edit source of an existing quant. How to reproduce: - Activate storage locations settings; - Oo to Inventory > Opterations > Physical Inventory; - Select all lines and press "Request a count" assigned to mitchel admin; - Go to Barcode in Inventory Adjustments; - Scan shelf1 (barcode is 2601892); - Click on existing line from WH/Stock then press +1 :arrow_right: The line's location is updated to Shelf 1, it shouldn't happen. OPW-3792605 Forward-Port-Of: odoo/enterprise#59483 Forward-Port-Of: odoo/enterprise#58427
Planning improvement: - Notify the user when no match is found while using auto plan from a shift. Steps: ----------- - Install planning - Create employee and set role - Open Planning Gantt - Create a new shift - Click on the auto plan issue: ------- dict is returned without value. {'open_shift_assigned': []} task-3774045 Forward-Port-Of: odoo/enterprise#59717 Forward-Port-Of: odoo/enterprise#58046
Original PR description
Planning improvement:
- Notify the user when no match is found while using auto plan from a shift.
Steps:
-----------
- Install planning
- Create employee and set role
- Open Planning Gantt
- Create a new shift
- Click on the auto plan
issue:
-------
dict is returned without value.
{'open_shift_assigned': []}
task-3774045
Forward-Port-Of: odoo/enterprise#59717
Forward-Port-Of: odoo/enterprise#58046### Steps to reproduce * install `l10n_mx_edi` * switch to a Mexican company * create a down payment from a sales order * confirm and print the down payment We expect the down payment line to have the UNSPSC code 84111506, but we get 01010101 instead. Additionally, the Unit Code for down payments should be "ACT" ### Cause Down payments aren't products anymore, so we don't have access to their `unspsc_code_id` property. opw-3821724 Forward-Port-Of: odoo/enterprise#59334
Original PR description
### Steps to reproduce * install `l10n_mx_edi` * switch to a Mexican company * create a down payment from a sales order * confirm and print the down payment We expect the down payment line to have the UNSPSC code 84111506, but we get 01010101 instead. Additionally, the Unit Code for down payments should be "ACT" ### Cause Down payments aren't products anymore, so we don't have access to their `unspsc_code_id` property. opw-3821724 Forward-Port-Of: odoo/enterprise#59334
Steps to reproduce: - Set up DHL shipping - Create Sale order add dhl shipping and validate the delivery Fix: set the correct shipper and receiver referrence opw-3775347 Forward-Port-Of: odoo/enterprise#59716 Forward-Port-Of: odoo/enterprise#59627
Original PR description
Steps to reproduce: - Set up DHL shipping - Create Sale order add dhl shipping and validate the delivery Fix: set the correct shipper and receiver referrence opw-3775347 Forward-Port-Of: odoo/enterprise#59716 Forward-Port-Of: odoo/enterprise#59627
This update adds dark mode support to Odoo's offline page, providing a more comfortable viewing experience when the application is unavailable. Users will no longer experience harsh bright screens when the offline page appears, improving overall user experience during downtime.
Original PR description
Tired of getting flashbang every time this screen pops up 💫 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update adjusts performance test thresholds for the Appointment HR module to account for a change in how website menus are cached. When the Help Desk module is installed, the menu now contains special links that prevent caching, resulting in more database queries. The fix increases the acceptable query count in tests to reflect this new behavior.
Original PR description
[This first commit] fixed an issue with the website menu cache. The menu is not cached anymore if there is a record like URL in the it. When `website_helpdesk` module is installed, since `saas-16.3`, the menu contains a record like URL which disable the menu cache and increase the number of queries. The solution is to increase the max number of queries even if a better solution would be to remove the `Help` link from the menu but we can't do that because `appointment_hr` doesn't depend on `website`. [This first commit]: https://github.com/odoo/odoo/commit/43576cd424b6d0fc7da01142b5e6550e371ad1ff runbot-60956 runbot-59981 Forward-Port-Of: odoo/enterprise#59618
A ticket field was incorrectly appearing in the timesheet list when viewing support tickets with timesheet tracking enabled. This fix removes the duplicate field to match the expected behavior and provide a cleaner user interface.
Original PR description
Before this commit, the ticket field is displayed in the sublist view of timesheet when the user is in ticket form view with timesheets feature enabled. This commit hides the ticket field as it was the case base. issue found during the testing of task-2276015
This update resolves a visual issue where the comment box was being incorrectly highlighted when signing reports in the Field Service module. The fix removes unnecessary styling that was causing the unwanted highlight effect, improving the user experience when completing and signing worksheets.
Original PR description
17.0 Steps to reproduce: - install field service - check worksheet option from setting in field service - complete worksheet of any task and click on sign report - click on sign button on portal Issue: - comment box is getting highlight Solution: - remove the position relative styling from comment box Task:3770835
This fix corrects the layout spacing in the project task view when task dependencies are enabled. The title field was appearing too far from the left edge because all fields had equal width. The fix adjusts the width of the priority and state fields to restore proper alignment and improve the visual appearance of the task display.
Original PR description
Versions: --------- saas-16.3 Steps to Reproduce: ------------- - open project - open project settings and mark task dependencies - open task Issue: ------ - The title is super far from the left. Cause: -------- - Every field have the same width. Fix: -------- - We fix the width of priority and state. task-3761269 Forward-Port-Of: odoo/odoo#156441
This update fixes test failures in the product variants feature that occurred when running tests without demo data. The fix ensures that variant-related tests run reliably in all environments, improving the stability of the product module's testing process.
Original PR description
Some tests on dynamic variants mechanism didn't pass on test without demo data due to odoo/odoo#143543. Forward-Port-Of: odoo/odoo#159818 Forward-Port-Of: odoo/odoo#159709
This update fixes a display issue in the direct messaging search feature where long user names were not properly wrapped, causing UI problems. The fix ensures that user names that exceed the available space are now truncated appropriately, improving the overall user experience and interface appearance.
Original PR description
**Current behavior before PR:** Long user names in direct messaging search are not wrapped, leading to UI display issues. **Desired behavior after PR is merged:** Resolved the issue where long user names were not properly wrapped in direct messaging search. Now, when a user name exceeds the allotted space, it is truncated. Task-3748791 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#158769