Daily updates from Odoo
Navigate
Branch
Monday, March 6, 2023
18 changes
Enhancements to existing features
Users with write access can now create a clone of an existing Knowledge article directly from the article view. This helps teams quickly create similar articles while preserving key details such as the parent location, properties, and status.
Original PR description
This commit is adding a new button to the article view for users that can write on specific articles. We are adding the possibility for the user to clone an existing article if he has write access on it. By cloning an article the clone keeps the same parent, the same property values, the item status and many more in addition of the fields copied when using the `action_make_private_copy` method. This is useful when a user wants to create many articles that are similar: he creates the first one and then creates one or more clones that he slightly modifies corresponding to its needs. task-3186202
The Knowledge app gets a cleaner and more practical interface for creating article indexes, managing article properties, and browsing article cards. These changes make it easier for users to organize knowledge content, find key actions, and work with embedded views in wide layouts.
Original PR description
This merge applies some design and functional limprovements. - merge /index and /article_structure into a single command - rename desc of /file commande - remove vertical padding between articles in side panel - rework knowledge property panel UI and add an helper - make embbeded view wider on full width mode - review kanban card design of article items For more detail, see sub-commits.
Point of Sale users in Mexico can now enter additional fiscal details for customers and invoices directly during the sales flow. This helps collect the required information when creating invoices for current or previous POS orders, reducing follow-up work and improving compliance readiness.
Original PR description
In the POS, allow to fill the `l10n_mx_edi_fiscal_regime` and the `l10n_mx_edi_no_tax_breakdown` fields on the `PartnerDetailsEdit` window. In addition, when creating an invoice from a POS order (for the current order or for a previous order when the customer ask for an invoice), display a popup to fill the `l10n_mx_edi_usage` and the `l10n_mx_edi_cfdi_to_public` fields. task-3178954 Community: https://github.com/odoo/odoo/pull/112285
The Helpdesk and Appraisal apps now show activity records with a refreshed interface. This makes related activity information easier to review and supports a clearer day-to-day user experience.
Original PR description
This commit revamps some activity records UI in different applications. task: 3133150
Odoo now stores failed-delivery bounce emails for marketing automation messages, making it easier to understand why an email did not reach a recipient. Users can read the bounce details directly from the interface, reducing time spent troubleshooting sending issues.
Original PR description
Purpose ======= The bounce emails aren't stored in Odoo, which can complicated the debugging of the email sending. Now, we store this bounce email, and we allow the user to read it from the interface, so he can easily find the issue when an email sending fail. Specifications ============== The bounce email is stored of the mail notification for standard emails sending, and on the mailing traces when using mass mailing. Task-2116296 See odoo/odoo/pull/105923
India payroll now includes updated salary structures, salary components, and payslip reports tailored to local payroll practices. The update also adds gratuity handling, probation follow-up activities for HR managers, and improvements to payment advice navigation and usability.
Original PR description
- New added salary rule category: Base Salary, Daily Salary, Special Allowance - Create two payroll structure Structure with Provident fund Structure without Provident fund - There are add some new…
- New added salary rule category:
Base Salary, Daily Salary, Special Allowance
- Create two payroll structure
Structure with Provident fund
Structure without Provident fund
- There are add some new salary components in india payroll:
Base Salary
Daily Salary
House Rent Alloeance
Standard Deduction
Leave Travel Allowance
Bonus, Supplementary Allowance
Variable pay, GROSS
Professional Tax
Provident fund - Employee
Provident fund - Employeer
- Improve the payslip report and details payslip report based on india country
-Add Amount In Words Rs in payslip report
-Remove the busic salary row
- Contract:
- Add gratuity filed in hr.contract and use in salary rule
Ex-
Variable pay = contract.wage - contract.gratuity - BSA - (categories.DSL * 2)
- Add Probation type option in contract Types
If the contract type is Probation and the contract end date is today then the automatic activity
schedules its hr manager. It is easy for hr manager. Which employee's probation is over?
- The Payment Advice menu is set after the Dashboard menu.
- Some UI generic impermanent in Payment Advice.like status bar
task-3062183Appointment invitations now keep track of the business record they came from, so future meetings are automatically linked to the related sales lead or recruitment applicant. This makes follow-up easier by showing linked leads on appointment types and recording the connection in meeting history.
Original PR description
### Purpose Before only custom appointment type appointments were linked to leads, now we extend the feature to all category. We also link the appointment to the Applicant. ### Specification The invitation keep in memory the record from which it was created to apply it to the meetings created in the future. So we move the opportunity_id field from the `appointment.type` model into the `appointment.invite` model. We also add a stat button info showing the number of leads linked to an appointment type. ### Links task-2984657
The Chilean SII Partner Activities form now uses a cleaner page layout in Accounting configuration. This makes the screen easier to read and more consistent with other Odoo forms, with no change to business data or workflow.
Original PR description
currently for the form view of the model l10n_cl.company.activities sheet tag is not added. Accounting -> Configuration -> Chilean SII -> SII Partner Activities. adding sheet to the form view for better ui
This update makes several salary and appraisal fields available for translation. It helps companies using multiple languages provide clearer, localized HR information to employees and managers.
Original PR description
https://www.odoo.com/web#id=3159917&menu_id=4720&cids=1&action=333&active_id=1251&model=project.task&view_type=form
Resolved issues and error corrections
Demo forum posts in the Helpdesk Forum area are now assigned to the intended user instead of Odoobot. This keeps demo karma ownership accurate and avoids confusing sample data when teams review or demonstrate the feature.
Original PR description
Purpose ======= Now that we show the owner of the Karma tracking, we want to fix the demo data, so they do not belong to Odoobot. Task-2234179
The Colombian PYME balance sheet report now treats equity amounts with the correct sign. This helps ensure the balance sheet balances properly and gives businesses more reliable financial reporting.
Original PR description
When checking if the BS is balanced with a script, it seems that the equity part of the BS was wrong, all the sign were reverse. By doing the negative of the account the BS is now balanced task-id: 3041738
This fixes a minor issue in the Knowledge app's data setup process that could fail when article member information is missing. The change helps keep setup and test data generation reliable without changing normal user workflows.
Original PR description
We here fix the issue of possibly iterating over a `False` value (`get` fallback) for `article_member_ids` (from c1c275cf) by avoiding the loop altogether in this case, in favor of readability and efficiency. Task-3215864
Code cleanup and technical improvements
This internal cleanup ensures field components use the settings from the exact view element being displayed, rather than accidentally reusing settings from another matching field. This reduces the risk of inconsistent behavior in screens where the same field appears multiple times with different options.
Original PR description
This commit is to replace all uses of activeFields in Field composents by passing fieldInfos to extractProps. We will therefore retrieve the node-dependent information in the extractProps function.
Why?
This ensures that the info used is that of the correct node. Because the activeFields function contains the information from the last node that referred to the same field.
Example:
<tree>
<field name="a"/>
<field name="a" context='{'b':"yop"}'/>
</tree>
For the first field:
FieldInfo.context = {}
activeField.context = {'b':"yop"}
For the second field:
FieldInfo.context = {'b':"yop"}
activeField.context = {'b':"yop"}
Part of task: 3179751This update removes old testing support code that is no longer needed after related areas were moved to the newer interface framework. It should not change day-to-day user workflows, but helps keep the codebase simpler and easier to maintain.
Original PR description
The corresponding codebases have been converted to owl, and those patches are no longer useful.
This update renames an internal label used when working with related fields, making the code easier for Odoo teams to understand and maintain. It does not introduce new functionality or change the user experience, but helps reduce confusion for future development.
Original PR description
[REF] *: rename fieldsToFetch to relatedFields We take advantage of the change of api made in commit https://github.com/odoo/odoo/commit/145540921f2629ae188c84dee17c8d95dccdde16 to rename FieldsToFetch to relatedFields.These two commits are in the same version of odoo (16.2). FieldsToFetch is not a good name for defining the fields to be fetch for relational fields. So we decided to rename it to relatedFields. Part of Task: 3179751
Miscellaneous changes
Sign runs tests with root user which is inactive. However inactive users should never be added as followers, which is now fixed in community. This commit updates tests accordingly. Tests should probably user a real user, but trying to convert them lead to other issues in tests which require some cleaning, and which is outside the scope of this fix. Task-3046371 (Mail: Better Language Support in Composer) Backport of odoo/odoo@c9a0f3e10d179335b397778834c4b1ba34ebd2c2 Forward-Port-Of: od
Original PR description
Sign runs tests with root user which is inactive. However inactive users should never be added as followers, which is now fixed in community. This commit updates tests accordingly. Tests should probably user a real user, but trying to convert them lead to other issues in tests which require some cleaning, and which is outside the scope of this fix. Task-3046371 (Mail: Better Language Support in Composer) Backport of odoo/odoo@c9a0f3e10d179335b397778834c4b1ba34ebd2c2 Forward-Port-Of: odoo/enterprise#37834 Forward-Port-Of: odoo/enterprise#37781
Starting january 2022, Tax Authorities in Norway require tax returns to be submitted online. The easiest way to do so is to submit the tax report in a specified XML format, that needs to be implemented (done here). The current tax report in Odoo is outdated, the following PR addresses this problem: https://github.com/odoo/odoo/pull/84253 Changes: - add XML template for tax return - add XML generation model task id=2667013 Forward-Port-Of: odoo/enterprise#37134 Forward-Port-Of: odoo/
Original PR description
Starting january 2022, Tax Authorities in Norway require tax returns to be submitted online. The easiest way to do so is to submit the tax report in a specified XML format, that needs to be implemented (done here). The current tax report in Odoo is outdated, the following PR addresses this problem: https://github.com/odoo/odoo/pull/84253 Changes: - add XML template for tax return - add XML generation model task id=2667013 Forward-Port-Of: odoo/enterprise#37134 Forward-Port-Of: odoo/enterprise#23041
Currently, SCT requires the journal to be in a set of determined currencies. We want to allow using this payment method for all journals, whatever their currency. The only check that should be made is on the currency of the payment. opw-3159737 Forward-Port-Of: odoo/enterprise#37733
Original PR description
Currently, SCT requires the journal to be in a set of determined currencies. We want to allow using this payment method for all journals, whatever their currency. The only check that should be made is on the currency of the payment. opw-3159737 Forward-Port-Of: odoo/enterprise#37733