Tuesday, November 17, 2020
61 changes · master
Enhancements to existing features
Several Odoo apps now have refreshed icons, giving users a more consistent and polished visual experience. This is a presentation-only update and does not change business workflows or app functionality.
Original PR description
Updated App icons of the following modules:
-fetchmail
-iap
-mail_bot
-partner_autocomplete
-sale_timesheet
-sms
-snailmail
-helpdesk_account
-helpdesk_fsm
-helpdesk_repair
-helpdesk_sale_coupon
-helpdesk_stock
-helpdesk_timesheet
-hr_expense_extract
-industry_fsm_sale
-industry_fsm_stock
-project_forecast
-timer
-voip_onsip
-website_helpdesk_forum
TaskID: 2312083
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prAccounting move line exports can now include the currency symbol used on each line. This makes CSV files from reports such as the partner ledger clearer and easier to interpret when multiple currencies are involved.
Original PR description
Currently, when exporting move lines via for example the partner ledger, we are not displaying the currency in any way in the CSV. This will add an optional field in the list view of the aml which contains the currency symbol, which will then be exported into the CSV. task id #2381355 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The HR Contract module now includes its own app icon. This makes the app easier to recognize in the Odoo interface and improves visual consistency across modules.
Original PR description
In this commit the App icon is added for the hr_contract module task-2360070 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The HR Settings tab on employee records has been reorganized so related information is easier to find. Payroll details and application-related settings are now grouped separately, helping HR teams review and update employee information more efficiently.
Original PR description
Improvements in the HR Settings tab in the Employee Form by re-organising various information. By this commit, mobility_card, next_appraisal_date and timesheet_cost fields are moved to "Application Settings" group and the fields, job_id, registration_number, language_code and nif_country_code are moved to "Payroll" group in the HR Settings tab. task - 2351762 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Sign app no longer shows the “Upload a PDF to Sign” option when used on mobile. This prevents mobile users from creating signing templates in a flow that is not supported, reducing confusion and keeping behavior consistent across the app.
Original PR description
Purpose of this task is, when we use the mobile app, the template to 'UPLOAD A PDF To SIGN' was visible from mobile view. In this commit, when we use the mobile app we shouldn't be authorised to create a template. task -id: 2335667 PR: 13115
The employee form’s HR Settings tab has been reorganized to make key information easier to find. Payroll-related details are now grouped separately from application settings, helping HR teams navigate employee records more efficiently.
Original PR description
Improvements in the HR Settings tab in the Employee Form by re-organising various information. By this commit, mobility_card, next_appraisal_date and timesheet_cost fields are moved to "Application Settings" group and the fields, job_id, registration_number, language_code and nif_country_code are moved to "Payroll" group in the HR Settings tab. task - 2351762 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Appraisal menu helper text was updated to be shorter and easier to understand. This makes the appraisal area feel cleaner and helps users focus on the next action without extra feature-focused wording.
Original PR description
The purpose of this task is to improve the Appraisal's action helper. so, this commit changed the helper message for the appraisal menu. TaskID: 2360930
Several Odoo apps received refreshed icons to improve visual consistency and recognition in the app launcher. This is a cosmetic update only and does not change business workflows or features.
Original PR description
Updated App icons of the following modules:
-fetchmail
-iap
-mail_bot
-partner_autocomplete
-sale_timesheet
-sms
-snailmail
-helpdesk_account
-helpdesk_fsm
-helpdesk_repair
-helpdesk_sale_coupon
-helpdesk_stock
-helpdesk_timesheet
-hr_expense_extract
-industry_fsm_sale
-industry_fsm_stock
-project_forecast
-timer
-voip_onsip
-website_helpdesk_forum
TaskID: 2312083
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prResolved issues and error corrections
This fix reorganizes website form files into the expected folders so Odoo can correctly recognize its own JavaScript and style files. This helps translation tools find text that needs localization, improving multilingual website form support without changing user-facing features.
Original PR description
The js files must be inside a `static/src/js` directory and scss inside
`static/src/scss` by convention.
This allows, for instance, to detect js files that are made by odoo
(in opposition to external libraries) and extract translatable terms
in the _export_translatable_resources method.
Introduced at e7152652754a14ac784e2
opw-2381030Miscellaneous changes
Fleet settings no longer reference a non-existent accounting add-on. This prevents confusion or errors when users configure fleet-related options.
Original PR description
The module fleet_account doesn't exist opw:2382169
Fixed an issue where the coupon rule selector could be hidden when opened inside a popup window. This makes coupon setup smoother and prevents users from losing access to selection options in the dialog.
Original PR description
Currently, when inline domain selector is inside the modal dialog then the domain selector popover hide inside the modal body due to auto scroll on modal body. domain selector in dialog is rare case and here there is less content inside the coupon dialog due to that we can use the overflow visible for this specific wizard(modal dialog). So in this commit, fix the issues by adding overflow property in the modal body due to that, it will always display on top of the modal. TaskID: 2225272
User-facing text in the Project app was corrected for grammar, punctuation, capitalization, and word choice. This makes labels and messages easier to understand and gives users a more polished experience without changing functionality.
Original PR description
This commit fixes various types of language errors in strings visible to the user, including - singular/plural mix-ups - missing or incorrect punctuation - missing or incorrect articles - inconsistent use of title case and sentence case and other capitalization errors - mixed-up words - missing words - incorrect prepositions - missing or incorrect apostrophes Task 2337369
This fix improves the guided tour experience by making the droplet animation stay aligned with the correct button while users scroll. It helps prevent confusion during steps such as signing a document, making onboarding guidance smoother and clearer.
Original PR description
[FIX] web_tour: fix issue of droplet animation follow the wrong button Currently, when signing the document during the tour, the droplet animation don't follow correctly the button. So in this commit, due to timeout/Aniamation there is lag on scroll so need to change 50 to 0.1, now droplet have correctly follow the button, or appear after the button animation TaskID: 2296010
The contract history view now lists employee contracts with the most recent start dates first. This makes it easier for HR users to quickly see the latest contract information without manually scanning or reordering records.
Original PR description
…act_history
Prior to this commit:
* The contract_ids one2many widget in the hr_contract_history form was not sorted
desc.
After this commit:
* The contract_ids one2many widget in the hr_contract_history form is correctly sorted
desc.
related PR: odoo/enterprise#14647, odoo/upgrade#1939
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThe Notes app now matches other Odoo areas when users open scheduled activities from the top menu. Instead of showing all notes, it defaults to notes with activities due today or overdue, making the activity view more focused and consistent.
Original PR description
…ties For all the other models, when clicking the line in the "activities" top menu, you arrive in a kanban view which is filtered to only list objects which actually have scheduled activities on them, for notes it displayed all the user's notes regardless of any activity scheduled or not. To fix this defualt filter was to be set to "Today or Late Activities". The changes made are in the .js file where the data.filter is set to activities_overdue. taskID-2312083 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The update prevents users from accidentally entering bulk-edit mode in onboarding list screens. This helps users open records normally during setup and avoids confusion that could make onboarding feel blocked.
Original PR description
Removing multi_edit="1" from the treeviews because of when user tend to get 'stuck' through onboarding because of multi edit feature. When records are selected user can't open that records just when they leaves from multi edit / mass edition then that feature will works. **TaskID** : 2373161
Courtesy of Transifex's translators for reporting bad/unclear sentences. Forward-Port-Of: odoo/odoo#61785
Original PR description
Courtesy of Transifex's translators for reporting bad/unclear sentences. Forward-Port-Of: odoo/odoo#61785
Before this commit, when an invalid element was dropped (e.g. dragging a mention) the drop area freeze and make the UI unusable. task-2373971 Forward-Port-Of: odoo/odoo#61380
Original PR description
Before this commit, when an invalid element was dropped (e.g. dragging a mention) the drop area freeze and make the UI unusable. task-2373971 Forward-Port-Of: odoo/odoo#61380
Description of the issue/feature this PR addresses: Set the right country on the tax report for Switzerland Current behavior before PR: The country set on the tax report for this chart of account is set to Brazil Desired behavior after PR is merged: The country set on the tax report for this chart of account is set to Switzerland (as it should). Follow-up of https://github.com/odoo/odoo/pull/61630 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit
Original PR description
Description of the issue/feature this PR addresses: Set the right country on the tax report for Switzerland Current behavior before PR: The country set on the tax report for this chart of account is set to Brazil Desired behavior after PR is merged: The country set on the tax report for this chart of account is set to Switzerland (as it should). Follow-up of https://github.com/odoo/odoo/pull/61630 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61793
Steps to reproduce the bug: 1.Create an automated action with the following: - Model: Task (project.task) - Active: True - Trigger: On Update - Action To Do: Create Next Activity 2. Open or create a task in Project module 3. Edit 4. Change or set customer (partner_id) Bug: An error message was raised. opw:2376492 Forward-Port-Of: odoo/odoo#61800
Original PR description
Steps to reproduce the bug: 1.Create an automated action with the following: - Model: Task (project.task) - Active: True - Trigger: On Update - Action To Do: Create Next Activity 2. Open or create a task in Project module 3. Edit 4. Change or set customer (partner_id) Bug: An error message was raised. opw:2376492 Forward-Port-Of: odoo/odoo#61800
# Purpose The first stage has not always its sequence equal to 1. So if the probability was for example equal to 0, then the salesman will not be set to the new lead. # Specifications Since when we create a lead, the default stage is automaticaly the first one in the sequence order. We only need to check if the lead is not already won (probability = 100) when we create a lead and try to assign the salesman to it. task-2329327 Forward-Port-Of: odoo/odoo#58153
Original PR description
# Purpose The first stage has not always its sequence equal to 1. So if the probability was for example equal to 0, then the salesman will not be set to the new lead. # Specifications Since when we create a lead, the default stage is automaticaly the first one in the sequence order. We only need to check if the lead is not already won (probability = 100) when we create a lead and try to assign the salesman to it. task-2329327 Forward-Port-Of: odoo/odoo#58153
Behavior prior to the commit: - when setting the customer (partner) on a sales order, the sales team is set based on the partner's sales person. If there is no sales person on the partner then the team defaults to the first team in sequence for the company. - the team set on the partner is not used (by default, this field is not visible, but it can be set from server action or added via studio). In Odoo 12.0 the team set on the partner was used as a fallback, but this was removed in
Original PR description
Behavior prior to the commit: - when setting the customer (partner) on a sales order, the sales team is set based on the partner's sales person. If there is no sales person on the partner then the…
Behavior prior to the commit: - when setting the customer (partner) on a sales order, the sales team is set based on the partner's sales person. If there is no sales person on the partner then the team defaults to the first team in sequence for the company. - the team set on the partner is not used (by default, this field is not visible, but it can be set from server action or added via studio). In Odoo 12.0 the team set on the partner was used as a fallback, but this was removed in commit 242be00429a9 Behavior after the commit: - the partner's team is used as fallback when the partner is updated - when the salesperson is updated on the quote, we also use the current team as fallback (since presumably this was set either from the partner, or using the existing default rule, there is no reason to change it) Note: - Change in existing installation is expected to be minimal since it only affects the customers who are making use of the partner.team_id field, not populated or displayed by default, but there is a risk for a customer who: 1. has that field populated on existing partners (maybe upgraded from an old install where it was displayed?) 2. is relying on the new (as of v13.0) behavior of assigning the default sales team based on the sequence opw-2351868 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61794 Forward-Port-Of: odoo/odoo#61527
Due to recent legal changes in EU, you cannot install tracking cookies in a user's browser without explicit consent. Before this patch, Odoo embedded youtube videos were violating that law (AFAIK & IANAL). With this simple patch, you benefit from YouTube's offering to embed videos without cookies. The UI remains the same, but no tracking is done. This feature is supported upstream in YouTube when you enable enhanced privacy to embed video: . With this simple patch, you benefit from YouTube's offering to embed videos without cookies. The UI remains the same, but no tracking is done. This feature is supported upstream in YouTube when you enable enhanced privacy to embed video:  This is how demo slide cookies look before the patch:  And after:  @Tecnativa TT26153 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61601 Forward-Port-Of: odoo/odoo#61581
**Current behavior before PR:** When trying to send the notification for the user form, it shows a traceback. This is happening after https://github.com/odoo/odoo/commit/ab4000fb3cf8fa54ba714ceceec391b78d73755e **Desired behavior after PR is merged:** Send the notification without any traceback as handle the MailDeliveryException inside CrashManager Task-2333121 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port
Original PR description
**Current behavior before PR:** When trying to send the notification for the user form, it shows a traceback. This is happening after https://github.com/odoo/odoo/commit/ab4000fb3cf8fa54ba714ceceec391b78d73755e **Desired behavior after PR is merged:** Send the notification without any traceback as handle the MailDeliveryException inside CrashManager Task-2333121 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60938
Before this commit payment tokens had no name for Test Payment Acquirer After this commit tokens generated by Test Payment Acquirer have a name that combines the last 4 digits of the card number and the card account holder name https://github.com/odoo/odoo/issues/50965 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-p
Original PR description
Before this commit payment tokens had no name for Test Payment Acquirer After this commit tokens generated by Test Payment Acquirer have a name that combines the last 4 digits of the card number and the card account holder name https://github.com/odoo/odoo/issues/50965 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#61423
This patch guarantees that computed fields with `compute_sudo=True` do not cause access errors when fetched from database. This fixes a non-deterministic access error upon `commit`, where fields are recomputed and flushed with some random environment. The method `recompute` performs its duty by accessing the fields to recompute. The compute method of a field is called but does not assign it. As the field is not in cache, its value is read from database. However, as the latter is not
Original PR description
This patch guarantees that computed fields with `compute_sudo=True` do not cause access errors when fetched from database. This fixes a non-deterministic access error upon `commit`, where fields are recomputed and flushed with some random environment. The method `recompute` performs its duty by accessing the fields to recompute. The compute method of a field is called but does not assign it. As the field is not in cache, its value is read from database. However, as the latter is not done in superuser mode, it may cause some access error. Forward-Port-Of: odoo/odoo#61820
What are the steps to reproduce your issue ? 1. Go to 'odoo.com/trial' and create a database with 'account' or 1. Start local server with a new database and with '--without-demo=all --init=account' 2. Change main currency from 'EUR' to 'USD' in settings What is currently happening? Error raised when trying to install 'point_of_sale' What are you expecting to happen? Install 'point_of_sale' normally even after changing main currency Why is this h
Original PR description
What are the steps to reproduce your issue ?
1. Go to 'odoo.com/trial' and create a database with 'account'
or
1. Start local server with a new database and with '--without-demo=all --init=account'
2. Change main currency from 'EUR' to 'USD' in settings
What is currently happening?
Error raised when trying to install 'point_of_sale'
What are you expecting to happen?
Install 'point_of_sale' normally even after changing main currency
Why is this happening?
But there is a condition which verifies that there is not already
a pricelist with the currency we want to set or with the currency
of the company. Otherwise it prevents the pricelist modification
How to fix the bug ?
Change the condition so that it allows the change of the pricelist
in the case where the currency we want to set is not the same as the
currency of the company
opw-2376457
Forward-Port-Of: odoo/odoo#61764Before this commit, the last rating value returned was not the last consumed one. TaskID: 2260685 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#60531
Original PR description
Before this commit, the last rating value returned was not the last consumed one. TaskID: 2260685 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#60531
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#61826 Forward-Port-Of: odoo/odoo#61797
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#61826 Forward-Port-Of: odoo/odoo#61797
STEPS: * create 3 attributes with custom values option * create a quotation with a product having all 3 attributes and custom values * select the custom values for attributes in different orders for each SO line BEFORE: Product description get random order for the custom attributes list AFTER: Order is fine --- opw-2379778 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have sign
Original PR description
STEPS: * create 3 attributes with custom values option * create a quotation with a product having all 3 attributes and custom values * select the custom values for attributes in different orders for each SO line BEFORE: Product description get random order for the custom attributes list AFTER: Order is fine --- opw-2379778 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#61836
Problem ------- For regular allocation that have an empty date_from (Allocation existing before 14.0), it's not possible to save any change since an invisible field is required and cannot be set. Solution -------- The field date from should be only required for type accrual -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61885
Original PR description
Problem ------- For regular allocation that have an empty date_from (Allocation existing before 14.0), it's not possible to save any change since an invisible field is required and cannot be set. Solution -------- The field date from should be only required for type accrual -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61885
With PostgreSQL version 9.6, it was impossible to install the module fleet A traceback was raised saying: could not determine which collation to use for view column "cost_type" Forward-Port-Of: odoo/odoo#61829
Original PR description
With PostgreSQL version 9.6, it was impossible to install the module fleet A traceback was raised saying: could not determine which collation to use for view column "cost_type" Forward-Port-Of: odoo/odoo#61829
Description of the issue/feature this PR addresses: When you send Proforma, in object you see Quotation -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61471
Original PR description
Description of the issue/feature this PR addresses: When you send Proforma, in object you see Quotation -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61471
Steps to reproduce the bug: - Let's consider a product P with price=100€, Timesheets on tasks and Create a task in sales order's project - Create a SO with 1 P and confirm it - A project PR and a task T have been created - Assign an employee E to T and record 01:00 hour - Create an invoice I from the SO and confirm I - Go to the project overview of the SO Bug: 100€ was counted twice in Non billable task and in Billed on Timesheets PS: When validating I, an analytic line L is
Original PR description
Steps to reproduce the bug: - Let's consider a product P with price=100€, Timesheets on tasks and Create a task in sales order's project - Create a SO with 1 P and confirm it - A project PR and a task T have been created - Assign an employee E to T and record 01:00 hour - Create an invoice I from the SO and confirm I - Go to the project overview of the SO Bug: 100€ was counted twice in Non billable task and in Billed on Timesheets PS: When validating I, an analytic line L is created and L is not linked to PR. That's why 100€ was counted twice. As implemented here: https://github.com/odoo/odoo/blob/14.0/addons/sale_timesheet/views/hr_timesheet_templates.xml#L133 The non billable tasks must be all the tasks linked to the current project without sale_line_id. So we can deduct that the analytic lines of the non billable tasks must be the analytic lines linked to the current project but without so_line opw:2370418 Forward-Port-Of: odoo/odoo#61433
Before this commit, payment test would create token without a name. When you tried to pay your subscription on the portal with these, the following error would occurs: ``` Error to render compiling AST AttributeError: 'bool' object has no attribute 'replace' Template: sale_subscription.subscription Path: /t/t[2]/div/t/t[2]/ul/li[1]/div[3]/t Node: <t t-esc="account.payment_token_id.short_name"/> The error occured while rendering the template sale_subscription.subscription and evalua
Original PR description
Before this commit, payment test would create token without a name. When you tried to pay your subscription on the portal with these, the following error would occurs: ``` Error to render compiling AST AttributeError: 'bool' object has no attribute 'replace' Template: sale_subscription.subscription Path: /t/t[2]/div/t/t[2]/ul/li[1]/div[3]/t Node: <t t-esc="account.payment_token_id.short_name"/> The error occured while rendering the template sale_subscription.subscription and evaluating the following expression: <t t-esc="account.payment_token_id.short_name"/> ``` This commit add a distinct name for these token to avoid errors and confusion. Taskid: 2367508 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60510
Note that in 14.0 the same fix was already applied with [1]. This commit only clarifies the line's related comment and use the right zindex variable (even though the value is the same). [1]: https://github.com/odoo/odoo/commit/0f2cab4aebcc33ca9e278c9395fed2cc8934ed38 X-original-commit: 702f2b93cec19fab75eca25a53aa16cf419b289e Forward-Port-Of: odoo/odoo#61866
Original PR description
Note that in 14.0 the same fix was already applied with [1]. This commit only clarifies the line's related comment and use the right zindex variable (even though the value is the same). [1]: https://github.com/odoo/odoo/commit/0f2cab4aebcc33ca9e278c9395fed2cc8934ed38 X-original-commit: 702f2b93cec19fab75eca25a53aa16cf419b289e Forward-Port-Of: odoo/odoo#61866
Prior to this commit: A race condition could occur when dropping the dynamic product snippet creating a traceback "Cannot read property 'limit' of undefined". After this commit: Potential race condition has been removed from the code. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61872
Original PR description
Prior to this commit:
A race condition could occur when dropping the dynamic product snippet
creating a traceback "Cannot read property 'limit' of undefined".
After this commit:
Potential race condition has been removed from the code.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#61872Currenttly, activity not show from kanban view and not able to scroll the view from bottom scrollbar. So in this commit, activity box will be display in proper manner. Links PR:#60529 TaskID:2336146 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60529
Original PR description
Currenttly, activity not show from kanban view and not able to scroll the view from bottom scrollbar. So in this commit, activity box will be display in proper manner. Links PR:#60529 TaskID:2336146 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60529
before this commit, In the user setting, hovering on the live chat input will focus on the signature div it happens because of the signature div svg height. this commit fixes the issue by adding the css property in the svg element of signature widget due to that svg element contains the proper width and height. TaskID: 2361880 Forward-Port-Of: odoo/odoo#60099
Original PR description
before this commit, In the user setting, hovering on the live chat input will focus on the signature div it happens because of the signature div svg height. this commit fixes the issue by adding the css property in the svg element of signature widget due to that svg element contains the proper width and height. TaskID: 2361880 Forward-Port-Of: odoo/odoo#60099
**PURPOSE** https://tinyurl.com/y4lt79t5 **LINKS** TaskID: 2369225 Closes: https://github.com/odoo/odoo/pull/61649 Forward-Port-Of: odoo/odoo#61649
Original PR description
**PURPOSE** https://tinyurl.com/y4lt79t5 **LINKS** TaskID: 2369225 Closes: https://github.com/odoo/odoo/pull/61649 Forward-Port-Of: odoo/odoo#61649
Currently, When previewing a document, the toolbar (zoom in/out,rotate..) has disappeared. So, in this commit edited a CSS property. TaskId: 2349808 Forward-Port-Of: odoo/enterprise#14465
Original PR description
Currently, When previewing a document, the toolbar (zoom in/out,rotate..) has disappeared. So, in this commit edited a CSS property. TaskId: 2349808 Forward-Port-Of: odoo/enterprise#14465
The state was missing from the address displayed un the pop up markers on the map view. Task: 2348328 Forward-Port-Of: odoo/enterprise#13811
Original PR description
The state was missing from the address displayed un the pop up markers on the map view. Task: 2348328 Forward-Port-Of: odoo/enterprise#13811
Before this commit, once you open a droplet events handler, and when you go to another page without validating or delete it, it appears on another page and the problem came from commit: https://github.com/odoo/enterprise/commit/650ff7b218604ecdee7059bd15eb161231db5b15 After this commit, the droplet events handler will be closed when clicking outside of the sign template. task - 2336246 Forward-Port-Of: odoo/enterprise#13884
Original PR description
Before this commit, once you open a droplet events handler, and when you go to another page without validating or delete it, it appears on another page and the problem came from commit: https://github.com/odoo/enterprise/commit/650ff7b218604ecdee7059bd15eb161231db5b15 After this commit, the droplet events handler will be closed when clicking outside of the sign template. task - 2336246 Forward-Port-Of: odoo/enterprise#13884
Before this commit, payment test would create token without a name. When you tried to pay your subscription on the portal with these, the following error would occurs: ``` Error to render compiling AST AttributeError: 'bool' object has no attribute 'replace' Template: sale_subscription.subscription Path: /t/t[2]/div/t/t[2]/ul/li[1]/div[3]/t Node: <t t-esc="account.payment_token_id.short_name"/> The error occured while rendering the template sale_subscription.subscription and evalua
Original PR description
Before this commit, payment test would create token without a name. When you tried to pay your subscription on the portal with these, the following error would occurs: ``` Error to render compiling AST AttributeError: 'bool' object has no attribute 'replace' Template: sale_subscription.subscription Path: /t/t[2]/div/t/t[2]/ul/li[1]/div[3]/t Node: <t t-esc="account.payment_token_id.short_name"/> The error occured while rendering the template sale_subscription.subscription and evaluating the following expression: <t t-esc="account.payment_token_id.short_name"/> ``` Taskid: 2367508 Forward-Port-Of: odoo/enterprise#14329
…ry lable before this commit, while dragging the document from the central document page onto one of the workspace category labels it throws trackback in Firefox. it happens because the Firefox fire a dragleave event while dragging the document over the workspace category label. after this commit, dragging the document to the workspace category label it doesn't throw any trackback in Firefox. task - 2349799 Forward-Port-Of: odoo/enterprise#13985
Original PR description
…ry lable before this commit, while dragging the document from the central document page onto one of the workspace category labels it throws trackback in Firefox. it happens because the Firefox fire a dragleave event while dragging the document over the workspace category label. after this commit, dragging the document to the workspace category label it doesn't throw any trackback in Firefox. task - 2349799 Forward-Port-Of: odoo/enterprise#13985
…ries Prior to this commit: As the generation of work entries is based on the date_generated_from and date_generated_to fields of the contract, it was not possible to regenerate work entries twice for the same period of time. This can be a problem if the work entries of an employee gets messed up. After this commit: It will be possible to use a wizard in order to regenerate work entries for an employee. The wizard is accessible from the work entries gantt view and
Original PR description
…ries
Prior to this commit:
As the generation of work entries is based on the date_generated_from and date_generated_to fields
of the contract, it was not possible to regenerate work entries twice for the same period of time.
This can be a problem if the work entries of an employee gets messed up.
After this commit:
It will be possible to use a wizard in order to regenerate work entries for an employee.
The wizard is accessible from the work entries gantt view and is is currently limited to
non 'validated' work entries. The existing work entries are archived and new ones are generated.
task-2372175
Forward-Port-Of: odoo/enterprise#14765
Forward-Port-Of: odoo/enterprise#14575Quick Fix an issue where the manager could edit a published employee feedback. Task ID: 2348513 Forward-Port-Of: odoo/enterprise#13678
Original PR description
Quick Fix an issue where the manager could edit a published employee feedback. Task ID: 2348513 Forward-Port-Of: odoo/enterprise#13678
To avoid users timesheet on a day they are not supposed to work. Choice is to set the tip on the first day after a day they're not supposed to work TaskID: 2352672 Forward-Port-Of: odoo/enterprise#14303
Original PR description
To avoid users timesheet on a day they are not supposed to work. Choice is to set the tip on the first day after a day they're not supposed to work TaskID: 2352672 Forward-Port-Of: odoo/enterprise#14303
Current behavior before PR: Traceback, when adding timesheet after an invoice, is generated based on the timesheet for that task. Desired behavior after PR is merged: No traceback, when adding timesheet after an invoice, is generated based on the timesheet for that task. LINKS PR https://github.com/odoo/enterprise/pull/14284 Task-2357182 Forward-Port-Of: odoo/enterprise#14284
Original PR description
Current behavior before PR: Traceback, when adding timesheet after an invoice, is generated based on the timesheet for that task. Desired behavior after PR is merged: No traceback, when adding timesheet after an invoice, is generated based on the timesheet for that task. LINKS PR https://github.com/odoo/enterprise/pull/14284 Task-2357182 Forward-Port-Of: odoo/enterprise#14284
- Activate 'Discount on SO line' on user - Activate Variants and the pricelist with advanced feature - Create a product P with price 0 and available in Subscription - Create 2 variants for P, V1 and V2 - On a pricelist PL, set the `discount_policy` to `without_discount` - Set a fixed price for V1 and V2 on PL - Create a new subscription with PL - Add V1 The price remains zero. It happens because `lst_price` is zero in this case. The root cause is the commit 991e5088c6c26b6a: it i
Original PR description
- Activate 'Discount on SO line' on user - Activate Variants and the pricelist with advanced feature - Create a product P with price 0 and available in Subscription - Create 2 variants for P, V1 and…
- Activate 'Discount on SO line' on user - Activate Variants and the pricelist with advanced feature - Create a product P with price 0 and available in Subscription - Create 2 variants for P, V1 and V2 - On a pricelist PL, set the `discount_policy` to `without_discount` - Set a fixed price for V1 and V2 on PL - Create a new subscription with PL - Add V1 The price remains zero. It happens because `lst_price` is zero in this case. The root cause is the commit 991e5088c6c26b6a: it introduces the support for the `without_discount` behavior on the Subscriptions, but this support is only partial. Indeed, a complete support of the feature would require to duplicate the logic from the SO: https://github.com/odoo/odoo/blob/d310f1c59c7fd28903d91b0f2fc46044d0cea6a0/addons/sale/models/sale.py#L1636-L1668 https://github.com/odoo/odoo/blob/d310f1c59c7fd28903d91b0f2fc46044d0cea6a0/addons/sale/models/sale.py#L1585-L1628 https://github.com/odoo/odoo/blob/d310f1c59c7fd28903d91b0f2fc46044d0cea6a0/addons/sale/models/sale.py#L1453-L1484 (this might not be exhaustive) We should simply not support this on Subscriptions. opw-2367845 Forward-Port-Of: odoo/enterprise#14784 Forward-Port-Of: odoo/enterprise#14728
Prior to this commit, the `renewal_allowed` field on `payment.transaction` was never re-computed if the state was updated. This made emails not being sent when renewing a subscription although the transaction had been successfully processed. This commits fixes the computation by making `_compute_renewal_allowed` depend on `state`. Forward-Port-Of: odoo/enterprise#14712
Original PR description
Prior to this commit, the `renewal_allowed` field on `payment.transaction` was never re-computed if the state was updated. This made emails not being sent when renewing a subscription although the transaction had been successfully processed. This commits fixes the computation by making `_compute_renewal_allowed` depend on `state`. Forward-Port-Of: odoo/enterprise#14712
In some cases, users may want to do that to consolidate the reports of multiple sub-companies. To avoid additional complexity and stick to our stability policy, we add a config parameter to enable this behavior. No currency conversion is supported here, as we expected the aggregated companies to share the same main currency. OPW 2372358 Forward-Port-Of: odoo/enterprise#14771 Forward-Port-Of: odoo/enterprise#14744
Original PR description
In some cases, users may want to do that to consolidate the reports of multiple sub-companies. To avoid additional complexity and stick to our stability policy, we add a config parameter to enable this behavior. No currency conversion is supported here, as we expected the aggregated companies to share the same main currency. OPW 2372358 Forward-Port-Of: odoo/enterprise#14771 Forward-Port-Of: odoo/enterprise#14744
To allow excluding some journals, like IFRS, by default. Forward-Port-Of: odoo/enterprise#14701 Forward-Port-Of: odoo/enterprise#14694
Original PR description
To allow excluding some journals, like IFRS, by default. Forward-Port-Of: odoo/enterprise#14701 Forward-Port-Of: odoo/enterprise#14694
Before this commit, the progress bar upload test could fail because the rendering of the document inspector may not have occurred when attempting to click on one of its button. This commit fixes this issue by awaiting for the rendering of the inspector. Forward-Port-Of: odoo/enterprise#14776
Original PR description
Before this commit, the progress bar upload test could fail because the rendering of the document inspector may not have occurred when attempting to click on one of its button. This commit fixes this issue by awaiting for the rendering of the inspector. Forward-Port-Of: odoo/enterprise#14776
In studio mode, on list view, enable "Show Invisible Elements" raises an error. To reproduce the issue: 1. Go, for instance, in the Invoicing module 2. Toggle Studio 3. On the left panel: View > Click on "Show Invisible Elements" => It raises an error This fix ignores the column "header", which is not concerned by the visibility option. OPW-2379454 Forward-Port-Of: odoo/enterprise#14722
Original PR description
In studio mode, on list view, enable "Show Invisible Elements" raises an error. To reproduce the issue: 1. Go, for instance, in the Invoicing module 2. Toggle Studio 3. On the left panel: View > Click on "Show Invisible Elements" => It raises an error This fix ignores the column "header", which is not concerned by the visibility option. OPW-2379454 Forward-Port-Of: odoo/enterprise#14722
This join clause in the ICP report is an artifact from an older version. In case an invoice line was linked to multiple taxes, it duplicated the account.move.line returned by SQL for each of them, causing the same line to be taken several times into account. OPW 2373577 Forward-Port-Of: odoo/enterprise#14767
Original PR description
This join clause in the ICP report is an artifact from an older version. In case an invoice line was linked to multiple taxes, it duplicated the account.move.line returned by SQL for each of them, causing the same line to be taken several times into account. OPW 2373577 Forward-Port-Of: odoo/enterprise#14767
Steps to reproduce the bug: 1.Create an automated action with the following: - Model: Task (project.task) - Active: True - Trigger: On Update - Action To Do: Create Next Activity 2. Open or create a task in Project module 3. Edit 4. Change or set customer (partner_id) Bug: An error message was raised. opw:2376492 Forward-Port-Of: odoo/enterprise#14764
Original PR description
Steps to reproduce the bug:
1.Create an automated action with the following:
- Model: Task (project.task)
- Active: True
- Trigger: On Update
- Action To Do: Create Next Activity
2. Open or create a task in Project module
3. Edit
4. Change or set customer (partner_id)
Bug:
An error message was raised.
opw:2376492
Forward-Port-Of: odoo/enterprise#14764STEPS: * install and go to Barcode * click inventory adjustment * scan a lot that has non-zero quantity on hand BEFORE: it shows "Product 1" AFTER: it shows "Product 1 / 123" WHY: if you scan a product, then theoretical_qty is displayed; if scan lot, edit manually, then theoretical_qty is displayed too. So, not having theoretical_qty after scanning a lot is a bug --- opw-2360983 Forward-Port-Of: odoo/enterprise#14451
Original PR description
STEPS: * install and go to Barcode * click inventory adjustment * scan a lot that has non-zero quantity on hand BEFORE: it shows "Product 1" AFTER: it shows "Product 1 / 123" WHY: if you scan a product, then theoretical_qty is displayed; if scan lot, edit manually, then theoretical_qty is displayed too. So, not having theoretical_qty after scanning a lot is a bug --- opw-2360983 Forward-Port-Of: odoo/enterprise#14451
Before this commit, just the message error was return, and not the payment's cfdi document that generates the error. Not having the document, complicates the understanding of the error and how to fix it. Now, the generated payment's cfdi document as well as the error are return. Related to 06a82a94fc4310dcb9b0570717338891cfaaf33b Forward-Port-Of: odoo/enterprise#14661
Original PR description
Before this commit, just the message error was return, and not the payment's cfdi document that generates the error. Not having the document, complicates the understanding of the error and how to fix it. Now, the generated payment's cfdi document as well as the error are return. Related to 06a82a94fc4310dcb9b0570717338891cfaaf33b Forward-Port-Of: odoo/enterprise#14661
Steps to reproduce the bug: - Let's consider a company contact C with two children CH1 and CH2 - Create a subscription for CH1 and a subscription for CH2 - Archive CH1 and CH2 Bug: The count of subscriptions in C was displaying 0 instead of 2 Same issue for the helpdesk tickets opw:2360155 Forward-Port-Of: odoo/enterprise#14558
Original PR description
Steps to reproduce the bug: - Let's consider a company contact C with two children CH1 and CH2 - Create a subscription for CH1 and a subscription for CH2 - Archive CH1 and CH2 Bug: The count of subscriptions in C was displaying 0 instead of 2 Same issue for the helpdesk tickets opw:2360155 Forward-Port-Of: odoo/enterprise#14558
Courtesy of Transifex's translators for reporting bad/unclear sentences. Enterprise part of odoo/odoo#61785 Forward-Port-Of: odoo/enterprise#14751
Original PR description
Courtesy of Transifex's translators for reporting bad/unclear sentences. Enterprise part of odoo/odoo#61785 Forward-Port-Of: odoo/enterprise#14751