Daily updates from Odoo
Tuesday, May 14, 2024
26 changes · master
New functionality added to Odoo
Field service teams can now mark task-related products as under warranty. When enabled, the related sale item is automatically priced at zero, helping ensure warranty work is not billed to customers by mistake.
Original PR description
In this commit, we introduce the functionality to activate the "under warranty" feature for tasks within the industry_fsm_sale module. When this feature is enabled for a task, the sale item price is automatically set to zero, indicating the warranty status. task-3784174
Enhancements to existing features
Approval product selection now defaults to items that can be purchased instead of items that can be sold. This better matches how most approval requests use products, making it faster for users to find the relevant purchase-related items.
Original PR description
Before this commit the default filter on the product form of approval was 'Can be Sold'. But in approvals, majority users uses purchase related products. This commit adds the default filter of 'Can be Purchased' on the products and products variants form of approval. Same default filter is also applied on more product list for selecting products for approval request. task-3633895
Planning shift forms are easier to use, with a clearer Save Template action and repeat options placed near the shift dates. The planning workflow also opens the correct form when creating a new shift from the sales planning dialog, reducing confusion for users.
Original PR description
- following improvement made in this PR:
- Instead of saving template on boolean field add a 'save template' button to the planning slot form view.
- move the 'repeat' field under the date with boolean icon fa-repeat.
- update test tour with 'mitchell' as it is already considering user timezone
first when calculating start and end time in `_calculate_start_end_dates`.
task-3636218The rental eCommerce module was adjusted to stay aligned with recent changes in the main website and sales platform. This helps keep rental product snippets and related website content working consistently after the broader platform update.
Original PR description
See also odoo/odoo#154632
The website sales dashboard tests were updated to match a related change where the old sales onboarding flow was removed and replaced. This keeps validation aligned with the current experience and helps prevent false test failures during future releases.
Original PR description
This PR include the following changes: - Remove the configuration bar. task-3645924 COM PR: odoo/odoo#152270 ENT PR: odoo/enterprise#61325 UPG PR: odoo/upgrade#5644 DOC PR: odoo/documentation#8391
Managers can now request appraisals for employees anywhere below them in their reporting hierarchy, not just direct reports. This makes the appraisal process more flexible for senior managers and avoids unnecessary errors when managing broader teams.
Original PR description
The system now allows for creating appraisals for individuals even if you're not their direct manager but are in their managerial hierarchy. For instance, if A is the manager of B, and B is the manager of C, A can request an appraisal for C. Previously, this resulted in an error because only direct managers could create an appraisal.
Polish financial reports have been updated to match the latest Polish chart of accounts and account groups. This makes the reports more relevant and usable for companies relying on Polish accounting standards.
Original PR description
Currently, the polish chart of account is not up to date and is therefore underused by user since it is not relevant. This PR goes with a community PR which goal is to update the chart of accounts and account groups. Because of this change, financial reports have to be updated too so they match the new chart. Adding this, the financial reports should be relevant and match the new chart of accounts. Community PR : [odoo/odoo#130538](https://github.com/odoo/odoo/pull/130538) task-3332731
Odoo now checks that a bank journal currency matches the linked bank account currency before importing transactions. If the journal is empty it can update the journal currency automatically, while journals with existing entries are blocked from importing mismatched transactions to prevent incorrect amounts; the reconciliation view also avoids an error when currency data is missing.
Original PR description
Previously, when you sync a bank journal with a bank account that have different currency, odoo will import all the transaction with the amount of the bank account, but in the currency of the…
Previously, when you sync a bank journal with a bank account that have different currency, odoo will import all the transaction with the amount of the bank account, but in the currency of the journal. For example: when importing 500 USD from the bank account to an IDR journal, it will become 500 IDR. This behavior also gets a bit weirder because the code checks the currency of the bank with the company (which should be unrelated here). This commit aims to fix that, and establish these new behaviors: - The currency of the company is irrelevant. Only the journal matters. (because a journal can have different currency than the company's) - If the journal currency has a mismatch with the bank account's: - If there's no existing entries in the journal, re-assign the journal's currency to the bank account's currency - If there's existing entries, prevent the import process from happening to prevent the mentioned weird behaviors. related community-PR: https://github.com/odoo/odoo/pull/162235 task-id: 3798134
Knowledge articles now show their place in the article hierarchy directly in the top bar, replacing generic breadcrumbs. Users can more easily understand where an article sits, jump to related parent articles, and move back and forward through recently opened articles, while less-used article setup actions are grouped under more options to save space.
Original PR description
Purpose: -------- Instead of showing the general breadcrumbs, the form view of knowledge now displays the current article's hierarchy. This makes it easier for users to jump to articles (no need to look for the parent in the sidebar anymore) and to have more context about the current article. Two new buttons on the left of the hierarchy allow the user to jump back to previously opened articles, as well as to the previous action when applicable (like clicking on the previous breadcrumb item if any). The "add icon", "add cover" and "add properties" buttons are moved in the "more options" panel to save space as the breadcrumbs and hierarchy may take a lot of space in the topbar. See underlying commits for more details. Task-3790413
Payroll now avoids sending an extra profile-update notification to the HR responsible person when employee self-editing is enabled. This keeps notifications cleaner by ensuring the same person receives only one relevant message.
Original PR description
While employee editing is allowed through the settings, HR responsible will receive a notification when an employee updates his/her profile information In this commit, When HR responsible is present in the users to notify while employee editing It won't send this other notification to the HR responsible This way only one notification will be sent to the users task-3642351
Financial report filters have been simplified to make reports easier to configure and use. The update also touches budget-related report controls, helping users work more efficiently when reviewing financial information.
Resolved issues and error corrections
Appointment bookings linked to Google or Microsoft calendars will no longer send extra cancellation or update emails when the calendar provider already notifies attendees. This reduces duplicate messages and gives customers a cleaner booking communication experience.
Original PR description
There is now a method on calendar to know whether a notification email should be sent to attendees. We use it for appointment too to avoid sending updates to users who will already be alerted via the calendar provider (google/microsoft) when syncing the event.
Features or functions removed from Odoo
Unneeded access rules in the Approvals app were removed because the same permissions are already handled by an existing rule. This reduces duplication and helps keep access management easier to maintain without changing normal user workflows.
Original PR description
This will remove unnecessary access rules as they are already covered by another rule. Task: 3786622
The point-of-sale IoT customer display code was cleaned up after the customer display was moved into its own dedicated app. This reduces duplicated functionality and helps keep the point-of-sale IoT module easier to maintain without changing the intended customer experience.
Original PR description
In the corresponding community commit we refactor the customer display into it's own module. In this commit we remove the code that is no longer needed, because it is replaced by said customer display module
Appointment publishing can no longer be managed from the backend form or Kanban views. This simplifies the backend interface and helps ensure publishing is handled through the intended website flow.
Original PR description
This PR removes the functionality of publishing the appointment from the backend. - Remove the publish unpublish button from the appointment.type form view. - Remove the publish toggle button from Kanban cards. Task-3905167
Miscellaneous changes
Check Report Summary line columns were not aligned correctly, fixing it to have partner_name at the beginning, date at the middle, and check sequence number at the end of the line. task id: 3708433 Forward-Port-Of: odoo/enterprise#61149
Original PR description
Check Report Summary line columns were not aligned correctly, fixing it to have partner_name at the beginning, date at the middle, and check sequence number at the end of the line. task id: 3708433 Forward-Port-Of: odoo/enterprise#61149
Currently, when a warning is displayed on the progress bar, the hours overlap with the name of the line. This PR will fix it by adding the class 'bg-view' to the span. task-3888502 Forward-Port-Of: odoo/enterprise#61365
Original PR description
Currently, when a warning is displayed on the progress bar, the hours overlap with the name of the line. This PR will fix it by adding the class 'bg-view' to the span. task-3888502 Forward-Port-Of: odoo/enterprise#61365
In this commit [1], we changed the way we display intrastat report lines by grouping them. We did it for all the intrastat report, it was wrong. Actually, we should only do it for the belgian report. The aim of this commit is adding a key in options to know if lines should be grouped or not. By default the option is set to False except for the Belgian report. Since version 16.4, users can change the value by using the filter. task-3892823 [1]: https://github.com/odoo/enterprise/commit/217
Original PR description
In this commit [1], we changed the way we display intrastat report lines by grouping them. We did it for all the intrastat report, it was wrong. Actually, we should only do it for the belgian report. The aim of this commit is adding a key in options to know if lines should be grouped or not. By default the option is set to False except for the Belgian report. Since version 16.4, users can change the value by using the filter. task-3892823 [1]: https://github.com/odoo/enterprise/commit/217594fe8ba00329b3eb5c68e3eca3b556127cde Forward-Port-Of: odoo/enterprise#61783 Forward-Port-Of: odoo/enterprise#61455
The `use_create_components_lots` option of manufacturing picking type was never read as the context to get the active production order was not always specified. Forward-Port-Of: odoo/enterprise#61267 Forward-Port-Of: odoo/enterprise#61137
Original PR description
The `use_create_components_lots` option of manufacturing picking type was never read as the context to get the active production order was not always specified. Forward-Port-Of: odoo/enterprise#61267 Forward-Port-Of: odoo/enterprise#61137
This will add the previous year occupation to the double holiday computation. Task: 3893810 Forward-Port-Of: odoo/enterprise#61862
Original PR description
This will add the previous year occupation to the double holiday computation. Task: 3893810 Forward-Port-Of: odoo/enterprise#61862
As packages amount on customer locations side could be huge, don't retrieve those packages as they are not needed. @svs-odoo @Aurelienvd Forward-Port-Of: odoo/enterprise#59473
Original PR description
As packages amount on customer locations side could be huge, don't retrieve those packages as they are not needed. @svs-odoo @Aurelienvd Forward-Port-Of: odoo/enterprise#59473
part of task-3818666 Forward-Port-Of: odoo/enterprise#62350
Original PR description
part of task-3818666 Forward-Port-Of: odoo/enterprise#62350
Before this commit, when having opposite tax grid the domain of the journal_report_tax_tag_template_open_aml function was wrong. In case of opposite tax grid we should have put a list of tax_grid in the tag_id key which wasn't the case. It was only taking the last one since it was overridden in the next iteration of the loop. task-3869482 Forward-Port-Of: odoo/enterprise#62340 Forward-Port-Of: odoo/enterprise#61302
Original PR description
Before this commit, when having opposite tax grid the domain of the journal_report_tax_tag_template_open_aml function was wrong. In case of opposite tax grid we should have put a list of tax_grid in the tag_id key which wasn't the case. It was only taking the last one since it was overridden in the next iteration of the loop. task-3869482 Forward-Port-Of: odoo/enterprise#62340 Forward-Port-Of: odoo/enterprise#61302
Ensuring TZ allows to avoid issues in no-demo mode, notably when a timezone is required in sub records, like appointment types. Runbot-60487 Forward-Port-Of: odoo/enterprise#62061
Original PR description
Ensuring TZ allows to avoid issues in no-demo mode, notably when a timezone is required in sub records, like appointment types. Runbot-60487 Forward-Port-Of: odoo/enterprise#62061
Issue: --------- When a user lacks access to employee and setting permissions, the resource image does not appear. Fix: -------- We used the `hr.employee.public` model instead of `hr.employee` because everyone can access this one. Steps: --------- - Install the planning app - Create a user with planning user access, without employee and setting access - Create a Test employee(Test) - Create a shift and assign it to Test - Log in as the planning user
Original PR description
Issue: --------- When a user lacks access to employee and setting permissions, the resource image does not appear. Fix: -------- We used the `hr.employee.public` model instead of `hr.employee` because everyone can access this one. Steps: --------- - Install the planning app - Create a user with planning user access, without employee and setting access - Create a Test employee(Test) - Create a shift and assign it to Test - Log in as the planning user - Open planning and group by department Forward-Port-Of: odoo/enterprise#62251
[IMP] account_online_synchronization: populate swift/bic in journals Swift_code/BIC is already being returned by bank connection with odoofin accounts api We already populate the rest of the journals' details. So, We populate the swift/bic and link it with the journals Reason: Improve the user-experience Task-3891695 odoofin-pr: https://github.com/odoo/odoofin/pull/273 Forward-Port-Of: odoo/enterprise#61639
Original PR description
[IMP] account_online_synchronization: populate swift/bic in journals Swift_code/BIC is already being returned by bank connection with odoofin accounts api We already populate the rest of the journals' details. So, We populate the swift/bic and link it with the journals Reason: Improve the user-experience Task-3891695 odoofin-pr: https://github.com/odoo/odoofin/pull/273 Forward-Port-Of: odoo/enterprise#61639