Friday, June 23, 2023
7 changes · master
Enhancements to existing features
Landed cost records are now sorted by recorded date with the newest entries shown first. This makes recent cost updates easier to find and review without scrolling to the bottom of the list.
Original PR description
before this commit, when creating new record in landed cost, the newly added record is coming in the last position in the tree view. after this commit, the records shown in the tree view will be sorted based on the desc order of recorded date in the landed cost. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Developers can now create inherited views without repeating the model name when it is the same as the original view. This reduces boilerplate in customizations and lowers the chance of small configuration mistakes, with no expected change for end users.
Original PR description
It slightly decreases the amount of needed boilerplate code when creating inheriting views, by simply assuming the model is the same as the inherited one.
For example,
```xml
<!-- The commented line is no longer required -->
<record id="view_partner_form" model="ir.ui.view">
<!-- <field name="model">res.partner</field> -->
<field name="inherit_id" ref="base.view_partner_form" />
<field name="arch" type="xml">
<field name="name" position="after">
<field name="id" />
</field>
</field>
</record>
```
NOTE: A similar technique is already used to guess the view type. In the same spirit, it's extended to also guess the model.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThe Point of Sale printer settings now show product categories as easy-to-read tags. This makes category selection clearer for users configuring printer rules.
Original PR description
before this commit, in pos.printer model the product_categories_ids is displayed without many2many_tags widget. after this commit, for product_categories_ids field many2many_tags widget is added Before:  After:  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Newly created employees and resources now display an avatar based on their initials instead of a generic grey placeholder. This makes employee selection fields easier to scan and gives records a more polished appearance from the moment they are created.
Original PR description
Before this commit, when the user creates new resource and employee on the fly in many2one field, the default avatar of Initial name should be set instead of placeholder (grey icon). The reason why a grey icon is displayed is because the `_compute_avatar` for employee set that icon when avatar or image is not found. This commit add default avatar of initial name when new resource and employee is created. task-3251689
This update aligns Enterprise tests with a community change that shows quick visual feedback when users switch menus before the full screen loads. It helps keep automated checks reliable while supporting a smoother perceived navigation experience.
Original PR description
The PR https://github.com/odoo/odoo/pull/124068/files changes the action and menu services so that each menu item changes will (almost) immediately displays an empty screen, to provide some quick feedback to the user, before showing the actual action, once it is loaded. As a result, a few tests have to be adapter, since the actual action is displayed a tick later in tests.
Helpdesk customer emails for ticket receipt and closure were updated with clearer wording and a more polished tone. These emails will also be automatically deleted after sending, reducing unnecessary database storage while keeping customers informed.
Original PR description
Purpose: make the 'ticket closed' email template sexier - change the 'helpdesk: ticket closed' email template as follows: - Subject: Ticket Closed - Reference 15 - Dear [Customer Name], - We would…
Purpose: make the 'ticket closed' email template sexier - change the 'helpdesk: ticket closed' email template as follows: - Subject: Ticket Closed - Reference 15 - Dear [Customer Name], - We would like to inform you that we have closed your ticket (reference 15). We trust that the services provided have met your expectations and that you have found a satisfactory resolution to your issue. - However, if you have any further questions or comments, please do not hesitate to reply to this email to re-open your ticket. Our team is always here to help you and we will be happy to assist you with any further concerns you may have. - Thank you for choosing our services and for your cooperation throughout this process. We truly value your business and appreciate the opportunity to serve you. - Kind regards, - [Name] Helpdesk Team. - don't forget to add linebreaks to make the message breathable - https://nimb.ws/ShGmkL 'helpdesk: request acknowledgment' email template: change the name to: 'helpdesk: ticket received' - change the template description to: "Send customers a confirmation email to notify them that their helpdesk ticket has been received and is currently being reviewed by the helpdesk team. Automatically send an email to customers when a ticket reaches a specific stage in a helpdesk team by setting this template on that stage." Purpose: these emails are not worth taking storage space in the database, especially since there might be a lot of them + be consistent with the other email templates that are almost all in auto_delete - set auto_delete to true on the following email templates: helpdesk: request acknowledgment + helpdesk: ticket closed Task-3251713 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Projects can now enable the Documents feature without manually selecting a folder first; the system creates one automatically when needed. Demo data for document-related projects was also cleaned up to reuse existing task stages, making sample environments more consistent.
Original PR description
This PR brings two minor improvements to the Project/Documents bridges: - In order to make enabling the "Documents" feature on existing projects easier, make folder field non required in all cases, and generate a new folder if the field is left empty while the feature is enabled. - Make the demo data a bit cleaner by using the existing task stages from other demo projects for the generated documents demo project. Task-3251627