Daily updates from Odoo
Navigate
Branch
Thursday, June 27, 2019
10 changes
Enhancements to existing features
The web interface now hides the "Remove" button when users open related records from list-style fields, reducing the chance of accidentally unlinking a record when they meant to discard changes. The option remains available in kanban-style related fields where there is no alternative removal control.
Original PR description
When we open any x2m record (in a FormViewDialog), there is a "Remove" button to delete/unlink the opened record from parent. This button is placed besides "Discard" button and it creates little confusion in some cases. For example, in list view, there's already a bin / 'x' icon depending on the field type using which people are used to delete/unlink the record. And when they open a record, they might accidentally click "Remove" button instead of "Discard". To avoid this, now we won't show "Remove" button when we open record from x2many list view. However, we have to keep this button in case x2many of kanban as there's no other way to remove the record. Task : 1886913 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
This update adds tests to confirm that company context is handled correctly across the website, company switcher, and HR reporting. It helps prevent users from seeing or acting on the wrong company data when working in multi-company environments.
Original PR description
test_website: Add multi-company test ============================= Purpose ------------ This commit tests some behaviors with multi company mode after changes brought by f847a46. Specification…
test_website: Add multi-company test ============================= Purpose ------------ This commit tests some behaviors with multi company mode after changes brought by f847a46. Specification ------------------- The website company should be automatically set in the context as 'allowed_company_ids'. That way, we can remove the switch company menu on the website, which doesn't make a lot of sense. This test enforce this behavior. web: Add QUnit tests for the SwitchCompanyMenu ========================================= Purpose ------------ This commit tests some behaviors with multi company mode after changes brought by f847a46. Specification ------------------ Ensure the robustness of the switch company menu for multiple cases like: - Bar rendering - Switch to another company in mono/multi environment - Toggle another company in mono/multi environment - Remove a company in mono/multi environment The widget itself has been slighty modified to make it more testable: - Reading from session is now in the `willStart` function instead of `init` to allow mocking the session (in tests, `init` is executed before the mock is applied). - In the event handlers, don't use `bbq` to retrieve current allowed company ids. `bbq` is not easily nor cleanly patched. - When reading allowed company ids from session, cast ids from string to integer. They are everywhere casted except there. and some linting hr: Add multi company tests ====================== Purpose ------------- This commit tests some behaviors with multi company mode after changes brought by f847a46. Specification ------------------ Check that a report printing for several records on different companies: - Works if the context is correctly set, i.e. both companies are in the allowed_company_ids - Doesn't work if the context is not correctly set
Payroll no longer depends on a hidden, fixed Attendance record when creating work entries and payslips. The default work entry type is now set on the payroll structure type, keeping standard behavior while making configuration clearer and reducing the risk of payroll generation breaking if master data is removed.
Original PR description
Purpose ======= Currently, the default type when generating work entries is the type "Attendance" defined in data (xml id `work_entry_type_attendance`). It is automatically loaded through xml reference. This has several issues: 1) This particular type is auto-magically set, the end user does not know why and can't change this behavior with configuration. 2) More importantly, If the data is deleted, the entire work entry and payslip generation is broken. Specification ============= Work entry and payslip generation should not have a hard dependence on the "Attendance" data. The default work entry type used to generate work entries from the calendar should be defined on the structure type, The default value should be set to "Attendance". The general behavior of the Payroll app should remain unchanged. Task id 2024460
Payroll officers can now select the specific company car to use when calculating Belgian payroll benefits on a payslip. This helps avoid employees being charged for a car they have not yet started driving and adds a check to find payslips where the employee is the vehicle driver.
Original PR description
purpose: As the atn is computed according the vehicle set on the contract, If the employee is pending a new car, he could pay the ATN of this car he doesn't drive Specification: - Add a field vehicle_id on the payslip (pre filled with the company car set on the contract) - The Payroll officer can change it. Use the ATN of this car for the payslip computation. - In Payslip search, add a filter on "Check Car". It filters on payslip where employee is set as driver on the vehicle task-1925505
Payroll users can now select a specific salary structure when generating payslips from a batch. This supports cases such as 13th month pay by ensuring the generated payslips follow the chosen payroll structure.
Original PR description
Able to generate 13th month payslip. Added structure_id in generate payslip from batch wizard. If structure_id is selected in wizard then, payslips will be generated according to selected structure. task-1935188
Users opening records from the Gantt view can once again remove those records directly from the dialog. This keeps deletion available where there is no alternative removal path, preventing unnecessary workflow interruptions.
Original PR description
This commit adapts the changes done in https://github.com/odoo/odoo/pull/28792 In the above PR, we hide the 'Remove' button in FormViewDialog by default. But for the gantt view, there's no other way to remove the record opened from this view, so we need to keep the button in this case. task-1886913
This change updates the Norwegian localization work referenced by the project task. It likely keeps local business requirements aligned with current Odoo enterprise localization needs, though the provided pull request details do not list specific file-level changes.
Original PR description
Task: https://www.odoo.com/web?#id=37726&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.f2cd5345ee05b29072f47d4d393f5900
Resolved issues and error corrections
This update fixes an issue where website editor changes could lose the intended language setting when saving translated content. Businesses can more reliably manage multilingual website text without accidentally overwriting or missing language-specific values.
Original PR description
Task : https://www.odoo.com/web#id=31484&view_type=form&model=project.task&action=327&menu_id=5195 Pad : https://pad.odoo.com/p/r.41e891bfe0cc1a8e4852b0904c7050fa 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
This fix prevents Odoo's core system from accidentally replacing existing context information during operations. It helps keep background settings and user-specific data intact, reducing the risk of unexpected behavior across the application.
This update fixes a date-related issue in an accounting report test that could fail depending on the day it was run. It helps keep automated checks stable and reduces false alarms during development.
Original PR description
The date was set to year-06-26, any day before that in the same year would create a line for overdue amount, not counted in an assert below