Monday, December 18, 2023
13 changes · master
Enhancements to existing features
Barcode scanning in the web interface now uses a more efficient decoding method for repeated scans. This can make continuous scanning smoother and reduce unnecessary processing without changing how users scan barcodes.
Original PR description
In the ZXing library, the documentation for the decode method says : > This version of decode honors the intent of Reader.decode(BinaryBitmap) in > that it passes null as a hint to the decoders. However, that makes it > inefficient to call repeatedly. Use setHints() followed by decodeWithState() > for continuous scan applications. As we already use `setHints()`, adapting the decoding method to `decodeWithState()` can provide a potential efficiency gain. task-3600472 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Invalid form fields now get a light warning background, making data entry errors more visible. This helps users quickly identify and correct mistakes, especially in tables with many rows or related records.
Original PR description
When fields are invalid, it can sometimes be difficult to notice especially in x2many table. This commit applies a light danger background on the invalid fields making them easier to spot. task-3506930 | Before | After | | ---- | ---- | | <img width="1094" alt="image" src="https://github.com/odoo/odoo/assets/118886338/1056223a-9dd8-42f1-9833-6a0514a26720">| <img width="1275" alt="image" src="https://github.com/odoo/odoo/assets/118886338/19a5d3ac-bb75-4ca2-b120-f9c66c474ab7">| --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Discuss conversations are now assigned to their sidebar categories automatically instead of being sorted after updates. This should make the sidebar handling more efficient and reliable without changing how users interact with Discuss or Live Chat.
Original PR description
*: im_livechat. Before this commit, discuss sidebar categories were filled by listening to thread updates. This is suboptimal since thread types never change. This commit make use of the discuss record inverses to assign the thread to its category automatically. part of task-3640730 enterprise: https://github.com/odoo/enterprise/pull/52888
When a contact is selected for an SMS, the recipient phone number is now filled in automatically. This reduces manual entry, saves time, and helps avoid mistakes when sending messages.
Original PR description
Automatically fetch the number when Contact is set. task-3537546 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
Timesheet reporting now lets users group employee timesheet data by customer. This makes it easier for managers to review time spent per client and understand customer-related workload without extra manual analysis.
Original PR description
Improve added group by partner in reporting in timesheet. - Before this commit there was no group by partner in reporting by employee in timesheet app. - In this commit group by added in timesheet app. task-3512452
This update removes an unused internal method from the base user management area. It helps keep the system code cleaner and easier to maintain, with no expected impact on day-to-day users.
Original PR description
Introduced at 774ea74c38
Mexico HR now uses the existing employee social security number field instead of keeping a separate Mexico-specific field. This reduces duplicate data entry and keeps employee records more consistent across the system.
Original PR description
- Remove l10n_mx_nss from hr.employee model since in that model already exists the field ssnid to save the social security number so it is not necessary to add another field just for Mexico. - Add ssnid field to the employee form instead of l10n_mx_nss. Original PR from Vauxoo: https://github.com/odoo/odoo/pull/145873 that we took on to add the required upgrade script.
The Create Project option on sales orders is now placed in the action menu instead of directly on the sales order screen. This reduces confusion by making it clearer that projects are normally created automatically, while still keeping the manual option available when needed.
Original PR description
This PR moves the 'create project' button from the SO view to the action menu. This change is done because having the button directly on the SO view leads people to believe that they have to manually create a project when it is automatic. The SO view was changed to remove the button, and it was moved to the action menu. The action_create_project() method was also changed to return a danger display notification in the case where creating a project for the SO is not allowed. task-3612993
The Mexican HR employee form now uses Odoo's existing social security number field instead of a separate Mexico-specific field. This avoids duplicate employee data and keeps social security information in one standard place.
Original PR description
- Remove l10n_mx_nss from hr.employee model since in that model already exists the field ssnid to save the social security number so it is not necessary to add another field just for Mexico. - Add ssnid field to the employee form instead of l10n_mx_nss. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds automated checks to ensure planning shifts keep their linked project, task, and sales order details when an archived employee's shifts are converted into open shifts. It also verifies that newly created resources receive an initials-based avatar, helping preserve clear scheduling information and resource identification.
Original PR description
This commit adds some tests for checking those behaviours :
- When an employee is archived, the project, task, SOL should be
copied when converting his shifts into open shifts
- When a resource is creatly on the fly, an avatar with their
initials should be automatically generated
taskid:3387301The worksheet template field on field service tasks is now hidden until a customer is selected and worksheets are enabled. This reduces confusion for project users by only showing the setting when it can actually be used.
Original PR description
Before these commit: When worksheet is enable and customer field is empty in project task, worksheet template field is visible in project task which confuses the project user where they still do not see the worksheet and when changing worksheet template field they need to select the customer field. After these commit: Now worksheet is enable and customer field is selected then worksheet template field is visible to project user in project task , and if customer field is not selected then worksheet template field will not visible to project user. task-3494496
WhatsApp conversation threads are now automatically placed in the appropriate Discuss sidebar category. This makes it easier for users to find and manage WhatsApp conversations alongside other discussions without extra manual organization.
Original PR description
part of task-3640730 community: https://github.com/odoo/odoo/pull/146484
The Indian GSTR-1 tax report now highlights common compliance issues before filing, such as incorrect tax use, missing or mismatched HSN codes, and invalid unit quantity codes. This helps businesses catch data problems earlier and reduce the risk of GST filing errors.
Original PR description
In this PR: ================================== Added new warnings in tax report for GSTR-1 -Intrastate transaction must not have IGST tax -Interstate transaction must not have SGST or CGST as tax -Products must have HSN code -Products having HSN code starting with '99' must have type as 'Service' -Products having type as 'Service' must have HSN code starting with '99' -UQC code must be as per Indian GST standards task-3558902