Monday, October 28, 2024
23 changes · master
Enhancements to existing features
Account reports now support broader keyboard navigation, helping users move through filters, report lines, and actions more efficiently without relying on the mouse. This makes financial reporting workflows faster and more accessible for users who prefer or need keyboard-driven interaction.
Original PR description
This PR enhances the keyboard navigation functionality in account reports, allowing users to perform various actions more efficiently using keyboard shortcuts. For a full list of shortcuts, please refer to the [Documentation](https://docs.google.com/spreadsheets/d/11kNokL51XO8ZoOKBTLMNlIdECmtkLzVpbD1Xa9-Wt9Q/edit?usp=sharing) Task ID: 3769944
The Sign app has been updated to work with a newer PDF viewing engine. This helps keep document preview and signing flows reliable and aligned with current PDF handling improvements.
Original PR description
This commit adapts some code to follow the changes made in PDF.js Changelogs: * https://github.com/mozilla/pdf.js/releases/tag/v4.4.168 * https://github.com/mozilla/pdf.js/releases/tag/v4.5.136 * https://github.com/mozilla/pdf.js/releases/tag/v4.6.82 * https://github.com/mozilla/pdf.js/releases/tag/v4.7.76 task-4255281
The timesheet leaderboard now labels totals with the relevant month abbreviation, making it clearer which period the figures refer to. This small wording improvement helps users interpret leaderboard results more quickly and reduces ambiguity.
Original PR description
- Change "total" to "timesheets [month abbreviation]". task-3906433
This update renames an internal controller setting from “json” to “jsonrpc” to better reflect how Odoo web requests work. It does not change how users or integrations call these features, but it reduces confusion for developers and helps prevent future misconfiguration.
Original PR description
The json type is actually Odoo-RPC over Json-RPC. The "type='json'" name has been a source of confusion for years now. Fix it. It changes nothing to the way those controller are called. It only changes the way those controllers should be defined in the source code. New occurences of `@route(type='json')` are going to raise an error for an unknown controller type. If you want a cross-version compatible thing you can do: ```py @route(type='json' if odoo.release.version_info < (18, 0) else 'jsonrpc') ``` or ```py @route(type=odoo.http.JsonRPCDispatcher.routing_type) ``` A upgrade-code script exists '18.1-02-route-jsonrpc.py', use it via the new command line: ./odoo-bin code_upgrade. task-4257153
A new GSTR-1 section mapping field is added to customer invoice records in Indian reporting. This helps businesses compare invoice data against GSTR reporting more efficiently and improves accuracy during tax review.
Original PR description
With this PR, gstr-1 section mapping field will be added in `account.move`, enabling efficient cross-verification of user-provided data with GSTR Reporting. task-3360018
Resolved issues and error corrections
This draft update focuses on stabilizing several automated website and document workflow checks so teams can rely on them during future releases. The current visible change touches document folder rights testing, with additional tour fixes noted as in progress across website, rental, sales, eLearning, and reporting areas.
Original PR description
.test_rental_order_with_rental_product_and_sale_product_matrix, => No longer exist :TestAddToCartSnippet.test_configure_product, => Done .test_01_automatic_editor_on_new_website, => Done **.test_08_portal_tour_archived_variant_multiple_attributes**, => Trying **.test_10_multi_checkbox_attribute,** => TODO **.test_dblclick_event_from_calendar**, => TODO **.test_course_publisher_elearning_manager**, => Problem with preview Mode (sometimes in fullscreen mode and sometimes not) .test_09_website_edit_link_popover, => TODO :TestSaleTimesheetUi.test_ui, => Should be good. :TestReportSections.test_sections_tour, => TODO .test_document_folder_rights_for_multi_company_tour, => TODO .test_02_homepage_tour_every_theme => TODO
Features or functions removed from Odoo
An obsolete internal field related to model access groups was removed from the Studio export process. This cleanup reduces maintenance overhead without changing day-to-day functionality for users.
Original PR description
odoo/odoo#185501 task-2410245
Miscellaneous changes
**Current behavior:** Using the DHL delivery shipping module, if you complete a sale order's delivery and then add new product to the order and, again, validate the new delivery, the shipping chatter will be posted in all of the sale order's pickings. **Expected behavior:** The chatter should only be posted in the picking which was actually validated. **Steps to reproduce:** *Install delivery_dhl and l10n_be_hr_payroll* *Swap to My Belgian Company* *Duplicate the My Belgian Compan
Original PR description
**Current behavior:** Using the DHL delivery shipping module, if you complete a sale order's delivery and then add new product to the order and, again, validate the new delivery, the shipping chatter…
**Current behavior:** Using the DHL delivery shipping module, if you complete a sale order's delivery and then add new product to the order and, again, validate the new delivery, the shipping chatter will be posted in all of the sale order's pickings. **Expected behavior:** The chatter should only be posted in the picking which was actually validated. **Steps to reproduce:** *Install delivery_dhl and l10n_be_hr_payroll* *Swap to My Belgian Company* *Duplicate the My Belgian Company partner record, giving it new unique values where necessary (VAT, address, etc.)* 1. Create a new sale order to the copied Belgian company 2. Add some storable product and add DHL EU shipping to the order (only DHL connector working) 3. Confirm the order, and validate the delivery 4. Back on the sale order, add another order line and save 5. Validate the new delivery, see that the delivery chatter is posted on both deliveries **Cause of the issue:** The message is currently logged on `sale_id.picking_ids`. **Fix:** Change the line in question to only log the message on the currently iterated over picking, as well as any relevant, previously created ones (e.g., in a multistep route context). opw-4059145 Forward-Port-Of: odoo/enterprise#72730 Forward-Port-Of: odoo/enterprise#71441
Fix the flicker of the control panel when selecting a document. Remove the extra padding that was set around the current selection button so that its height matches the one of the other control panels buttons preventing the flicker. Task-4266281 Forward-Port-Of: odoo/enterprise#72175
Original PR description
Fix the flicker of the control panel when selecting a document. Remove the extra padding that was set around the current selection button so that its height matches the one of the other control panels buttons preventing the flicker. Task-4266281 Forward-Port-Of: odoo/enterprise#72175
before this commit, many of the url is pointing to 17.0 after this commit, the url will point to 18.0 documentation link Forward-Port-Of: odoo/enterprise#72858
Original PR description
before this commit, many of the url is pointing to 17.0 after this commit, the url will point to 18.0 documentation link Forward-Port-Of: odoo/enterprise#72858
Before this commit, since the `full_time_required_hours` field is unset on the calendar of Aaron employee, the test `/planning:TestUi.test_01_ui` fails because no progressbar is displayed for that employee in the gantt view of `planning.slot` model, meaning the employee is not supposed to work. This commit sets `full_time_required_hours` on the calendar of `Aaron` employee to display the progressbar for that employee as it was expected before the rework of flexible hours for resources. run
Original PR description
Before this commit, since the `full_time_required_hours` field is unset on the calendar of Aaron employee, the test `/planning:TestUi.test_01_ui` fails because no progressbar is displayed for that employee in the gantt view of `planning.slot` model, meaning the employee is not supposed to work. This commit sets `full_time_required_hours` on the calendar of `Aaron` employee to display the progressbar for that employee as it was expected before the rework of flexible hours for resources. runbot-99111 Forward-Port-Of: odoo/enterprise#72419
When generating either a PO or SO from one company to another, currently the commitment date of a Sale Order or the Expected Arrival of a Purchase Order are not used to generate their counter-part in the other company. This means that if you set the expected arrival of the PO in Company A to 10 days in the future, the SO generated in Company B will still try to deliver it as soon as possible, regardless of the date set. Forward-Port-Of: odoo/enterprise#72770 Forward-Port-Of: odoo/enterprise#
Original PR description
When generating either a PO or SO from one company to another, currently the commitment date of a Sale Order or the Expected Arrival of a Purchase Order are not used to generate their counter-part in the other company. This means that if you set the expected arrival of the PO in Company A to 10 days in the future, the SO generated in Company B will still try to deliver it as soon as possible, regardless of the date set. Forward-Port-Of: odoo/enterprise#72770 Forward-Port-Of: odoo/enterprise#72586
https://github.com/odoo/odoo/pull/183823 Forward-Port-Of: odoo/enterprise#72074
Original PR description
https://github.com/odoo/odoo/pull/183823 Forward-Port-Of: odoo/enterprise#72074
The groups s codes for work entry types were wrong. this commit adds the right codes for the work entry types. task-4221186 Forward-Port-Of: odoo/enterprise#71448
Original PR description
The groups s codes for work entry types were wrong. this commit adds the right codes for the work entry types. task-4221186 Forward-Port-Of: odoo/enterprise#71448
## Issue: - Tax descriptions in the field service report contain HTML tags, leading to undesirable formatting. - Tax descriptions that are empty result in `<p><br></p>` being printed. - Tax descriptions with content result in `<p>[description]</p>` being printed. ## Steps To Reproduce: - Create a field service task and add products on it. - Add a Sales Order Item that has taxes. - Print the field service report. - Notice when the taxes has no description it print `<p><br><p>`. - Notic
Original PR description
## Issue: - Tax descriptions in the field service report contain HTML tags, leading to undesirable formatting. - Tax descriptions that are empty result in `<p><br></p>` being printed. - Tax…
## Issue: - Tax descriptions in the field service report contain HTML tags, leading to undesirable formatting. - Tax descriptions that are empty result in `<p><br></p>` being printed. - Tax descriptions with content result in `<p>[description]</p>` being printed. ## Steps To Reproduce: - Create a field service task and add products on it. - Add a Sales Order Item that has taxes. - Print the field service report. - Notice when the taxes has no description it print `<p><br><p>`. - Notice when the taxes has has something in the [description] field it print `<p>[description]><p>`. ## Solution: - In the `account.tax` model, the description field was changed to an HTML field with this commit: https://github.com/odoo/odoo/commit/112c68a07b817e5e9a6c01e34a0fe7238b2eaa07 - Added `_get_description_plaintext` method to convert HTML content to plaintext using `html2plaintext`. This will also ensure compatibility for future changes to the description field. related community fix: https://github.com/odoo/odoo/pull/184053 opw-4104951 Forward-Port-Of: odoo/enterprise#72529 Forward-Port-Of: odoo/enterprise#68454
With a BE Company Setup Go to Documents > Configuration > Settings - Enable Accounting (Centralize accounting files and documents) - Open Journals and synchronize the Customer Invoices journal with a workspace Create an invoice Click Send&Print - Check "BIS Billing 3.0" - Send the message, the invoice will now have 2 attachments: pdf and xml Check the documents workspace Issue: Only the pdf is present This occurs because of the conditions needed to create the document.
Original PR description
With a BE Company Setup Go to Documents > Configuration > Settings - Enable Accounting (Centralize accounting files and documents) - Open Journals and synchronize the Customer Invoices journal with a workspace Create an invoice Click Send&Print - Check "BIS Billing 3.0" - Send the message, the invoice will now have 2 attachments: pdf and xml Check the documents workspace Issue: Only the pdf is present This occurs because of the conditions needed to create the document. When we send the message we create the attachment but the move does not have attachment_ids set yet, so we fail to assign the first one. In this phase we just need to link the xml as the pdf will be registered when assigned as main attachment of the move opw-4088910 Forward-Port-Of: odoo/enterprise#72518 Forward-Port-Of: odoo/enterprise#69085
The shared_sign_request_tour, attempts to open some template and then click on some sign item. However it fails when it tries to click on the sign item, because it's not found. This happened because the tour sometimes open the wrong sign template (one with no items). This commit aims to fix the issue by archiving other sign templates when testing this flow. fixes runbot-98036 Forward-Port-Of: odoo/enterprise#72477
Original PR description
The shared_sign_request_tour, attempts to open some template and then click on some sign item. However it fails when it tries to click on the sign item, because it's not found. This happened because the tour sometimes open the wrong sign template (one with no items). This commit aims to fix the issue by archiving other sign templates when testing this flow. fixes runbot-98036 Forward-Port-Of: odoo/enterprise#72477
This is a complement of previous fix: https://github.com/odoo/enterprise/commit/9b2d9508745fb1b00e42c8d729d01ad7ae1b4b85 Add the company of the move in the context as it is possible that the company of the move and the current company are different. Related community PR: https://github.com/odoo/odoo/pull/185096 Forward-Port-Of: odoo/enterprise#72746 Forward-Port-Of: odoo/enterprise#71725
Original PR description
This is a complement of previous fix: https://github.com/odoo/enterprise/commit/9b2d9508745fb1b00e42c8d729d01ad7ae1b4b85 Add the company of the move in the context as it is possible that the company of the move and the current company are different. Related community PR: https://github.com/odoo/odoo/pull/185096 Forward-Port-Of: odoo/enterprise#72746 Forward-Port-Of: odoo/enterprise#71725
Steps to reproduce the bug: - Create a storable product “P1”: - Tracked with SN - Create a BoM: - no need to component - Add an operation “OP1” with steps - Control by product - Create a manufacturing order for one unit of P1 - Confirm the MO - Go to the shop floor and process “OP1” - Validate the MO - Go to the SN of P1 Problem: The quality check smart button is not displayed, while the SN is linked to a QC. opw-4189396 Forward-Port-Of: odoo/e
Original PR description
Steps to reproduce the bug:
- Create a storable product “P1”:
- Tracked with SN
- Create a BoM:
- no need to component
- Add an operation “OP1” with steps
- Control by product
- Create a manufacturing order for one unit of P1
- Confirm the MO
- Go to the shop floor and process “OP1”
- Validate the MO
- Go to the SN of P1
Problem:
The quality check smart button is not displayed, while the SN is linked to a QC.
opw-4189396
Forward-Port-Of: odoo/enterprise#72693The commit intends to add tests to newly introduced functionality of marketing automation where we added whatsapp. Forward-Port-Of: odoo/enterprise#71346
Original PR description
The commit intends to add tests to newly introduced functionality of marketing automation where we added whatsapp. Forward-Port-Of: odoo/enterprise#71346
- Some are out of date/module was added since the last batch export. - Some were incorrectly manually modified - Also some cleanup of the `code` comments Forward-Port-Of: odoo/enterprise#72821
Original PR description
- Some are out of date/module was added since the last batch export. - Some were incorrectly manually modified - Also some cleanup of the `code` comments Forward-Port-Of: odoo/enterprise#72821
Add a compound index on (`res_model`, `res_id`) to support domains searching documents based on those criteria, similarly to `ir_attachment_res_idx` on `ir.attachment`. Forward-Port-Of: odoo/enterprise#72824 Forward-Port-Of: odoo/enterprise#72426
Original PR description
Add a compound index on (`res_model`, `res_id`) to support domains searching documents based on those criteria, similarly to `ir_attachment_res_idx` on `ir.attachment`. Forward-Port-Of: odoo/enterprise#72824 Forward-Port-Of: odoo/enterprise#72426
When real time measure is not linked to a device (scale), no need to add the 'Take measure' label as the user must input a value Forward-Port-Of: odoo/enterprise#72763
Original PR description
When real time measure is not linked to a device (scale), no need to add the 'Take measure' label as the user must input a value Forward-Port-Of: odoo/enterprise#72763