Daily updates from Odoo
Navigate
Branch
Friday, June 30, 2023
16 changes
Enhancements to existing features
The Knowledge app’s emoji picker has been repositioned from the page header to the bottom area. This makes the editing interface cleaner and keeps emoji selection available without competing with header actions.
Original PR description
https://github.com/odoo/odoo/pull/116060
Spreadsheet templates can now be edited collaboratively, similar to regular spreadsheets. This makes it easier for teams to build and update shared templates together, reducing handoffs and version conflicts.
Original PR description
This PR implements the collaborative editing in spreadsheet templates. The underlying idea is the same as collaborative editing on normal spreadsheets. task [3252858](https://www.odoo.com/web#id=3252858&cids=1&menu_id=4720&model=project.task&view_type=form)
The Planning app now includes additional sample data for material resources such as cranes, projectors, and scanners, along with scheduled slots for those resources. This makes demo environments more realistic and helps users better understand how material resource planning works.
Original PR description
In this commit improve the following generic UX - add demo data for material resources and created slots for that material resources - add role crane and create resources for crane: crane 1, crane 2 and created slots for these resources - Same for projector and scanner task-3128509
Resolved issues and error corrections
Appointment confirmation emails now calculate the day using the appointment's timezone. This prevents customers in timezones such as Pacific/Auckland from receiving emails with the wrong date when booking around midnight.
Original PR description
Steps to reproduce: ------------------- - create an appointment with the Pacific/Auckland timezone (UTC +12:00); - with a public user, register for an appointment on the website before 12 AM. (We can see the email sent in the chatter) Issue: ------ The number of the day used in the template does not correspond to the timezone. Solution: --------- Use `mail_tz` to obtain the day according to the timezone. opw-3267279
Code cleanup and technical improvements
Several onboarding checklists and setup steps are now managed through Odoo’s shared onboarding system. This makes setup guidance more consistent across invoicing, sales, consolidation, payments, appointments, and website sales dashboards, especially for multi-company use.
Original PR description
Purpose: Use the onboarding module to manage onboardings, steps and their progress for the different companies This PR (and related COM one) moves these: * `account`:" invoicing" and "dashboard" + "vendor bill" and "sale_tax" steps * `sale`: "quotation" * `account_consolidation`: "dashboard" * `payment`: payment provider setup step, used in different modules. * `website_sale_dashboard` Task-3025136 See https://github.com/odoo/odoo/pull/104223 See https://github.com/odoo/upgrade/pull/4021
Miscellaneous changes
Forward-Port-Of: odoo/enterprise#43349
Original PR description
Forward-Port-Of: odoo/enterprise#43349
Forward-Port-Of: odoo/enterprise#43267
Original PR description
Forward-Port-Of: odoo/enterprise#43267
Step to reproduce: - Create a sub with a pre-invoiced recurring and a post-invoice recurring product - Invoice the sub - Upsell the Sub with 1 qty for both product - Invoice the upsell - Add delivered qty to the post-invoice product - Invoice the upsell Current behaviour: - The second invoice for the upsell also invoice the line that have already been invoiced during the first invoice. This is because subscription module add recurring line even if they are not in the case of an upsell.
Original PR description
Step to reproduce: - Create a sub with a pre-invoiced recurring and a post-invoice recurring product - Invoice the sub - Upsell the Sub with 1 qty for both product - Invoice the upsell - Add delivered qty to the post-invoice product - Invoice the upsell Current behaviour: - The second invoice for the upsell also invoice the line that have already been invoiced during the first invoice. This is because subscription module add recurring line even if they are not in the case of an upsell. Behviour after the change: - The second invoice only invoice the post-invoice line. The sale `_get_invoiceable_line` is now also used for upsell as they don't need recurring behaviour. opw-3279273 Forward-Port-Of: odoo/enterprise#42969 Forward-Port-Of: odoo/enterprise#42606
In case of a foreign currency payment made in a bank journal in the same foreign currency, some info was removed by mistake. Steps to reproduce the issue: 1) Set company's location to Peru and the currency to PEN. 2) Install the Peruvian accounting module l10n_pe. 3) Create a bank account with the default currency set to USD. 4) Create a corresponding bank journal with currency set to USD. 5) Create and register payment for a customer invoice in PEN, attributed to that journal. 6)
Original PR description
In case of a foreign currency payment made in a bank journal in the same foreign currency, some info was removed by mistake. Steps to reproduce the issue: 1) Set company's location to Peru and the currency to PEN. 2) Install the Peruvian accounting module l10n_pe. 3) Create a bank account with the default currency set to USD. 4) Create a corresponding bank journal with currency set to USD. 5) Create and register payment for a customer invoice in PEN, attributed to that journal. 6) Create and register payment for a customer invoice in USD, attributed to that journal. 7) From the dashboard, click 'Outstanding Payments/Receipts' for that journal. 8) Label appears for the payments made in PEN, but not for the ones in USD. opw-3332049 Forward-Port-Of: odoo/enterprise#43065
The requested date is done date which does not exist before the delivery is validated. So I have used if condition so that it does not produce error if the user tries to generate the report before validating the delivery. Steps To Reproduce: 1. Add chile localization and create a sales order and validate the delivery. 2. Generate the Delivery Guide from the print drop down. Current Behaviour: The date in the report generated is scheduled date. Expected Behaviour: The date in the rep
Original PR description
The requested date is done date which does not exist before the delivery is validated. So I have used if condition so that it does not produce error if the user tries to generate the report before validating the delivery. Steps To Reproduce: 1. Add chile localization and create a sales order and validate the delivery. 2. Generate the Delivery Guide from the print drop down. Current Behaviour: The date in the report generated is scheduled date. Expected Behaviour: The date in the report should be effective date. OPW-3288178 Forward-Port-Of: odoo/enterprise#42929 Forward-Port-Of: odoo/enterprise#41848
Steps to reproduce: - create an MO and on its WO add a time tracking line - set its Work Center requires log in to false - mark MO as done Bug: extra line on the cost analysis Fix: only set employee only on WO that requires log in Forward-Port-Of: odoo/enterprise#43282
Original PR description
Steps to reproduce: - create an MO and on its WO add a time tracking line - set its Work Center requires log in to false - mark MO as done Bug: extra line on the cost analysis Fix: only set employee only on WO that requires log in Forward-Port-Of: odoo/enterprise#43282
Currently, the balance sheet report excludes 1931 account from Cash and bank and includes it in Other liabilities. The account should be included in Cash and bank, as that is the correct section for this type of account. opw-3336373 Forward-Port-Of: odoo/enterprise#43355 Forward-Port-Of: odoo/enterprise#43276
Original PR description
Currently, the balance sheet report excludes 1931 account from Cash and bank and includes it in Other liabilities. The account should be included in Cash and bank, as that is the correct section for this type of account. opw-3336373 Forward-Port-Of: odoo/enterprise#43355 Forward-Port-Of: odoo/enterprise#43276
## Current behaviour Sale Order Items on a task shows only SO related to the current customer, or all SO if there is no customer on the task. ## Expected behaviour If we have a customer on the task, show also SOs from child contact of that customer (mirror the SO count in `Contacts` app) ## Steps to reproduce - Install Contacts, Sales, Field Services - Create 4 contacts, a company, with child contact A and B, a contact C who is child of A - For each contact create an SO and confirm a
Original PR description
## Current behaviour Sale Order Items on a task shows only SO related to the current customer, or all SO if there is no customer on the task. ## Expected behaviour If we have a customer on the task,…
## Current behaviour Sale Order Items on a task shows only SO related to the current customer, or all SO if there is no customer on the task. ## Expected behaviour If we have a customer on the task, show also SOs from child contact of that customer (mirror the SO count in `Contacts` app) ## Steps to reproduce - Install Contacts, Sales, Field Services - Create 4 contacts, a company, with child contact A and B, a contact C who is child of A - For each contact create an SO and confirm a field service product - Now on any task, add the company as customer. - In the Sale Order Item we can't select any of the SOs from the child contacts of the company. ## Reason for the problem Since 184597b13dc5cd7d310539f087f4e60f641320e1 where we wanted to show all SOs when no `partner_id` was set on the task, we made use of `=?` operator which is `True` when there is no `partner_id`, but it matched only for `=` when it's not the case, not taking into account `child_of` of said contact. ## Fix Extend the domain with an `OR` to take child contacts if the `partner_id` is not `False`. ## Affected versions - 16.0 - saas-16.1 - saas-16.2 - saas-16.3 - master --- opw-3374191 Linked PR: https://github.com/odoo/odoo/pull/126285 Forward-Port-Of: odoo/enterprise#43093
For some reason, half of the appoval css was removed when updating odoo to the new design. This commit copies the old CSS from 16.2 Before ======  After ====  opw-3379746 Forward-Port-Of: odoo/enterprise#43371
Original PR description
For some reason, half of the appoval css was removed when updating odoo to the new design. This commit copies the old CSS from 16.2 Before ======  After ====  opw-3379746 Forward-Port-Of: odoo/enterprise#43371
Purpose: In case employeer puts themselves as their manager for an appraisal, they suddenly will be able to see all the answers for their appraisal. Which is too risky. After this commit, the following won't be possible. task - 3384817 Forward-Port-Of: odoo/enterprise#43290
Original PR description
Purpose: In case employeer puts themselves as their manager for an appraisal, they suddenly will be able to see all the answers for their appraisal. Which is too risky. After this commit, the following won't be possible. task - 3384817 Forward-Port-Of: odoo/enterprise#43290
Before this commit, since #36459, the partner field in project and task is hidden if the project is non-billable or not fsm one. When Sales app is installed, all projects with a partner set or with at least one of their tasks with a partner set, the projects are made billable in `sale_project` module. This commit filters the projects to only make billable the basic projects and not the fsm projects. Forward-Port-Of: odoo/enterprise#43352
Original PR description
Before this commit, since #36459, the partner field in project and task is hidden if the project is non-billable or not fsm one. When Sales app is installed, all projects with a partner set or with at least one of their tasks with a partner set, the projects are made billable in `sale_project` module. This commit filters the projects to only make billable the basic projects and not the fsm projects. Forward-Port-Of: odoo/enterprise#43352