Daily updates from Odoo
Thursday, July 25, 2024
15 changes · master
Enhancements to existing features
Helpdesk reports now use average calculations for fields where totals were misleading. This makes reporting clearer and prevents unnecessary measures from appearing automatically in cohort views.
Original PR description
A lot of field that appear in reporting views use the "sum" aggregate method, where the "avg" method would make more sense. This PR changes the aggregate method where needed. This has the added benefit of them not being automatically added to cohort views. Task-3383332
The 1099 box field is now positioned below the payment method field on partner records. This keeps related payment and tax reporting information grouped together, making the form easier to review and maintain.
Original PR description
In this commit: https://github.com/odoo/odoo/pull/172479/commits/47312748f5ce87a921877c46f1136ec7a23e7190 We moved the field property_payment_method_id into the account module and we want it to be below the payment terms in the res_partner view. This commit will change the xpath so that the field box_1099_id is now below the payment method field. task: 4016652
Resolved issues and error corrections
This update adjusts the field service report setup after a related project field was removed from the burn chart. It helps ensure the burn chart view continues to load and display correctly for users.
Original PR description
Removed project field from burn chart so we have to updated corresponding XPath. task-3999664
This fix ensures loyalty program descriptions are always provided when needed, preventing validation errors during related workflows. It helps keep discount calculations reliable for loyalty programs and avoids interruptions for teams using helpdesk, sales, and loyalty features.
Original PR description
**In this commit:** - Description field is made required because it is used for all programs and exclusively used to compute value of discount product. **Affected Version:** master **opw**-4032798
Code cleanup and technical improvements
This update removes an outdated option from Odoo's automated guided tour tests and replaces it with a simpler way to identify pop-up windows. It keeps test behavior aligned with the newer tour API while reducing maintenance complexity across several business apps.
Original PR description
https://github.com/odoo/odoo/pull/174315
This update removes an outdated setting from an automated Timesheet Grid walkthrough used for testing and guidance. It keeps the module aligned with the current tour system and helps reduce future maintenance issues, with no expected change for everyday users.
Original PR description
From b2b2576691750c0444d8871f95b733bec07ae45d, consumeEvent in no longer used in interactive Tour. Then, it's removed from tour API. task~3974087 https://github.com/odoo/odoo/pull/174347 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Description of the issue this commit addresses: We do not want the user to be able to create fiscal years on child companies. --- Desired behavior after this commit is merged: A new check in fiscal years raises an error when the user tries to create a fiscal year from a child company. --- no task-feedback Forward-Port-Of: odoo/enterprise#67285 Forward-Port-Of: odoo/enterprise#67121
Original PR description
Description of the issue this commit addresses: We do not want the user to be able to create fiscal years on child companies. --- Desired behavior after this commit is merged: A new check in fiscal years raises an error when the user tries to create a fiscal year from a child company. --- no task-feedback Forward-Port-Of: odoo/enterprise#67285 Forward-Port-Of: odoo/enterprise#67121
Steps: - Install helpdesk_timesheet - In Kanban View > Start the timer of a ticket Issue: - If we have a kanban card with an older date and we start and stop the timer, a new kanban entry will be made with today's date. But for the tickets , if we start a timer, the ticket_id is not set in the timer header with in the new ticket. Cause: - Due to the condition given in the `action_start_new_timesheet_timer`, there is no helpdesk_ticket_id mentioned in that function. Fix: - B
Original PR description
Steps: - Install helpdesk_timesheet - In Kanban View > Start the timer of a ticket Issue: - If we have a kanban card with an older date and we start and stop the timer, a new kanban entry will be made with today's date. But for the tickets , if we start a timer, the ticket_id is not set in the timer header with in the new ticket. Cause: - Due to the condition given in the `action_start_new_timesheet_timer`, there is no helpdesk_ticket_id mentioned in that function. Fix: - By extending the `_get_new_timesheet_timer_vals` to the helpdesk_timesheet module to gave helpdesk_ticket_id the issue will be solved. task-3970176 Forward-Port-Of: odoo/enterprise#67294 Forward-Port-Of: odoo/enterprise#64359
- 17.0 We reverted the commit https://github.com/odoo/enterprise/commit/a789702766df289f4abe993374583a69027ef572 because it was causing the issue of hiding days when the row name was too long in the timesheet grid view. ### Steps to reproduce: - Install the project and timesheet app. - Open the project app, create a project, and add a task to it. - Add a timesheet a week before the current date for the created task. - Now open the timesheet app in grid view. - The created project and
Original PR description
- 17.0 We reverted the commit https://github.com/odoo/enterprise/commit/a789702766df289f4abe993374583a69027ef572 because it was causing the issue of hiding days when the row name was too long in the timesheet grid view. ### Steps to reproduce: - Install the project and timesheet app. - Open the project app, create a project, and add a task to it. - Add a timesheet a week before the current date for the created task. - Now open the timesheet app in grid view. - The created project and task are in italic font. - The last letter of the project and task name is slightly cut. ### Issue: The last letter of the string is slightly cut in the timesheet grid view. ### Cause: The dedicated space allowed for normal text is not sufficient for the italic. So, the last letter was slightly cut. ### Solution: Provide an extra space to the italic string. task-3888277 Forward-Port-Of: odoo/enterprise#67238 Forward-Port-Of: odoo/enterprise#63786
Currently it is assumed that all assets we write on belong to the same company. (Any exceptions to this are probably rare in practice.) This commit ensures that writing on assets with different companies works correctly. (no task) Forward-Port-Of: odoo/enterprise#67262 Forward-Port-Of: odoo/enterprise#65795
Original PR description
Currently it is assumed that all assets we write on belong to the same company. (Any exceptions to this are probably rare in practice.) This commit ensures that writing on assets with different companies works correctly. (no task) Forward-Port-Of: odoo/enterprise#67262 Forward-Port-Of: odoo/enterprise#65795
In this PR: Hide the `Timesheet Init Amount` and `Timesheet unit Amount` fields from the pivot and graph views. task-3970176 Forward-Port-Of: odoo/enterprise#67310 Forward-Port-Of: odoo/enterprise#64649
Original PR description
In this PR: Hide the `Timesheet Init Amount` and `Timesheet unit Amount` fields from the pivot and graph views. task-3970176 Forward-Port-Of: odoo/enterprise#67310 Forward-Port-Of: odoo/enterprise#64649
When opening the shopfloor from a specific workcenter, workorder or production order, only the concerned workcenter should be shown. task-4060857 Forward-Port-Of: odoo/enterprise#66923
Original PR description
When opening the shopfloor from a specific workcenter, workorder or production order, only the concerned workcenter should be shown. task-4060857 Forward-Port-Of: odoo/enterprise#66923
Steps: Login as portal, and to to a task form, page sub-tasks. Make Customer column visible. Add a line and try to edit that field. Issue: You can't. But after saving, you can. Cause: The field is invisible if `allow_billable` and `is_fsm` are False. A child task inherits both from its parent, but this one hasn't been created yet. Solution: In this case, the condition is not needed. If we create the child and he has both fields to False, it means its parent too. Yet the `partner_
Original PR description
Steps: Login as portal, and to to a task form, page sub-tasks. Make Customer column visible. Add a line and try to edit that field. Issue: You can't. But after saving, you can. Cause: The field is invisible if `allow_billable` and `is_fsm` are False. A child task inherits both from its parent, but this one hasn't been created yet. Solution: In this case, the condition is not needed. If we create the child and he has both fields to False, it means its parent too. Yet the `partner_id` column is invisible if it is the case. So the solution is simple: remove the condition. related: https://github.com/odoo/odoo/pull/174323 task-3713729 Forward-Port-Of: odoo/enterprise#67252
This improves the changes made by 6f1f45e137bbd87498b7e3998fe013716c2e66bf, moving the creation of the `account.move` at the approval step of an expense report. Before 6f1f45e137bbd87498b7e3998fe013716c2e66bf change: The `hr_payroll_expense` flow worked by relying on the fact that we created the expense sheet move at the very last moment, allowing to set the correct account to its payment term line, to reconcile with the payslip move easily. Before this change: In 6f1f45e137bbd87498b7e39
Original PR description
This improves the changes made by 6f1f45e137bbd87498b7e3998fe013716c2e66bf, moving the creation of the `account.move` at the approval step of an expense report. Before…
This improves the changes made by 6f1f45e137bbd87498b7e3998fe013716c2e66bf, moving the creation of the `account.move` at the approval step of an expense report. Before 6f1f45e137bbd87498b7e3998fe013716c2e66bf change: The `hr_payroll_expense` flow worked by relying on the fact that we created the expense sheet move at the very last moment, allowing to set the correct account to its payment term line, to reconcile with the payslip move easily. Before this change: In 6f1f45e137bbd87498b7e3998fe013716c2e66bf, since approving the report creates draft `account.move`s & `account.payment`s. This makes it more difficult to reconcile the two moves. A workaround was found in deleting the draft entry of the expense sheet when flagging it to be reimbursed through a payslip. After this change: This removes that workaround and allows a proper reconciliation of the two `account.move`s by using the draft entry `matching_number` mechanic. There are several improvements: - Avoid deleting a move, thus allowing it to be edited - Automatically reconcile, no matter if the accounts do not match, a misc entry is automatically generated if needed - Manual fallback, if the amounts of the two `account.move`s do not match, we keep the temporary `matching_number` set on the lines to help the accountant manually reconcile. We cannot do it automatically in this case as it requires user input (selecting an account for the write-off entry) task-id: 3955524 Forward-Port-Of: odoo/enterprise#64256
Before this commit, some Markup were missing in some post message which resulted in some html to be displayed in the chatter. task: 4041892 Community: https://github.com/odoo/odoo/pull/173375 Forward-Port-Of: odoo/enterprise#67255 Forward-Port-Of: odoo/enterprise#66767
Original PR description
Before this commit, some Markup were missing in some post message which resulted in some html to be displayed in the chatter. task: 4041892 Community: https://github.com/odoo/odoo/pull/173375 Forward-Port-Of: odoo/enterprise#67255 Forward-Port-Of: odoo/enterprise#66767