Monday, July 15, 2024
16 changes
2 changes
Enhancements to existing features
The Events page is easier to browse with clearer country indicators, better use of space in the search area, and tag counts shown directly in filter dropdowns. Visitors also see events from their current country first when country filtering is available, helping them find relevant local events faster.
Original PR description
1. Add country flag when filter option is on 2. Reduce search bar width for >lg screens 3. Show tags inside the category drop down title instead of in a separate line, for larger screen. Also add a 'All' option to clear all searched tags of that category. Task-3869922
Resolved issues and error corrections
The generate serials/lots dialog in Manufacturing now receives the correct quantity value when used from the shop floor. This prevents users from seeing an undefined Quantity Received value and avoids errors when creating lot numbers for tracked components.
Original PR description
Issue: ============================ There is an 'undefined' value for the 'Quantity Received' field in the generate lot number dialog. When attempting to generate a lot number for a component from…
Issue: ============================ There is an 'undefined' value for the 'Quantity Received' field in the generate lot number dialog. When attempting to generate a lot number for a component from the shop floor, the 'Quantity Received' field displays as 'undefined', leading to an error. Steps to Reproduce: ============================ 1. Install the 'mrp_workorder' module. 2. Create a Bill of Materials (BoM) in the Manufacturing module with manual consumption components tracked by lot. 3. Create a Manufacturing Order (MO) for the product. 4. Open the 'detailed operation' wizard for a component with lot tracking in the shop floor module. 5. Click on 'Generate Serials/Lots'. 6. Verify that the Quantity Received field displays the 'undefined' value. Resolution: ============================ Currently, the "quantity received" field displays 'undefined', causing an error when generating a lot number for a component. This issue occurred due to not getting a quantity field in the shop floor module. Added the "quantity" field to the relevant view to ensure that the "quantity received" field gets an actual quantity field value, preventing the error. Expected Result: ============================= This fix resolves the error and allows for efficient lot number generation of products in the shop floor module.
9 changes
New functionality added to Odoo
Indian Payroll now includes a Salary Register that lets businesses export employee salary information in one place. The export includes salary rules such as BASIC, HRA, and PF, along with salary structure details, making payroll reporting easier and more complete.
Original PR description
This commit adds the Salary Register in Indian Localization. With this addition, we can export the data of every employee. and that data will include, Salary Rules(BASIC, HRA, PF etc), Salary Structure etc. task-3773199
5 changes
Resolved issues and error corrections
This fix corrects a display issue where the Sign Report button was not appearing when using Worksheets without Field Service enabled. The condition that controlled the button's visibility was incorrectly requiring Field Service to be active, even though Worksheets can function independently. This change allows users to properly sign worksheet reports regardless of Field Service status.
Original PR description
Steps to reproduce: - Install "Field Service" - Open "Project" - Open the settings of a random project - Then click on the "Settings" tab - Disable "Field Service" and enable "Worksheets" - Create a new task with a worksheet - Click on start then stop and save - Click on "Sign Report" Issues: The sign button is not displayed due to the condition in the template which required previously to have `is_fsm` enabled. https://github.com/odoo/enterprise/blob/4d0a467220fba5253fb4a6f38844861d9ed4e442/industry_fsm/views/project_portal_templates.xml?plain=1#L42 opw-4032692 Forward-Port-Of: odoo/enterprise#66057
Enhancements to existing features
Pivot reporting views and related extensions now load only when needed. This should reduce initial loading work across affected apps and make everyday navigation feel faster, while keeping reporting functionality available when users open it.
Original PR description
We make the view pivot and its extensions to be lazy loaded. Task ID: `3546321`
Payment links generated from subscriptions now give customers clearer context about what they are paying for, instead of showing only a reference and amount. This reduces confusion during payment and can help customers complete subscription payments with more confidence.
Original PR description
If user generated payment link, it was very unclear, client had no idea what is he actually paying for, they only had reference and amount. See also: - https://github.com/odoo/odoo/pull/162177
The salary attachment report has been removed because the same information is now available directly in the salary attachment view. A new pivot view lets payroll users analyze salary attachment data in a more flexible way without relying on a separate report.
Original PR description
The salary attachment report was kind of pointless since we can get the same info in the salary attachment view. Added a pivot view for salary attachment to get a similar report to the one existing previously. Task: 3960990
Employee-related action menus have been simplified by moving or removing less-used options. This makes employee list and form screens easier to read and helps users find key actions in more appropriate places.
Original PR description
This Pr unclog the different hr action menu an move functionnalities in a more appropriate place to be more user firendly task-3927336 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Payroll users can now delete a batch when it has no payslips or when all linked payslips are still draft or canceled. This reduces cleanup friction while keeping completed or active payroll records protected.
Original PR description
This PR improves the batch deletion process in the hr_payroll module. Users can now delete a batch if all payslips within it are in a canceled or draft state, or if no payslips are linked to the batch. task-3964984
This update improves wording, labels, placeholders, filters, and navigation across appointment scheduling, WhatsApp templates, social posting, and marketing automation. These refinements make common screens clearer and easier to use, while also updating demo social links so examples point to valid official content.
Original PR description
Batch of small improvements like labels, design, ... See commits for more details. task-3515819
Code cleanup and technical improvements
The Web Studio report editor has been updated to work with Odoo’s newer HTML editing engine. This should make report editing more maintainable and responsive while fixing minor naming issues that could affect reliability.
This update improves the report editor in Odoo Studio by aligning it with the newer editing framework and correcting minor naming mistakes. It also makes report editing more efficient when handling document content, supporting smoother maintenance and future enhancements.
This fix improves the Field Service navigation feature by using actual addresses instead of GPS coordinates when generating navigation links. Previously, Google Maps would convert coordinates back to addresses, which could result in discrepancies. Now users will navigate to the correct address consistently.
Original PR description
Steps to reproduce: - Install "Field Service" - Open a random task - Click on "Navigate To" Issues: The link is constructed using the coordinates, however Google will convert those coordinates back to an address which will cause a potential discrepancy between the two. opw-4004846 Forward-Port-Of: odoo/enterprise#66611 Forward-Port-Of: odoo/enterprise#65893
This fix prevents demo content from the report editor from appearing in actual printed reports. Previously, when employees had empty fields (like missing resume descriptions), placeholder text from the editor would show up in printed documents instead of remaining blank. The solution introduces a new demo-only attribute so placeholder content only displays in the editor, not in real reports.
Original PR description
Steps to reproduce ================== - Install hr_skills,web_studio - Go to Employees - Open any record - Add a new resume entry without description - Save - Click on the actions gear - Print >…
Steps to reproduce ================== - Install hr_skills,web_studio - Go to Employees - Open any record - Add a new resume entry without description - Save - Click on the actions gear - Print > Print Resume => `Odoo India pvt. Ltd` is displayed in the report in place of the missing description Cause of the issue ================== With the new report editor in 16.4, some demo data have been added directly inside the report templates as default content. The assumption was that it would be displayed inside the report editor, but outside, since the field would have a value, the value would take over. The default content if displayed when the field value is falsy. In this case, the default content is used instead of the empty description. Solution ======== Introduce a new attribute, data-oe-demo, to be used inside the report editor. This doesn't have the drawbacks of the default content as we can choose to only display it inside the report editor --- [commit]: https://github.com/odoo/odoo/commit/a45c6c545ffdcee3bb50b3455884b8296e5d6a7c opw-4033434
This fix ensures that rental transfer pickings are properly created when portal or public users confirm rental orders, regardless of their user permissions. Previously, the system was checking the current user's settings instead of the database owner's settings, causing transfers to be skipped when external users placed orders. Now the system correctly uses the order creator's settings to determine whether transfers should be generated.
Original PR description
**Current behavior:** If a portal or public user causes a rental order to get confirmed, rental transfer pickings won't get created if the DB user has the setting enabled. **Expected behavior:** The transfer should be created with respect to the user of the database, not the external users. **Steps to reproduce:** 1. Enable rental transfers 2. Create a rental order to a portal user 3. In a fresh browser, open the preview link as the portal user 4. Sign & Pay for the order 5. See that no transfers got created **Cause of the issue:** We use the `env.user` to determine whether the transfers should be generated. **Fix:** Use the creator of the order to decide to create the transfer. opw-3933511
This update resolves multiple issues in the manufacturing shop floor system that were preventing proper data entry and barcode scanning. Key fixes include saving quantity and lot information during quality checks, improving the clarity of the quality check interface, correcting barcode trigger recognition, and updating the barcode PDF generation to resolve scanning problems. These changes ensure that shop floor operations run more smoothly and reliably.
Original PR description
This addresses several issues: - on 'register_consumed_materials' & 'register_byproducts' quality checks, the quantity entered and the selected lot were not saved - make this view clearer by separating the product and the other fields - 'print' & 'next' barcode triggers were sometimes capitalized, making them inoperant - fix component remaining quantity when no producing quantity has been set - generate a new pdf for barcodes: add print barcode & new ghostscript version seems to solve some erratic scanning problems task: 3987346