Monday, January 23, 2023
16 changes · master
Enhancements to existing features
Creating a new Knowledge article now keeps the writing area focused when users choose to add an icon or cover. This makes article setup smoother by avoiding an unnecessary interruption while users customize their content.
Original PR description
When the user creates a new article, the editor will automatically be focused. When the user clicks on the "Add icon" button or the "Add Cover" button, the user will lose the editor focus which is annoying. This commit will ensure that the user will not lose the editor focus when clicking on those buttons. task-3134527
This update removes an unused display rule in the account consolidation screens. It simplifies the setup slightly and reduces the chance of confusing or outdated behavior, with no expected change to normal user workflows.
Original PR description
before this commit, in consolidation.company_period model for the field period_id an invisible condition is added based on context key from_analysis_period, but such a key is not set in context from any where, so removing the unused invisible condition after this commit, the invisible condition is removed.
Adds automated checks to help ensure Helpdesk works correctly when multiple companies are used. This reduces the risk of setup issues by verifying that the Customer Care team is created for each company.
Original PR description
In this commit add test cases for helpdesk application following test cases are written. - multi company - check 'customer care' team create for all company. task-3012551
Resolved issues and error corrections
The subscription dashboard links for Learn More and Website now direct users to the subscription page instead of the accounting page. This helps users reach the relevant information faster and avoids confusion when exploring subscription features.
Original PR description
before this commit, on clicking learn more or website it redirect to accounting page. after this commit, it will redirect subscription page.
Features or functions removed from Odoo
Odoo is removing an old list-view field sizing option that has not worked since the list view was modernized. This cleanup reduces outdated configuration and keeps affected screens aligned with the currently supported display behavior.
Original PR description
Since the conversion of the list view to owl, the relative field size
has not been reimplemented. We have decided not to support it anymore.
So we will remove all its uses.
The relative width consists in adding a width attribute with an integer
value. This value corresponds to the weight of the field, the higher
it is, the more space the field will take. This size is only used when
the list is empty.
Example of this:
<tree>
<field ... width="2">
<field ... width="1">
</tree>
The first field will take 2x more space than the first one when the list
is empty.Code cleanup and technical improvements
The point of sale enterprise modules were updated to use the standard Odoo approach for extending screens, models, and components instead of a custom registry system. This is an internal cleanup that should make future maintenance easier and reduce onboarding complexity for developers, without changing day-to-day POS behavior for users.
Original PR description
*: l10n_de_pos_cert, l10n_de_pos_res_cert, pos_hr_mobile, pos_iot, pos_l10n_se, pos_restaurant_iot, pos_settle_due Previously, the point of sale module used a custom inheritance system for models and components. This system being non-standard, it makes it hard for newcomers to understand how to use it or for people with experience in the pos code base to understand how things are done elsewhere. The corresponding community commit removes the "registries" system from the pos modules this commit adapts enterprise code to use standard inheritance mechanisms, ie extending classes directly, and using patch to modify behaviour in place. task-3119628 Co-authored-by: Samuel Degueldre <sad@odoo.com> Community: https://github.com/odoo/odoo/pull/109928
Miscellaneous changes
Community PR: https://github.com/odoo/odoo/pull/106185 Forward-Port-Of: odoo/enterprise#36064 Forward-Port-Of: odoo/enterprise#34204
Original PR description
Community PR: https://github.com/odoo/odoo/pull/106185 Forward-Port-Of: odoo/enterprise#36064 Forward-Port-Of: odoo/enterprise#34204
This update removes a redundant database index in the event barcode area because an existing unique rule already provides the same coverage. It helps keep the system leaner and avoids unnecessary database maintenance without changing user-facing behavior.
Original PR description
- "event_registration_barcode_index" covers by "event_registration_barcode_event_uniq"
This update removes an outdated internal setting from the Planning app that is no longer needed. It helps keep the application easier to maintain without changing how users work with planning views.
Original PR description
It appears that one usage of the legacy_list js class remains in planning but is not needed, this commit removes that usage.
This update simplifies how Odoo prepares and renders email templates and composer content in several apps. It helps keep mail-related behavior more consistent and easier to maintain, with limited direct impact on day-to-day users.
### Steps to reproduce - create account groups with the following hierarchy: ``` - 10 - 101 - 1012 ``` - create one journal entry that falls into group `10` (and NOT in `101`) - create one journal entry that falls into group `1012` - make sure that no entry falls into group `101` - access the trial balance report You should be met with a traceback. opw-3120986 Forward-Port-Of: odoo/enterprise#35736
Original PR description
### Steps to reproduce
- create account groups with the following hierarchy:
```
- 10
- 101
- 1012
```
- create one journal entry that falls into group `10` (and NOT in `101`)
- create one journal entry that falls into group `1012`
- make sure that no entry falls into group `101`
- access the trial balance report
You should be met with a traceback.
opw-3120986
Forward-Port-Of: odoo/enterprise#35736Adds several fixes on the tablet view : - When either the given instruction or the comment isn't given in the step suggestion, it would print "False" in the chatter. Doesn't print those fields if they are empty. - Remove step suggestion when no BoM are linked to the workorder, as it wouldn't be recorded anywhere anyway. - When suggesting an update in step instructions with PLM installed, add a note in the chatter containing the reason and the user that made it. Those info were displayed in th
Original PR description
Adds several fixes on the tablet view : - When either the given instruction or the comment isn't given in the step suggestion, it would print "False" in the chatter. Doesn't print those fields if they are empty. - Remove step suggestion when no BoM are linked to the workorder, as it wouldn't be recorded anywhere anyway. - When suggesting an update in step instructions with PLM installed, add a note in the chatter containing the reason and the user that made it. Those info were displayed in the BoM without PLM, but lost as soon as PLM was installed. - Like #33001, but instead of trying to display the DocumentViewer, now displays also the text instruction written in the operation. - When suggesting deleting a step, add a note in the chatter of the old step containing the reason and the user that made it. Those info were displayed in the BoM without PLM, but lost as soon as PLM was installed. Forward-Port-Of: odoo/enterprise#34758
### Steps to reproduce * In `Settings > Accounting > Vendor Payments`, select any check layout and save. * Create a vendor payment of type check, and select a vendor whose address has a `street2` defined. * fill the Memo field * Confirm and print the check You should see that the memo overlaps with the address. This is an old issue (https://github.com/odoo/enterprise/pull/7829) that was reintroduced by https://github.com/odoo/odoo/pull/99837 opw-3112686 Forward-Port-Of: odoo/enterp
Original PR description
### Steps to reproduce * In `Settings > Accounting > Vendor Payments`, select any check layout and save. * Create a vendor payment of type check, and select a vendor whose address has a `street2` defined. * fill the Memo field * Confirm and print the check You should see that the memo overlaps with the address. This is an old issue (https://github.com/odoo/enterprise/pull/7829) that was reintroduced by https://github.com/odoo/odoo/pull/99837 opw-3112686 Forward-Port-Of: odoo/enterprise#35481
The previous formulation was a bit weird (e.g. "Schedule End of year party Appointment"). This view will be reworked in th next version but at least remove the "Appointment" from the view. Don't reexport the .pot just yet for those who still have the view with previous content. Forward-Port-Of: odoo/enterprise#36011
Original PR description
The previous formulation was a bit weird (e.g. "Schedule End of year party Appointment"). This view will be reworked in th next version but at least remove the "Appointment" from the view. Don't reexport the .pot just yet for those who still have the view with previous content. Forward-Port-Of: odoo/enterprise#36011
Steps to reproduce the bug: - Enable work order in mrp settings - Go to “Table top” bill of materials > operation Delete the step linked to the operation opw-3086777  Forward-Port-Of: odoo/enterprise#36040 Forward-Port-Of: odoo/enterprise#35253
Original PR description
Steps to reproduce the bug: - Enable work order in mrp settings - Go to “Table top” bill of materials > operation Delete the step linked to the operation opw-3086777  Forward-Port-Of: odoo/enterprise#36040 Forward-Port-Of: odoo/enterprise#35253
Some translations were lost when we changed to 16.0 since there is no l10n_* project for 16.0 on Transifex. Reintroduced lost translations for Arabic, German, French, Italian, Dutch and Chinese. Task: 3120894 Forward-Port-Of: odoo/enterprise#35266
Original PR description
Some translations were lost when we changed to 16.0 since there is no l10n_* project for 16.0 on Transifex. Reintroduced lost translations for Arabic, German, French, Italian, Dutch and Chinese. Task: 3120894 Forward-Port-Of: odoo/enterprise#35266