Tuesday, January 23, 2024
21 changes
17 changes
Enhancements to existing features
Planning users can now set available roles and a default role directly on material records. This makes it easier to configure materials for scheduling while removing timezone information from the material card view to keep it focused.
Original PR description
This commit adds some fields essentials for planning in the form view of `resource.resource` model displayed in the `Materials` menu in Planning app. Those fields are `role_ids` and `default_role_id`. This commit also removes the timezone field from the kanban view. task-3610478
Resolved issues and error corrections
Spreadsheet template downloads now use the proper template name and the expected .osheet.json file extension. This makes downloaded files easier to identify and prevents confusing or incorrect filenames for users.
Original PR description
Before this commit, spreadsheet template file names were not displayed properly, resulting in wrong file name upon getting downloaded. This commit fixes this issue by introducing a new file_name field which ensures proper file names with osheet.json extension is applied. Task: 3636223
Code cleanup and technical improvements
Miscellaneous changes
Like we have it for cars, we add the following description to bikes in the salary configurator : Monthly cost : [contract value] (Rent) Electric Assistance : Yes/No Color Bike Frame Type Frame Size task-3640749 Forward-Port-Of: odoo/enterprise#54741 Forward-Port-Of: odoo/enterprise#53084
Original PR description
Like we have it for cars, we add the following description to bikes in the salary configurator : Monthly cost : [contract value] (Rent) Electric Assistance : Yes/No Color Bike Frame Type Frame Size task-3640749 Forward-Port-Of: odoo/enterprise#54741 Forward-Port-Of: odoo/enterprise#53084
4 changes
Enhancements to existing features
This update improves system monitoring by automatically logging how long scheduled jobs take to complete. By recording job duration at the standard information level, administrators and support teams can more easily track system performance and identify slow-running tasks without requiring additional configuration.
Original PR description
Log the job duration of the usual `INFO` level for easier monitoring. 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 standardizes how many enterprise interface components declare the information they expect to receive. It improves consistency and maintainability across accounting, HR, helpdesk, and related areas without changing business workflows.
Original PR description
This commit adds static props to all component that don't define it. This makes props validation universal throughout the code base which helps for code clarity and consistency. This is the enterprise part of https://github.com/odoo/odoo/pull/143209 task-3594598
[FIX] l10n_lt_reports: Balance Sheet: respect legal line order "Total Assets" and "Total Equity and Liabilities" were inverted. This occured because those lines used to declare an explicit sequence in 15.0, and this sequence got removed from the data file in 16.0. We fix that by enforcing a sequence, and also reorder the lines in the file in order to ease the forward-port to 17.0, where the auto-sequencing feature is used (this way, we also minimize the number of conflicts when forward-portin
Original PR description
[FIX] l10n_lt_reports: Balance Sheet: respect legal line order "Total Assets" and "Total Equity and Liabilities" were inverted. This occured because those lines used to declare an explicit sequence in 15.0, and this sequence got removed from the data file in 16.0. We fix that by enforcing a sequence, and also reorder the lines in the file in order to ease the forward-port to 17.0, where the auto-sequencing feature is used (this way, we also minimize the number of conflicts when forward-porting a fix in this report in the future). ------------------------------------ [FIX] l10n_lt_reports: Balance Sheet: make less line foldable For usability. This will require less clicks to have a broader view of the report. OPW 3608139 Forward-Port-Of: odoo/enterprise#54717 Forward-Port-Of: odoo/enterprise#54299
**Steps:** - Navigate to the project module. - Choose any project and click on a Kanban card. - Inside the form view, click the start button from the status bar. - Observe the status bar. **Issue:** - Status bar flickering when starting/stopping timer **Cause:** - When clicking the start button in the project module's form view, the timer_start field causes flickering in the status bar due to excess padding. **Fix:** - Removing the excessive padding from the timer_start field wil
Original PR description
**Steps:** - Navigate to the project module. - Choose any project and click on a Kanban card. - Inside the form view, click the start button from the status bar. - Observe the status bar. **Issue:** - Status bar flickering when starting/stopping timer **Cause:** - When clicking the start button in the project module's form view, the timer_start field causes flickering in the status bar due to excess padding. **Fix:** - Removing the excessive padding from the timer_start field will resolve the flickering issue. **Task**-3610481 Forward-Port-Of: odoo/enterprise#54616 Forward-Port-Of: odoo/enterprise#51930
Forward-Port-Of: odoo/enterprise#54840 Forward-Port-Of: odoo/enterprise#54321
Original PR description
Forward-Port-Of: odoo/enterprise#54840 Forward-Port-Of: odoo/enterprise#54321
**Current behavior:** Sending a follow-up report to an overdue client with no due date attached will cause a TypeError. --- **Expected behavior:** If no due date is specified in the follow-up report, it will use a fallback date value from elsewhere. --- **Steps to reproduce:** 1. Create an invoice which is passed due 2. In the Follow-up Reports view, delete the due date field value from one of the invoice lines in the report 3. Click 'Follow up' then 'Send & Print'
Original PR description
**Current behavior:** Sending a follow-up report to an overdue client with no due date attached will cause a TypeError. --- **Expected behavior:** If no due date is specified in the follow-up report, it will use a fallback date value from elsewhere. --- **Steps to reproduce:** 1. Create an invoice which is passed due 2. In the Follow-up Reports view, delete the due date field value from one of the invoice lines in the report 3. Click 'Follow up' then 'Send & Print' --- **Cause of the issue:** A method _update_next_followup_action_date() tries to update the follow-up date for the next deadline without considering the due date field may be empty. --- **Fix:** Filter the account_move_line objects which do not have legitimate date values from the iteration block where the offending operations take place. --- opw-3666901 Forward-Port-Of: odoo/enterprise#53829
…fers Only hr admins are able to generate offers from contracts, which should not be the case Forward-Port-Of: odoo/enterprise#54811
Original PR description
…fers Only hr admins are able to generate offers from contracts, which should not be the case Forward-Port-Of: odoo/enterprise#54811
Currently the gantt view for user appointments (dentist, interview,...) is grouped by organizer of the event. While this works for the purpose of managing appointments it also hides the fact that the partners linked to each user may be attending some other event at the same time. To make this more clear we enable grouping by partner_ids and we make the gantt view default to that grouping. task-3452277 Forward-Port-Of: odoo/enterprise#54807 Forward-Port-Of: odoo/enterprise#45114
Original PR description
Currently the gantt view for user appointments (dentist, interview,...) is grouped by organizer of the event. While this works for the purpose of managing appointments it also hides the fact that the partners linked to each user may be attending some other event at the same time. To make this more clear we enable grouping by partner_ids and we make the gantt view default to that grouping. task-3452277 Forward-Port-Of: odoo/enterprise#54807 Forward-Port-Of: odoo/enterprise#45114
Forward-Port-Of: odoo/enterprise#54621
Original PR description
Forward-Port-Of: odoo/enterprise#54621
In #42351, the account.report.expression with xmlid `account_financial_report_line_02_0_6_fr_bilan_passif_balance` was deleted, and in its place was defined `account_financial_report_line_02_0_6_fr_bilan_passif_net`. However, since the two have the same `label='net'` the SQL constraint introduced in https://github.com/odoo/odoo/commit/987b82e5c9add1e9e2a9fdabe6dc73a3a6daa9ec would fail when upgrading the module. To resolve this, we prefer to delete the old expression pre-migration rather t
Original PR description
In #42351, the account.report.expression with xmlid `account_financial_report_line_02_0_6_fr_bilan_passif_balance` was deleted, and in its place was defined `account_financial_report_line_02_0_6_fr_bilan_passif_net`. However, since the two have the same `label='net'` the SQL constraint introduced in https://github.com/odoo/odoo/commit/987b82e5c9add1e9e2a9fdabe6dc73a3a6daa9ec would fail when upgrading the module. To resolve this, we prefer to delete the old expression pre-migration rather than revert the change in xmlid, in order to not break things for new databases where the new xmlid is used. Upgrade PR: https://github.com/odoo/upgrade/pull/5533 opw-3659810 Forward-Port-Of: odoo/enterprise#54629 Forward-Port-Of: odoo/enterprise#53492
*= industry_fsm_sale, planning Current behavior before PR: - HTML tags are displayed in the onboarding tour. Desired behavior after PR is merged: - Display the tag effects instead of showing it in the onboarding tour. After the https://github.com/odoo/odoo/pull/107618 web_tour was converted into Owl, 'markup' was required to show the html tag effect instead of htm tags. Task-3457112 Forward-Port-Of: odoo/enterprise#54765 Forward-Port-Of: odoo/enterprise#53893
Original PR description
*= industry_fsm_sale, planning Current behavior before PR: - HTML tags are displayed in the onboarding tour. Desired behavior after PR is merged: - Display the tag effects instead of showing it in the onboarding tour. After the https://github.com/odoo/odoo/pull/107618 web_tour was converted into Owl, 'markup' was required to show the html tag effect instead of htm tags. Task-3457112 Forward-Port-Of: odoo/enterprise#54765 Forward-Port-Of: odoo/enterprise#53893
Prior to this commit, the `o_menu_toggle` arrow had a glitch when the language was set on RTL. This commit adapts the arrow to fix this glitch. task-3548808 | Before | After | |--------|--------| |  |  | Forward-Port-Of: odoo/
Original PR description
Prior to this commit, the `o_menu_toggle` arrow had a glitch when the language was set on RTL. This commit adapts the arrow to fix this glitch. task-3548808 | Before | After | |--------|--------| |  |  | Forward-Port-Of: odoo/enterprise#51554
Before this commit, the error mail subject was converted to HTML. It would not look professionnal in a mail client... Forward-Port-Of: odoo/enterprise#54680
Original PR description
Before this commit, the error mail subject was converted to HTML. It would not look professionnal in a mail client... Forward-Port-Of: odoo/enterprise#54680
See also: - https://github.com/odoo/odoo/pull/150472 Forward-Port-Of: odoo/enterprise#54859
Original PR description
See also: - https://github.com/odoo/odoo/pull/150472 Forward-Port-Of: odoo/enterprise#54859
Thanks to the safe_eval call https://github.com/odoo/enterprise/blob/0ae2e56fc3e14ee0afdf314fda5c028ba9d33242/hr_payroll/controllers/main.py#L43 in `get_payroll_report_print`, whenever a non-ASCII character is passed, a Python `SyntaxError: invalid character` will occur because this character will be passed to `compile` https://github.com/odoo/odoo/blob/e7a511b7b5af57696e691f6f0a71bec63053f860/odoo/tools/safe_eval.py#L216 which expects only valid python code. Therefore we remove the
Original PR description
Thanks to the safe_eval call https://github.com/odoo/enterprise/blob/0ae2e56fc3e14ee0afdf314fda5c028ba9d33242/hr_payroll/controllers/main.py#L43 in `get_payroll_report_print`, whenever a non-ASCII character is passed, a Python `SyntaxError: invalid character` will occur because this character will be passed to `compile` https://github.com/odoo/odoo/blob/e7a511b7b5af57696e691f6f0a71bec63053f860/odoo/tools/safe_eval.py#L216 which expects only valid python code. Therefore we remove the unneccessary non-ASCII quote from the .po file that was probably a mistake in the first place. opw-3688140 Forward-Port-Of: odoo/enterprise#54729
Resolved issues and error corrections
Fixed an issue where the 'canceled' stage in the Helpdesk Tickets kanban view was not collapsing by default. This improves the user experience by automatically hiding completed canceled tickets, making the view cleaner and easier to navigate. The fix ensures the canceled stage behaves consistently with other collapsible stages in the system.
Original PR description
Versions: --------- - 17.0 Steps to reproduce: ------------------- - Install Helpdesk - In Tickets kanaban view - The 'canceled' stage is not folded by default Issue: ------ - The 'canceled' stage in the tickets kanaban view is not folded by default. Cause: ------ - The 'canceled' stage is not set to be foldable by default. Solution: --------- - By set the 'canceled' stage by default foldable the issue is resolved. task-3610483
This fix ensures that the Indian PAN (Permanent Account Number) field is hidden when users are working with non-Indian companies, even if the Indian accounting module is installed. Previously, the field would incorrectly appear for all companies, causing confusion. This improves the user experience by showing only relevant fields based on the active company's location.
Original PR description
**Before this commit:** If Indian-Accounting is installed in the user's system but the user is in another company, still the l10n_in_pan(PAN) field is visible. **Technical Reason:** attrs was not there to invisible the field. Adding invisible attrs if the active company is not Indian. **After this commit:** l10n_in_pan(PAN) field is not visible if the active company is not Indian. **Task**-3635445 Forward-Port-Of: odoo/odoo#147532
This update fixes an issue in the web editor where font style buttons were incorrectly showing as active when users selected cells. After this fix, font styles will only appear active when actually applied to the selected content, providing a clearer and more accurate representation of the current formatting state.
Original PR description
Current behavior before PR: Font styles shows active while selecting cells. Desired behavior after PR is merged: Font styles should not be active by default. task-3547652 Forward-Port-Of: odoo/odoo#138220