Monday, August 31, 2020
36 changes · master
Enhancements to existing features
The recruitment onboarding tour now uses smaller tooltip boxes for short tips and keeps celebration messages visible longer. This makes the guided experience easier to read and more comfortable for users completing recruitment setup.
Original PR description
- reduce the size of the tooltip box when the tip is short - display the rainbow message longer on the screen to allow the user to read it. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fleet users can now record bike-specific details such as frame type, frame size, and electric assistance. This makes vehicle records more accurate for organizations managing bikes, and related replacement planning labels are now more generally worded for all vehicle types.
Original PR description
The three following fields have been added to fleet.vehicle: - frame_type (Selection) - frame_size (Float) - electric_assistance (Boolean) These fields are specific to bikes and are only displayed in form view when vehicle_type = bike "plan_to_change_car" has been changed to the more generic form "plan_to_change_vehicle". Task ID: 2238055 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
The Belgian payroll fleet module now uses a more general vehicle change planning option and includes bikes in the related availability checks. This helps employees and HR teams handle company bike choices consistently alongside cars.
Original PR description
…form 'plan_to_change_car' has been changed to the more generic form 'plan_to_change_vehicle'.
The manufacturing planning screen now uses clearer naming, showing “Master Schedule” instead of MPS, and displays a helpful example when no data is available. The layout is more compact with sticky headers and panels, and the default planning view is weekly so users can review schedules more easily.
Original PR description
Purpose: - Easy understanding of the Master Schedule by showing an explained example when there is no data. - Reduce the screen size per product when displaying all the rows. Specification: - Rename 'Master Production Schedule' to 'Master Schedule' and 'MPS' to 'MS'. - Set Default value 'weekly' instead of 'monthly'. task- 2247728
Indian payroll setup data has been made available by default instead of only as demo data, making payroll configuration more complete for real use. Employee and payslip views now include additional required payroll fields, and salary details more clearly show both allowances and deductions.
Original PR description
Task: https://www.odoo.com/web#id=1953228&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.56a4ca2cf0683628001b82e9096e1204
Document signing templates now have a dedicated Responsible person, separate from the user who created the template. When a template is shared, the share flow uses this Responsible person by default, making ownership clearer and reducing manual corrections.
Original PR description
PURPOSE Currently, when we share a template, by default, the responsible is the user who create the template. The aims of this task is to isolate the creator form the responsible SPECIFICATIONS Template properties Add a Responsible When we share a template Auto-Complete by the Responsible in properties. LINKS: PR: #11765 Task-id: 2277566
The Approvals app now uses updated list views, clearer empty-screen guidance, and visible category images to make requests easier to browse and understand. Users can also delete their own draft or cancelled approval requests, reducing clutter before submission or after cancellation.
Original PR description
change approvals general list view, change message in approvals to review, link to the new request menu in all approvals and my request, set align and display approvals category's logo
Resolved issues and error corrections
This fix improves how billable projects and tasks are handled when creating sales orders from timesheet-related workflows. It helps ensure project billing settings, related products, and sales order creation behave consistently, reducing billing setup errors for service projects.
Original PR description
taskID 2323997 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
- Create a Meeting for Contact X - Go to Contacts and open Contact X The Meetings smart button shows 1, but when clicking on it, all user & partner meetings are displayed. opw-2320299 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 Forward-Port-Of: odoo/odoo#56711
Original PR description
- Create a Meeting for Contact X - Go to Contacts and open Contact X The Meetings smart button shows 1, but when clicking on it, all user & partner meetings are displayed. opw-2320299 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 Forward-Port-Of: odoo/odoo#56711
Employee records now avoid storing unnecessary default images and use the linked user’s photo when no custom employee image is available. This keeps employee profiles visually consistent while reducing redundant image storage.
Original PR description
Check if the employee has an image and that it is different from the default one. If not, use the image of the linked user. 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 adjusts when sales line information is shown on field service tasks. It helps users see the right sales details at the right time, reducing confusion when managing service work linked to sales.
Original PR description
taskID 2323997
This change prevents an error when users run the Send Bills action for invoice digitization on customer invoices. It helps keep the digitization workflow running smoothly without unexpected interruptions.
Original PR description
purpose : purpose of this task to solve the trackback that occur while performing Send Bills for digitalization server action in customer invoices
Forward-Port-Of: odoo/odoo#56306
Original PR description
Forward-Port-Of: odoo/odoo#56306
task 362 --- ### Description of the issue/feature this PR addresses: Do not use internal_type = 'debit_note' in context when generating ad debit note and when we compute the default and available document types for the account.move Instead we use the debit_origin_id field. ### Current behavior before PR: When create a new debit note will create the account.move with a debit note document type by default ### Desired behavior after PR is merged: There is not functional change,
Original PR description
task 362 --- ### Description of the issue/feature this PR addresses: Do not use internal_type = 'debit_note' in context when generating ad debit note and when we compute the default and available document types for the account.move Instead we use the debit_origin_id field. ### Current behavior before PR: When create a new debit note will create the account.move with a debit note document type by default ### Desired behavior after PR is merged: There is not functional change, will have the same behavior, only improved how it is working tecnically. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56089
Logic of this method has been cleaned: return an error message or False (meaning, no error message). Forward-Port-Of: odoo/odoo#56689
Original PR description
Logic of this method has been cleaned: return an error message or False (meaning, no error message). Forward-Port-Of: odoo/odoo#56689
SPECIFICATIONS: MAIL GATEWAY Document creation or update is still done without auto subscribe. Indeed user running mailgateway or owning alias is not necessarily linked to the email author. That way we avoid auto subscription of irrelevant people. Posting message based on incoming email is now allowing auto subscription if there is an author found during email parsing. We also ensure this author is not root, to be sure he is not added in followers of documents. SPECIFICATIONS: INACT
Original PR description
SPECIFICATIONS: MAIL GATEWAY Document creation or update is still done without auto subscribe. Indeed user running mailgateway or owning alias is not necessarily linked to the email author. That way…
SPECIFICATIONS: MAIL GATEWAY
Document creation or update is still done without auto subscribe. Indeed user
running mailgateway or owning alias is not necessarily linked to the email
author. That way we avoid auto subscription of irrelevant people.
Posting message based on incoming email is now allowing auto subscription if
there is an author found during email parsing. We also ensure this author is
not root, to be sure he is not added in followers of documents.
SPECIFICATIONS: INACTIVE PARTNERS
Tested flows
* posting a message through an inactive partner (like automated actions
posting a message on behalf of an inactive partner);
* automatic subscription based on parent record (like an archived user and
partner following a project that should not be added as follower of sub
tasks);
* automatic subscription based on responsible field: this is already fixed
as user has to be active to receive a notification and be added in
followers;
LINKS
Task ID-2326281
PR odoo/odoo#56560
Closes to odoo/odoo#38383
Forward-Port-Of: odoo/odoo#56560Improve usability of open tabs in the POS. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56728
Original PR description
Improve usability of open tabs in the POS. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56728
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 Forward-Port-Of: odoo/odoo#56734
Original PR description
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 Forward-Port-Of: odoo/odoo#56734
The correct way to check if an invoice is paid is through the payment_state field. A similar fix was done in 13.0 with 276b9327b, but in 13.0 the field was called invoice_payment_state. It was renamed to payment_state in saas-13.3 with 8e4158af8. opw-2328046 Forward-Port-Of: odoo/odoo#56762
Original PR description
The correct way to check if an invoice is paid is through the payment_state field. A similar fix was done in 13.0 with 276b9327b, but in 13.0 the field was called invoice_payment_state. It was renamed to payment_state in saas-13.3 with 8e4158af8. opw-2328046 Forward-Port-Of: odoo/odoo#56762
DBO won't be here anymore 👋 This is my last commit, I had to find something harmless. Task-NaNNanNanNanNanNan Forward-Port-Of: odoo/odoo#56780
Original PR description
DBO won't be here anymore 👋 This is my last commit, I had to find something harmless. Task-NaNNanNanNanNanNan Forward-Port-Of: odoo/odoo#56780
Current behavior before PR: An empty list helper position not centered when search panel sidebar is there and some issue created while having a droplet on it as the position will shifting after a few seconds (sign_tour) Desired behavior after PR is merged: Set an empty list helper at a relative position and now it will always be displayed at the center whenever have a search panel sidebar LINKS PR-https://github.com/odoo/odoo/pull/56498 Task-2323988 Forward-Port-Of: odoo/odoo
Original PR description
Current behavior before PR: An empty list helper position not centered when search panel sidebar is there and some issue created while having a droplet on it as the position will shifting after a few seconds (sign_tour) Desired behavior after PR is merged: Set an empty list helper at a relative position and now it will always be displayed at the center whenever have a search panel sidebar LINKS PR-https://github.com/odoo/odoo/pull/56498 Task-2323988 Forward-Port-Of: odoo/odoo#56498
go to hr_recruitment app - open applications menu - go to all applications menu click on add symbol - the cachemiss raised due to department_id -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56019
Original PR description
go to hr_recruitment app - open applications menu - go to all applications menu click on add symbol - the cachemiss raised due to department_id -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56019
**PURPOSE** There is an unwanted line break in the company address in the report header. The street value with some long string will breaks into two line instead of display in the single line. **SPEC** we have used the div tag instead span tag to display the whole string in the block format. So it will display the string in the proper format. Task : 2321081 Forward-Port-Of: odoo/odoo#56092
Original PR description
**PURPOSE** There is an unwanted line break in the company address in the report header. The street value with some long string will breaks into two line instead of display in the single line. **SPEC** we have used the div tag instead span tag to display the whole string in the block format. So it will display the string in the proper format. Task : 2321081 Forward-Port-Of: odoo/odoo#56092
* `not all` --> `any(not)` for earlier returns * `all([generator])` --> `all(generator)` to avoid list cast for nothing (it is better managed by the `all` call). Enterprise PR: https://github.com/odoo/enterprise/pull/12486 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56060
Original PR description
* `not all` --> `any(not)` for earlier returns * `all([generator])` --> `all(generator)` to avoid list cast for nothing (it is better managed by the `all` call). Enterprise PR: https://github.com/odoo/enterprise/pull/12486 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56060
Task: <a href="https://www.odoo.com/web?#id=2320549&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720">2320549</a> Forward-Port-Of: odoo/enterprise#12727 Forward-Port-Of: odoo/enterprise#12478
Original PR description
Task: <a href="https://www.odoo.com/web?#id=2320549&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720">2320549</a> Forward-Port-Of: odoo/enterprise#12727 Forward-Port-Of: odoo/enterprise#12478
* not all --> any(not) for earlier returns * all([generator]) --> all(generator) to avoid list cast for nothing (it is better managed by the all call). Community PR: https://github.com/odoo/odoo/pull/56060 Forward-Port-Of: odoo/enterprise#12486
Original PR description
* not all --> any(not) for earlier returns * all([generator]) --> all(generator) to avoid list cast for nothing (it is better managed by the all call). Community PR: https://github.com/odoo/odoo/pull/56060 Forward-Port-Of: odoo/enterprise#12486
Before this commit, and since Odoo 10.0, the `balance` of a Yodlee `account.online.provider` was only written at the very first synchronization, but never updated after that because of a wrong line of code. It was not a problem before saas-13.3 because this value was never used elsewhere. However, since 6136b991e1a Yodlee is calling `online_sync_bank_statement` with `self.balance` as last argument, so this value is now used. The issue is that new synchronizations are always created with t
Original PR description
Before this commit, and since Odoo 10.0, the `balance` of a Yodlee `account.online.provider` was only written at the very first synchronization, but never updated after that because of a wrong line of code. It was not a problem before saas-13.3 because this value was never used elsewhere. However, since 6136b991e1a Yodlee is calling `online_sync_bank_statement` with `self.balance` as last argument, so this value is now used. The issue is that new synchronizations are always created with the same wrong closing balance, which is the closing balance of the very first synchronization. Forward-Port-Of: odoo/enterprise#12790
[FIX] hr_contract_salary: update 13rd month salary configuration Before this commit, in the salary configuration, if the parameters were modified, the 13rd month wasn't updated. wage_with_holidays must to be added into the fields that are updated when the net salary is updated. opw-2309679 ---------------------------------------------------------------------------------- [FIX] l10n_be_hr_contract_salary: update double holiday salary configuration Before this commit, in the B
Original PR description
[FIX] hr_contract_salary: update 13rd month salary configuration Before this commit, in the salary configuration, if the parameters were modified, the 13rd month wasn't updated. wage_with_holidays must to be added into the fields that are updated when the net salary is updated. opw-2309679 ---------------------------------------------------------------------------------- [FIX] l10n_be_hr_contract_salary: update double holiday salary configuration Before this commit, in the Belgian salary configuration, if the parameters were modified, the double holiday salary wasn't updated. double_holiday_wage must to be added into the fields that are updated when the net salary is updated. opw-2309679 Forward-Port-Of: odoo/enterprise#12396 Forward-Port-Of: odoo/enterprise#12293
OCR now detects SWIFT code. When a new account is created for a new partner, if the bank corresponding to the detected SWIFT code exists in the DB we link this bank to the account. Server side PR: https://github.com/odoo/iap-apps/pull/236 Forward-Port-Of: odoo/enterprise#12779 Forward-Port-Of: odoo/enterprise#12640
Original PR description
OCR now detects SWIFT code. When a new account is created for a new partner, if the bank corresponding to the detected SWIFT code exists in the DB we link this bank to the account. Server side PR: https://github.com/odoo/iap-apps/pull/236 Forward-Port-Of: odoo/enterprise#12779 Forward-Port-Of: odoo/enterprise#12640
Currently, in the field services module when we edit the quantity of a product by clicking on it then it produces a traceback. step to reproduce: -Create an FSM task -Products -edit the quantity of a product by clicking on it So in this commit, we check the value of quantity. LINKS PR: #12330 Task-Id: 2315103 Forward-Port-Of: odoo/enterprise#12330
Original PR description
Currently, in the field services module when we edit the quantity of a product by clicking on it then it produces a traceback. step to reproduce: -Create an FSM task -Products -edit the quantity of a product by clicking on it So in this commit, we check the value of quantity. LINKS PR: #12330 Task-Id: 2315103 Forward-Port-Of: odoo/enterprise#12330
Bug === In social, in the feed view, you can hover the statistics of the accounts to get information about the number. The popover is sometime stuck and we must refresh the page to make it disappear. How to reproduce ? 1. Hover the statistics to make the popover visible 2. With chrome, press "AltGr + LeftArrow" to go back without moving the mouse 3. When you'll change the view, the popover will be stuck Solution ======== The bootstrap popover must be hidden before the eleme
Original PR description
Bug === In social, in the feed view, you can hover the statistics of the accounts to get information about the number. The popover is sometime stuck and we must refresh the page to make it disappear. How to reproduce ? 1. Hover the statistics to make the popover visible 2. With chrome, press "AltGr + LeftArrow" to go back without moving the mouse 3. When you'll change the view, the popover will be stuck Solution ======== The bootstrap popover must be hidden before the element is detached from the DOM. Task-2248204 Forward-Port-Of: odoo/enterprise#12683 Forward-Port-Of: odoo/enterprise#10459
Steps to reproduce the bug: - Create a journal entry - View Mexican-localization Trial Balance - Compare with multiple previous periods Bug: The created journal entry was displayed in the first period in the comparison, no matter when it was originally created. opw:2307794 Forward-Port-Of: odoo/enterprise#12659
Original PR description
Steps to reproduce the bug: - Create a journal entry - View Mexican-localization Trial Balance - Compare with multiple previous periods Bug: The created journal entry was displayed in the first period in the comparison, no matter when it was originally created. opw:2307794 Forward-Port-Of: odoo/enterprise#12659
The value of "quantity" appears in a wrong column : "origin country". This is due to account_intrastat. **Task ID: 2301256** Forward-Port-Of: odoo/enterprise#12476
Original PR description
The value of "quantity" appears in a wrong column : "origin country". This is due to account_intrastat. **Task ID: 2301256** Forward-Port-Of: odoo/enterprise#12476
send the user language and company country code to help detect dates Forward-Port-Of: odoo/enterprise#12689
Original PR description
send the user language and company country code to help detect dates Forward-Port-Of: odoo/enterprise#12689
Without demo data Enterprise part of odoo/odoo#56306 Forward-Port-Of: odoo/enterprise#12570
Original PR description
Without demo data Enterprise part of odoo/odoo#56306 Forward-Port-Of: odoo/enterprise#12570
When processing on mobile, via the barcode app, a transfer with product tracked by serial numbers, the quantity done isn't always updated. How to reproduce: - Create a product tracked by Serial Number and set a barcode for it; - Put at least two qty. in stock for this product; - Create a delivery for at least 2 of these product; - Open this delivery with the barcode app; - On the form view, scan the product's barcode: -> It opens the barcode lot lines wizard - Scan one
Original PR description
When processing on mobile, via the barcode app, a transfer with product tracked by serial numbers, the quantity done isn't always updated.
How to reproduce:
- Create a product tracked by Serial Number and set a barcode for it;
- Put at least two qty. in stock for this product;
- Create a delivery for at least 2 of these product;
- Open this delivery with the barcode app;
- On the form view, scan the product's barcode:
-> It opens the barcode lot lines wizard
- Scan one of the SN:
-> It updates correctly the lot qty. done (1/x);
- Scan an another SN:
-> It doesn't update the lot qty. done (still 1/x), even if the lot line qty. done is correclty to one.
To fix that, this commit adds an onchange on `stock_barcode.lot` `stock_barcode_lot_line_ids` to force the update of the `qty_done`.
opw-2276723
Forward-Port-Of: odoo/enterprise#12717