Tuesday, April 16, 2024
7 changes · master
Enhancements to existing features
Adds ready-to-use Indian payroll sample data so salespeople and business analysts can demonstrate payroll workflows more easily. The demo setup includes employees, users, contracts, leave allocations, bank details, payslips, and payslip batches for an Indian company.
Original PR description
The purpose of these demo data is for our salesperson or business analyst to give a demo to customers/partners. This PR includes the following demo data: --------- - Addition of Indian employees - Creation of users for the Indian company - Generation of contracts for all employees - Allocation of leaves for these employees - Inclusion of partners and their bank account details - Generation of payslips for all employees with varying structures - Creation of payslips batch task-3491700
This update adds broader automated checks to make sure the timesheet leaderboard behaves correctly across timer, grid, list, kanban, and holiday-related scenarios. It helps reduce the risk of ranking or display issues reaching users, improving confidence in timesheet reporting.
Original PR description
This commit will add a certain number of tests to ensure that the timesheets leaderboard works properly. task-3570306
Users can now enable a Merge option on selected business records and send them directly to the deduplication screen as one merge group. This makes it easier to clean up duplicate or noisy data on supported models without relying only on automated rules.
Original PR description
Purpose ======= Introduce a "manual" merge mode. Indeed, while the current rules introduced some "ongoing hygiene", one may wants to take manual action to "clean up one's database". For example,…
Purpose ======= Introduce a "manual" merge mode. Indeed, while the current rules introduced some "ongoing hygiene", one may wants to take manual action to "clean up one's database". For example, because one is working on a report (pivot table, o-spreadsheet, ...). Or because one is able to take a more drastic approach (merge records that aren't technically the same to reduce the amount of noise, ...). The objective is to allow the user to select multiple records on a model to open the data_merge deduplicate view with the records them selected to merge them quickly. Specification ============= Add a button on ir.model view that allow the user to enable the Merge contextual action on the current model. Once the merge action is enable, the user is able to select multiple records and open the data_merge deduplicate view targetting only the records them selected. The selected records are placed in the same merge group. In Data_merge/configuration, user can find the list of models in which the merge action has been activated. By default, display the "Merge" option in the action menu for the following models: crm.lost.reason crm.tag event.tag.category product.category project.tags project.task helpdesk.ticket helpdesk.tag res.country res.country.state res.partner.category res.partner.industry res.partner.title utm.campaign utm.medium utm.source As some models already have custom merge methods, the generic merge action should not be activated on those models, notably: crm.lead res.partner account.analytic.line Link ==== Task ID: 2459416 COM PR: https://github.com/odoo/odoo/pull/67613
Kenyan payroll now lets employees handle their own life insurance contributions while still having the appropriate deduction reflected on their payslip. This gives employees more flexibility and reduces company-managed administration for this benefit, while also cleaning up unused related code.
Original PR description
Add the possibility for employees to manage their life insurance by themselves instead of the company so they can contribute to the life insurance by themselves and still have the deduction on their payslip. Also this PR remove unused code by the same occasion task-3827182
Embedded view links in Knowledge articles now open a popover with clear actions to open, copy, edit, or remove the link. This makes linked views easier to manage directly from the article editor and improves guidance in the Helpdesk Knowledge flow.
Original PR description
*= knowledge website_helpdesk_knowledge With this PR, the behavior for embedded view links is, On the click, it opens a popover that contains the name (same as the body) and three buttons(copy, edit,…
*= knowledge website_helpdesk_knowledge With this PR, the behavior for embedded view links is, On the click, it opens a popover that contains the name (same as the body) and three buttons(copy, edit, remove). - Name in the popover which is a link, on the click, it will redirect to that view. - Copy button: It copies the name (with styling if applied) and prints on the paste as it is with the popover behavior. - Edit button: It opens a dialog box where the name has already been printed and users can edit the name and save it to edit the name in the main body. -> There is styling too, for customizing the link and making it a button. - Remove button: It converts the link into simple text. So, this is a new functionality to click on the link from the popover to redirect to that view, - For that, modified the tour which directs the users on how the flow works. **Task**-3082042 Co-authored-by: Naman Shah <nash@odoo.com> Co-authored-by: Damien Abeloos <abd@odoo.com>
A new digest gives teams regular visibility into social post engagement and clicks over the past day, week, and month. Appointment digest reporting is also enhanced with a linked action for booked meetings, making it easier to review related activity.
Original PR description
This PR will add a new digest for the `social` module. The digest will provide the following statistics: - Engagement on the posts created over the last 24h / 7 days / 30 days. - Number of clicks generated by the posts created over the last 24h / 7 days / 30 days. We will also link an action to the digest "# Meetings Booked" digest added to the community version (see related PR). task-2647241
Shop attribute filters now carry through from the product listing to product pages and remain selected when shoppers return to the shop. This makes browsing more consistent and reduces friction for customers refining products by attributes.
Original PR description
- Attributes filtered on /shop should carry over to the product page - When going back to /shop, the attributes selected should remain task-3067205 See also: - odoo/odoo#157412