Thursday, October 6, 2022
135 changes · master
Enhancements to existing features
This update refreshes Odoo's spreadsheet engine, adding clickable dashboard cells and several familiar spreadsheet formulas such as XLOOKUP, MID, PROPER, CLEAN, IFNA, and ISBLANK. Users should see more capable dashboards and better spreadsheet performance, especially for lookup-heavy sheets.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/a6675aa4 [IMP] clickable cell: give env as condition argument https://github.com/odoo/o-spreadsheet/commit/b8420475…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/a6675aa4 [IMP] clickable cell: give env as condition argument https://github.com/odoo/o-spreadsheet/commit/b8420475 [IMP] dashboard: clickable cells https://github.com/odoo/o-spreadsheet/commit/7b1c16b0 [REF] components: use dedicated component for dashboard mode https://github.com/odoo/o-spreadsheet/commit/b3f48d65 [REF] grid: move focusable element to grid https://github.com/odoo/o-spreadsheet/commit/cd083d9b [REF] grid: resize sheet view independently from grid https://github.com/odoo/o-spreadsheet/commit/ed4948b8 [REF] tests: globally mock grid clientX and clientY https://github.com/odoo/o-spreadsheet/commit/011aa0d4 [IMP] spreadsheet: export positionToZone helper https://github.com/odoo/o-spreadsheet/commit/b24e6483 [IMP] formula: ignore space when caching compiled formula https://github.com/odoo/o-spreadsheet/commit/65a67b51 [IMP] package.json: upgrade Typescript https://github.com/odoo/o-spreadsheet/commit/af4f2f58 [IMP] package.json: upgrade prettier https://github.com/odoo/o-spreadsheet/commit/4c15328d [IMP] functions: improve performance of lookup functions https://github.com/odoo/o-spreadsheet/commit/baafa638 [IMP] functions: add XLOOKUP function https://github.com/odoo/o-spreadsheet/commit/3d5c662e [IMP] functions: add MID function https://github.com/odoo/o-spreadsheet/commit/26f24529 [IMP] functions: add PROPER function https://github.com/odoo/o-spreadsheet/commit/07b4201f [IMP] functions: add CLEAN function https://github.com/odoo/o-spreadsheet/commit/adee58ff [IMP] functions: add IFNA function https://github.com/odoo/o-spreadsheet/commit/089f3b8d [IMP] functions: add ISBLANK function https://github.com/odoo/o-spreadsheet/commit/b638a3d5 [IMP] grid: use correct event attribute https://github.com/odoo/enterprise/pull/32358
The Mail app's online status icon logic was reorganized so the display rules live in the underlying data model rather than the screen component. This makes the feature easier to maintain and reduces the risk of inconsistent behavior in places where status icons appear.
Original PR description
+ Turn props on component into fields on PersonImStatusIconView model + Move handler from component methods to model record methods Task-3004188.
The mass mailing composer now hides the mailing name option when the selected records cannot actually create a mailing. This prevents users from thinking a mailing campaign will be created when the system would only send a regular mass email.
Original PR description
## Issue Currently when creating a composer in mass mode the composer always shows the 'mass mailing name' option even when a mailing cannot be created. This silently creates a regular mass mail. ## Fix This hides that option when selecting records of models that do not inherit from thread. So that users do not falsly believe a mailing will be created. task #2990447 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The mail activity interface was updated to use a newer internal component structure. This helps keep the messaging area easier to maintain and supports future improvements without changing day-to-day user workflows.
Original PR description
part of task-2783065 Enterprise PR: https://github.com/odoo/enterprise/pull/32360
This update refreshes Odoo's spreadsheet engine with new formula options, faster lookup calculations, and better dashboard interactions. Business users benefit from spreadsheets that are more compatible with familiar spreadsheet tools and dashboards where relevant cells can be clicked to open related data.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/808bd19f [IMP] figure: select figure on insertion https://github.com/odoo/o-spreadsheet/commit/a6675aa4 [IMP]…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/808bd19f [IMP] figure: select figure on insertion https://github.com/odoo/o-spreadsheet/commit/a6675aa4 [IMP] clickable cell: give env as condition argument https://github.com/odoo/o-spreadsheet/commit/b8420475 [IMP] dashboard: clickable cells https://github.com/odoo/o-spreadsheet/commit/7b1c16b0 [REF] components: use dedicated component for dashboard mode https://github.com/odoo/o-spreadsheet/commit/b3f48d65 [REF] grid: move focusable element to grid https://github.com/odoo/o-spreadsheet/commit/cd083d9b [REF] grid: resize sheet view independently from grid https://github.com/odoo/o-spreadsheet/commit/ed4948b8 [REF] tests: globally mock grid clientX and clientY https://github.com/odoo/o-spreadsheet/commit/011aa0d4 [IMP] spreadsheet: export positionToZone helper https://github.com/odoo/o-spreadsheet/commit/b24e6483 [IMP] formula: ignore space when caching compiled formula https://github.com/odoo/o-spreadsheet/commit/65a67b51 [IMP] package.json: upgrade Typescript https://github.com/odoo/o-spreadsheet/commit/af4f2f58 [IMP] package.json: upgrade prettier https://github.com/odoo/o-spreadsheet/commit/4c15328d [IMP] functions: improve performance of lookup functions https://github.com/odoo/o-spreadsheet/commit/baafa638 [IMP] functions: add XLOOKUP function https://github.com/odoo/o-spreadsheet/commit/3d5c662e [IMP] functions: add MID function https://github.com/odoo/o-spreadsheet/commit/26f24529 [IMP] functions: add PROPER function https://github.com/odoo/o-spreadsheet/commit/07b4201f [IMP] functions: add CLEAN function https://github.com/odoo/o-spreadsheet/commit/adee58ff [IMP] functions: add IFNA function https://github.com/odoo/o-spreadsheet/commit/089f3b8d [IMP] functions: add ISBLANK function https://github.com/odoo/o-spreadsheet/commit/b638a3d5 [IMP] grid: use correct event attribute
The mail activity completion popover was updated as part of an internal modernization effort. This helps keep the interface maintainable and consistent without changing the user-facing workflow.
Original PR description
part of task-2783065
The messaging discussion area has been updated to use a newer internal component structure. This helps keep the mail app easier to maintain and prepares it for future improvements, with no expected change to day-to-day user behavior.
Original PR description
part of task-2783065
The Mail app’s attachment preview component was updated to use the newer interface used across Odoo. This keeps attachment viewing aligned with the current platform behavior and removes obsolete event handling that was no longer used.
Original PR description
Since https://github.com/odoo/enterprise/commit/afcdd1878a2eaf4cbca85d1169dea31a108c8c43#diff-f064a21c91b8daa5d78c44e88e2c02345ff0a7230403dd3600a65d3a6b0653d3L18 there is no listener for preview_attachment_validation. Part of task-2783065
This update improves internal error messages when configuring mail-related data fields. It helps developers identify incorrect field definitions faster, reducing troubleshooting time and improving reliability for future mail features.
The test mock server used by messaging and related apps has been reorganized into separate pieces by business object and web controller. This makes the test infrastructure easier for developers to navigate and maintain, reducing the effort and risk when updating these areas in the future.
Original PR description
The mail mock server is getting bigger and bigger. As a consequence, navigating/keeping it up to date is quiet inconvenient. This commit solves this issue by splitting it by model/controller. enterprise: https://github.com/odoo/enterprise/pull/32314
The call options menu in Odoo's mail and Discuss area was updated to use the newer interface framework. This helps keep the calling experience easier to maintain and supports future improvements without changing day-to-day behavior for users.
Original PR description
part of task-2783065
The test mock server setup was reorganized into smaller parts by business area and function. This makes the internal test code easier for developers to navigate and update, reducing maintenance effort without changing customer-facing behavior.
Original PR description
*: approvals, documents, voip, website_helpdesk_livechat. The mail mock server is getting bigger and bigger. As a consequence, navigating/keeping it up to date is quiet inconvenient. This commit solves this issue by splitting it by model/controller. community: https://github.com/odoo/odoo/pull/98374
This update removes an unnecessary internal check in the VoIP activity view. It streamlines the code without changing the user experience, helping keep the VoIP module easier to maintain.
Original PR description
part of task-2783065
Resolved issues and error corrections
The confirmation window shown when removing a link preview now displays at the correct size instead of appearing vertically stretched. This small visual fix improves the user experience in messaging without changing functionality.
Original PR description
Prior to this commit, the size of the modal for removing a link preview was stretched vertically. This commit fixes this issue. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
This update reorganizes how conversation icons are handled across Discuss, Live Chat, and Time Off messaging areas. The change is mainly internal, making the interface code easier to maintain while preserving the existing user experience.
Original PR description
Task-3002515. \* = hr_holidays, im_livechat
Miscellaneous changes
The financial account must be editable until a journal items is set, which wasn't the case before this PR. I also switched the two fields so that's more logical for the user. task-id: 3006879 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102124
Original PR description
The financial account must be editable until a journal items is set, which wasn't the case before this PR. I also switched the two fields so that's more logical for the user. task-id: 3006879 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102124
Fixed an issue that could cause an error when clicking a user avatar in the Gantt view after installing Field Service. This improves reliability for users navigating schedules and employee assignments.
Original PR description
Steps to reproduce: -Install industry_fsm -Go to Gantt View -Click on the user avatar task-2960247
Allocated time now reflects the full scheduled shift, even when the employee or resource was created after the shift start time. This prevents confusing undercounts during onboarding and also uses the resource calendar when no contract exists.
Original PR description
Steps : \- On a new DB (no demo data). Say created at 15:00. \- Go to planning. \- Add a shift for today. \- Set the dates from 08:00 to 17:00. Issue : The 'Allocated Time' = 02:00. Cause : We used…
Steps : \- On a new DB (no demo data). Say created at 15:00. \- Go to planning. \- Add a shift for today. \- Set the dates from 08:00 to 17:00. Issue : The 'Allocated Time' = 02:00. Cause : We used to count from the resource creation min to the departure max. So, in this case, not from 08:00, but from 15:00. While this might seem logical, it confuses users in onboarding. Fix : Calculate the whole time, regardless of the resource lifespan. Notes : \- Similar issues solved with this commit : > Once the shift validated, the avatar progress bar uses the same allocated time. > Same in Project Task gantt view. \- When contract is installed, if the resource does not have a contract, the Allocated Time = 0. Now, it is calculated from the resource calendar. task-2983993 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 update keeps spreadsheet-related document features working correctly after a recent spreadsheet engine change. It helps maintain reliable spreadsheet actions, pivot behavior, and chart-related tests without introducing new business functionality.
Original PR description
…eadsheet update
Updates internal tests for Project HR scheduling so they match the latest way worked hours are calculated. This helps keep quality checks reliable and reduces the risk of false test failures after related platform changes.
Original PR description
The community commit modifies the way worked hours are calculated. This commit adapts some tests to it. task-2983993 related: https://github.com/odoo/odoo/pull/100295
This update adapts spreadsheet-related features to a recent underlying spreadsheet change. It helps keep document spreadsheets, pivot displays, charts, and spreadsheet editing behavior working reliably after the update.
Original PR description
…eadsheet update https://github.com/odoo/odoo/pull/102262
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#101552
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#101552
Description of the issue/feature this PR addresses: Requesting CLA approval Current behavior before PR: Requesting CLA Approval Desired behavior after PR is merged: Approved CLA for contribution --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101180
Original PR description
Description of the issue/feature this PR addresses: Requesting CLA approval Current behavior before PR: Requesting CLA Approval Desired behavior after PR is merged: Approved CLA for contribution --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101180
With version of urllib3 in ubuntu 22.04 (1.26.5) and with version of firebase_admin between 2.17.0 and 4.5.2 a gives the following warning: In firebase_admin/_http_client.py:30: DeprecationWarning: Using 'method_whitelist' with Retry is deprecated and will be removed in v2.0. Use 'allowed_methods' instead It has been fixed in later version https://github.com/firebase/firebase-admin-python/pull/532 since v4.5.2 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.co
Original PR description
With version of urllib3 in ubuntu 22.04 (1.26.5) and with version of firebase_admin between 2.17.0 and 4.5.2 a gives the following warning: In firebase_admin/_http_client.py:30: DeprecationWarning: Using 'method_whitelist' with Retry is deprecated and will be removed in v2.0. Use 'allowed_methods' instead It has been fixed in later version https://github.com/firebase/firebase-admin-python/pull/532 since v4.5.2 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101444
Impacted versions: 16.0 alpha (maybe previous version). (12.0 is working correctly.) ### Steps to reproduce: - with Odoo CE commit https://github.com/odoo/odoo/commit/6c6d7ce06ed4b18162db893a0afb65e0479ee11f (October, 4 2022) - install a module (point of sale for exemple) - try to uninstall it. ### current behaviour - "The documents to delete" field are bad displayed (``model_ids``) . (12.0 is working correctly.) ### Steps to reproduce: - with Odoo CE commit https://github.com/odoo/odoo/commit/6c6d7ce06ed4b18162db893a0afb65e0479ee11f (October, 4 2022) - install a module (point of sale for exemple) - try to uninstall it. ### current behaviour - "The documents to delete" field are bad displayed (``model_ids``)  ### Desired behavior after PR is merged: - "The document to delete" field is well displayed.  CC : @bouvyd --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102168
When converting the list view to owl, the support for view widgets was overlooked as this feature is not used very extensively and was not tested. This commit adds support for them and adds a test for it. Forward-Port-Of: odoo/odoo#102052
Original PR description
When converting the list view to owl, the support for view widgets was overlooked as this feature is not used very extensively and was not tested. This commit adds support for them and adds a test for it. Forward-Port-Of: odoo/odoo#102052
When duplicating a location, it is currently confusing to know if we're now updating the duplicate or the original. Adding a (copy) to the `name` after a duplicate will make it easier to know which location we are currently updating. Part of task-2985735 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101777
Original PR description
When duplicating a location, it is currently confusing to know if we're now updating the duplicate or the original. Adding a (copy) to the `name` after a duplicate will make it easier to know which location we are currently updating. Part of task-2985735 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101777
**Description of the issue/feature this PR addresses**: If the components of the manufacturing order are in done or cancel state you should NOT define the status of the manufacturing order as done. It should only be set as done if components and finished moves are done/cancel. **Impacted versions**: - 14.0 - 15.0 - master Ping @pedrobaeza cc @Tecnativa TT38551 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odo
Original PR description
**Description of the issue/feature this PR addresses**: If the components of the manufacturing order are in done or cancel state you should NOT define the status of the manufacturing order as done. It should only be set as done if components and finished moves are done/cancel. **Impacted versions**: - 14.0 - 15.0 - master Ping @pedrobaeza cc @Tecnativa TT38551 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101776 Forward-Port-Of: odoo/odoo#98105
This commit fix the following issues : - When an event don't have a color provided, the first color was used. The issue with this, is that that color can be used with another filter. Now, a neutral color is used to avoid confusion. - The filter that don't provided a color, will also use a neutral color, to keep harmonization with the color of the event. - The color of the current user, was missing on the user filters. - The color attribute set on the view was taken instead of
Original PR description
This commit fix the following issues :
- When an event don't have a color provided, the first color was used.
The issue with this, is that that color can be used with another
filter. Now, a neutral color is used to avoid confusion.
- The filter that don't provided a color, will also use a neutral color,
to keep harmonization with the color of the event.
- The color of the current user, was missing on the user filters.
- The color attribute set on the view was taken instead of the color
attribute set on a field when the field is set as filter, which
leads to a traceback.
Co-authored-by: Bruno Boi <boi@odoo.com>
Co-authored-by: Jorge Pinna Puissant <jpp@odoo.com>
Forward-Port-Of: odoo/odoo#101951With the sequence gone, the lines are now ordered incorrectly in the simplified LU tax report. Reordering the lines correctly. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101778
Original PR description
With the sequence gone, the lines are now ordered incorrectly in the simplified LU tax report. Reordering the lines correctly. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101778
Always generate a Factur-X xml and embed it when a PDF is created. But no edi.document is created, no warnings will be displayed on the invoice, and the PDF is not PDF/A-3. The only purpose here is the Odoo interoperability. Rename the 'Factur-X' option to 'Factur-X PDF/A-3' and make it only visible for FR and DE companies. This 'Factur-X PDF/A-3' option will trigger the regular account.edi flow: create an edi.document and show warnings on the move if errors are detected. When a PDF is pri
Original PR description
Always generate a Factur-X xml and embed it when a PDF is created. But no edi.document is created, no warnings will be displayed on the invoice, and the PDF is not PDF/A-3. The only purpose here is the Odoo interoperability. Rename the 'Factur-X' option to 'Factur-X PDF/A-3' and make it only visible for FR and DE companies. This 'Factur-X PDF/A-3' option will trigger the regular account.edi flow: create an edi.document and show warnings on the move if errors are detected. When a PDF is printed, embed the Factur-X xml and make the PDF a PDF/A-3. Thus, it can be used on Chorus Pro. task-2957808 https://github.com/odoo/enterprise/pull/31851 https://github.com/odoo/upgrade/pull/3940 Forward-Port-Of: odoo/odoo#99699
Allow users to use stacked line charts. The chart.js configuration is mimicking the one inside Odoo community. task 2888350 enterprise PR: https://github.com/odoo/enterprise/pull/31466 Forward-Port-Of: odoo/odoo#100492
Original PR description
Allow users to use stacked line charts. The chart.js configuration is mimicking the one inside Odoo community. task 2888350 enterprise PR: https://github.com/odoo/enterprise/pull/31466 Forward-Port-Of: odoo/odoo#100492
The accounts setting allows to have default taxes on accounts, but they are not used when changing the account on an account_move_line. Forward-Port-Of: odoo/odoo#101236
Original PR description
The accounts setting allows to have default taxes on accounts, but they are not used when changing the account on an account_move_line. Forward-Port-Of: odoo/odoo#101236
Following https://github.com/odoo/odoo/pull/100606, uniform font-weights across versions in order to get "predictable" visual results. Enterprise: - https://github.com/odoo/enterprise/pull/32272 task-3006942 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102132
Original PR description
Following https://github.com/odoo/odoo/pull/100606, uniform font-weights across versions in order to get "predictable" visual results. Enterprise: - https://github.com/odoo/enterprise/pull/32272 task-3006942 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102132
When [1] introduced the website edition using an iframe, it did not correctly adapt url attachments redirections. Following this flow, in the Website Builder: - From the Media Dialog, click on the "add document" top right button, - Paste a google doc url and save, - Click on the inserted document icon, => The google doc is opened inside the iframe (it leads to tracebacks). This commit fixes the way these documents are opened from the Website Preview iframe: '/web/content/...' links are alw
Original PR description
When [1] introduced the website edition using an iframe, it did not correctly adapt url attachments redirections. Following this flow, in the Website Builder: - From the Media Dialog, click on the "add document" top right button, - Paste a google doc url and save, - Click on the inserted document icon, => The google doc is opened inside the iframe (it leads to tracebacks). This commit fixes the way these documents are opened from the Website Preview iframe: '/web/content/...' links are always opened in the top window, as they can be external redirections. [1]: https://github.com/odoo/odoo/commit/31cc10b91dc7762e23b4bde9b945be0c4ce3fe3b task-2172311 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102225
Since the usage of the `CSS Grid` some view are broken. The new form view system is less tolerant to missing colspan. This commit, change the colspan when needed (e.g. no label) and in some case extract the label outside the `DIV` to use `GRID` layout. Steps to reproduce: * Go to survey * Select a survey * Select the Option notebook, fields are not aligned => BUG * OR * Click on Add a question * list view in Answers notebook are not aligned => BUG --- I confirm I have si
Original PR description
Since the usage of the `CSS Grid` some view are broken. The new form view system is less tolerant to missing colspan. This commit, change the colspan when needed (e.g. no label) and in some case extract the label outside the `DIV` to use `GRID` layout.
Steps to reproduce:
* Go to survey
* Select a survey
* Select the Option notebook, fields are not aligned => BUG
* OR
* Click on Add a question
* list view in Answers notebook are not aligned => BUG
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#102234The `__count` pivot measure was removed by mistake in the last dashboard update https://github.com/odoo/odoo/commit/4d6fb4549d4069fc52af0ba500f91ba271e9c62b --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102263
Original PR description
The `__count` pivot measure was removed by mistake in the last dashboard update https://github.com/odoo/odoo/commit/4d6fb4549d4069fc52af0ba500f91ba271e9c62b --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102263
It was missing the bootstrap form-check class Forward-Port-Of: odoo/odoo#102272
Original PR description
It was missing the bootstrap form-check class Forward-Port-Of: odoo/odoo#102272
Recently, the chatter was migrated to owl. When doing this, it lost its flex-grow property, whereas the attachment preview has kept it, which causes layout shift when moving from a record without an attachment preview to another with one and vice versa. This commit fixes that. Forward-Port-Of: odoo/odoo#102287
Original PR description
Recently, the chatter was migrated to owl. When doing this, it lost its flex-grow property, whereas the attachment preview has kept it, which causes layout shift when moving from a record without an attachment preview to another with one and vice versa. This commit fixes that. Forward-Port-Of: odoo/odoo#102287
Forward-Port-Of: odoo/odoo#102045
Original PR description
Forward-Port-Of: odoo/odoo#102045
Task-2998514 Enterprise PR: https://github.com/odoo/enterprise/pull/32273 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101886
Original PR description
Task-2998514 Enterprise PR: https://github.com/odoo/enterprise/pull/32273 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101886
Currently, when using the quick invoice encoding feature, we do not create the invoice line if no partner is set. This PR fixes by falling back on the default values of the account and the tax. Forward-Port-Of: odoo/odoo#102218
Original PR description
Currently, when using the quick invoice encoding feature, we do not create the invoice line if no partner is set. This PR fixes by falling back on the default values of the account and the tax. Forward-Port-Of: odoo/odoo#102218
The settings has its own formcompiler who is (apparently) there to remove some classes Revision https://github.com/odoo-dev/odoo/commit/9fa770f55579e6501d71971bc4afb2b92fbdb79a introduced padding on 'o_form_nosheet' containers for grid views compatibility, which should not be applied to Settings either. cc @sdegueldre works fine Forward-Port-Of: odoo/odoo#102411
Original PR description
The settings has its own formcompiler who is (apparently) there to remove some classes Revision https://github.com/odoo-dev/odoo/commit/9fa770f55579e6501d71971bc4afb2b92fbdb79a introduced padding on 'o_form_nosheet' containers for grid views compatibility, which should not be applied to Settings either. cc @sdegueldre works fine Forward-Port-Of: odoo/odoo#102411
Before this commit : on project sharing chatter upload file delete icon should be displayed in left bottom corner After this commit: now on uploaded file the delete icon display in top right corner of the file and only displayed on hover. task - 2904015 Forward-Port-Of: odoo/odoo#95619
Original PR description
Before this commit : on project sharing chatter upload file delete icon should be displayed in left bottom corner After this commit: now on uploaded file the delete icon display in top right corner of the file and only displayed on hover. task - 2904015 Forward-Port-Of: odoo/odoo#95619
Purpose: restore edit access to body when creating a new template. Likely introduced by 2bb148f9. Task-3002242 Forward-Port-Of: odoo/odoo#101718
Original PR description
Purpose: restore edit access to body when creating a new template. Likely introduced by 2bb148f9. Task-3002242 Forward-Port-Of: odoo/odoo#101718
When loading a registry from route with auth="none" and where module 'website' is set as 'to install', request.env will be None and install will crash as follows: ``` Traceback (most recent call last): ... File "/home/odoo/src/odoo/saas-15.3/odoo/modules/registry.py", line 88, in new odoo.modules.load_modules(registry, force_demo, status, update_module) File "/home/odoo/src/odoo/saas-15.3/odoo/modules/loading.py", line 482, in load_modules processed_modules += load_marked_
Original PR description
When loading a registry from route with auth="none" and where module 'website' is set as 'to install', request.env will be None and install will crash as follows: ``` Traceback (most recent call…
When loading a registry from route with auth="none" and where module 'website' is set as 'to install', request.env will be None and install will crash as follows:
```
Traceback (most recent call last):
...
File "/home/odoo/src/odoo/saas-15.3/odoo/modules/registry.py", line 88, in new
odoo.modules.load_modules(registry, force_demo, status, update_module)
File "/home/odoo/src/odoo/saas-15.3/odoo/modules/loading.py", line 482, in load_modules
processed_modules += load_marked_modules(cr, graph,
File "/home/odoo/src/odoo/saas-15.3/odoo/modules/loading.py", line 371, in load_marked_modules
loaded, processed = load_module_graph(
File "/home/odoo/src/odoo/saas-15.3/odoo/modules/loading.py", line 303, in load_module_graph
module.write({'state': 'installed', 'latest_version': ver})
File "/home/odoo/src/odoo/saas-15.3/addons/website/models/ir_module_module.py", line 78, in write
if request and request.context.get('apply_new_theme'):
File "/usr/lib/python3/dist-packages/werkzeug/local.py", line 348, in __getattr__
return getattr(self._get_current_object(), name)
File "/home/odoo/src/odoo/saas-15.3/odoo/http.py", line 1029, in context
return self.env.context
AttributeError: 'NoneType' object has no attribute 'context'
```
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#102267This commit fixes the wrong account suggestion if no invoice exists for set partner. Steps: - New invoice - Select a partner that has no invoices yet - Create a new line - The default account is quite random Fix: Only use the most frequent account for the set partner if there are existing invoices for that partner. Otherwise we fallback on the default account of the invoice's journal. task-id: 2972993 enterprise: https://github.com/odoo/enterprise/pull/32162 Forward-Port-Of: odo
Original PR description
This commit fixes the wrong account suggestion if no invoice exists for set partner. Steps: - New invoice - Select a partner that has no invoices yet - Create a new line - The default account is quite random Fix: Only use the most frequent account for the set partner if there are existing invoices for that partner. Otherwise we fallback on the default account of the invoice's journal. task-id: 2972993 enterprise: https://github.com/odoo/enterprise/pull/32162 Forward-Port-Of: odoo/odoo#99568
The following PR - odoo/odoo#98914 introduced changes in accounting analytic. The changes were applied to 'hr.expense' but they were not applied to 'hr.expense.split'. Which lead to traceback. task - 2997510 Forward-Port-Of: odoo/odoo#101524
Original PR description
The following PR - odoo/odoo#98914 introduced changes in accounting analytic. The changes were applied to 'hr.expense' but they were not applied to 'hr.expense.split'. Which lead to traceback. task - 2997510 Forward-Port-Of: odoo/odoo#101524
The "Reporting" title was not properly displayed (stuck to the left of the dropdown) and the Timesheets entry was not displayed as a proper dropdown item. task-3001445 Forward-Port-Of: odoo/odoo#101744
Original PR description
The "Reporting" title was not properly displayed (stuck to the left of the dropdown) and the Timesheets entry was not displayed as a proper dropdown item. task-3001445 Forward-Port-Of: odoo/odoo#101744
**Current behavior before PR:** https://www.awesomescreenshot.com/image/33020505?key=89e15993e7b0646b570615b71fac9c90 **Desired behavior after PR is merged:** <img width="1352" alt="Screenshot 2022-10-04 at 16 42 23" src="https://user-images.githubusercontent.com/3245568/193849958-d0769455-241f-4187-bca5-bf8539a5613e.png"> **Change Note** It's not very generic to affect other instances of the char field, but generic enough to take into account other heading elements. --- I
Original PR description
**Current behavior before PR:** https://www.awesomescreenshot.com/image/33020505?key=89e15993e7b0646b570615b71fac9c90 **Desired behavior after PR is merged:** <img width="1352" alt="Screenshot 2022-10-04 at 16 42 23" src="https://user-images.githubusercontent.com/3245568/193849958-d0769455-241f-4187-bca5-bf8539a5613e.png"> **Change Note** It's not very generic to affect other instances of the char field, but generic enough to take into account other heading elements. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102121
The column `location_dest_id` ends up squished to almost nothing and need to be dragged open to be able to read what's in it. This sets the width of this column back to its default size. Part of task-2985735 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102203
Original PR description
The column `location_dest_id` ends up squished to almost nothing and need to be dragged open to be able to read what's in it. This sets the width of this column back to its default size. Part of task-2985735 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102203
Previously, in form views without a sheet (eg in wizards), there would be a scrollbar on the content. This is caused by the fact that outer groups have gutters of size 5 in desktop which creates negative margins on the row of 1.5rem which is 18px with the default size, but the nosheet form view only has 16px of padding on the sides, causing the groups to be 4 pixels too wide. This commit fixes this by adding the correct padding classes on the form view when it doesn't have a sheet. Forward-P
Original PR description
Previously, in form views without a sheet (eg in wizards), there would be a scrollbar on the content. This is caused by the fact that outer groups have gutters of size 5 in desktop which creates negative margins on the row of 1.5rem which is 18px with the default size, but the nosheet form view only has 16px of padding on the sides, causing the groups to be 4 pixels too wide. This commit fixes this by adding the correct padding classes on the form view when it doesn't have a sheet. Forward-Port-Of: odoo/odoo#102300
When computing the edi_formats on a journal, keep the ones that are already checked (if they are compatible with this journal). The bug occurs when migrating a DB: if a new edi_format is created, the `create` will call the `_compute_edi_format_ids` on all journals. Thus, all edi_formats will be reset since nothing keeps track of the already checked edi_formats. This PR fixes this. Forward-Port-Of: odoo/odoo#102281
Original PR description
When computing the edi_formats on a journal, keep the ones that are already checked (if they are compatible with this journal). The bug occurs when migrating a DB: if a new edi_format is created, the `create` will call the `_compute_edi_format_ids` on all journals. Thus, all edi_formats will be reset since nothing keeps track of the already checked edi_formats. This PR fixes this. Forward-Port-Of: odoo/odoo#102281
In [1] the padding of the discrete cookies bar template was moved from the column to the row. This prevents editing the padding per column using the website editor. This commit moves this padding back onto the columns. This PR also unifies the python & JS behavior of cookies setter methods. [1]: https://github.com/odoo/odoo/commit/2ca91a90d0aa61405547349d5cd366179bc3f419 task-2800976 Forward-Port-Of: odoo/odoo#101859
Original PR description
In [1] the padding of the discrete cookies bar template was moved from the column to the row. This prevents editing the padding per column using the website editor. This commit moves this padding back onto the columns. This PR also unifies the python & JS behavior of cookies setter methods. [1]: https://github.com/odoo/odoo/commit/2ca91a90d0aa61405547349d5cd366179bc3f419 task-2800976 Forward-Port-Of: odoo/odoo#101859
As per request in the wowl pad > * [NGR] restore the v15 design of editable listviews https://www.awesomescreenshot.com/image/33055833?key=3d307067d11d22f974a5a18cbf5a6fd5 > * i.e. remove green outline, and fix bug that turns the rest of the row grey when navigating with the keyboard (see bug here > https://www.awesomescreenshot.com/image/33055887?key=333099c1bce38f60a375613a9c1083c0 ) **Before:** <img width="1321" alt="Screenshot 2022-10-05 at 14 14 57" src="https://user-images.gith
Original PR description
As per request in the wowl pad > * [NGR] restore the v15 design of editable listviews https://www.awesomescreenshot.com/image/33055833?key=3d307067d11d22f974a5a18cbf5a6fd5 > * i.e. remove green outline, and fix bug that turns the rest of the row grey when navigating with the keyboard (see bug here > https://www.awesomescreenshot.com/image/33055887?key=333099c1bce38f60a375613a9c1083c0 ) **Before:** <img width="1321" alt="Screenshot 2022-10-05 at 14 14 57" src="https://user-images.githubusercontent.com/3245568/194058097-0e38477a-48ee-4570-9420-1cc8a5cf373a.png"> **After:** <img width="1326" alt="Screenshot 2022-10-05 at 14 12 29" src="https://user-images.githubusercontent.com/3245568/194058116-90afa3ee-410f-44f9-8685-89280699c6d9.png"> --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102268
When a backorder was created and the auto_batch was activated for this picking_type, no batch was assigned to the created backorder, even if it matched the auto-batch criterias. Now when a picking is done, we check if backorders were created. If they are eligible for auto-batchs (given their picking_type, etc.), they also get the auto_batch done for them. We can't simply use the previous picking's batch, because if this batch is now done, then introducing a non-done picking into the b
Original PR description
When a backorder was created and the auto_batch was activated for this picking_type, no batch was assigned to the created backorder, even if it matched the auto-batch criterias. Now when a picking is done, we check if backorders were created. If they are eligible for auto-batchs (given their picking_type, etc.), they also get the auto_batch done for them. We can't simply use the previous picking's batch, because if this batch is now done, then introducing a non-done picking into the batch would raise an inconsistency between the pickings' states and raise an error. Task-2971346 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102306 Forward-Port-Of: odoo/odoo#99501
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#102328
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#102328
The status badge on workorder kanban card was hidden behind a dropdown widget because of a wrongly used class. 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#101029
Original PR description
The status badge on workorder kanban card was hidden behind a dropdown widget because of a wrongly used class. 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#101029
Closes #102166 @adr-odoo this is a "fix" that is mostly a bypass: but this subview of the x2many barcode nomenclature is very weird: having a `col="4"` on the outer group (and no inner group) caused some fields to disappear entirely somehow. Pbly worth a look. Forward-Port-Of: odoo/odoo#102338
Original PR description
Closes #102166 @adr-odoo this is a "fix" that is mostly a bypass: but this subview of the x2many barcode nomenclature is very weird: having a `col="4"` on the outer group (and no inner group) caused some fields to disappear entirely somehow. Pbly worth a look. Forward-Port-Of: odoo/odoo#102338
A value was set as 0 instead of false, causing a traceback. Forward-Port-Of: odoo/odoo#102342
Original PR description
A value was set as 0 instead of false, causing a traceback. Forward-Port-Of: odoo/odoo#102342
When 2e8647bf1662168e5f74395c7c624ef74670c0b2 converted the browser runner to a more reactive / evented system, one bit was missed in "wait_code_ok": concurrent.futures.Future raises exceptions on various events, such as tour timeouts. Because those exceptions were not caught (or just ignored) the code which takes screenshots was bypassed, leading to a lack of screenshots on tour timeouts (and a few other rarer errors), making debugging more complicated. The error reporting was also not ideal
Original PR description
When 2e8647bf1662168e5f74395c7c624ef74670c0b2 converted the browser runner to a more reactive / evented system, one bit was missed in "wait_code_ok": concurrent.futures.Future raises exceptions on various events, such as tour timeouts. Because those exceptions were not caught (or just ignored) the code which takes screenshots was bypassed, leading to a lack of screenshots on tour timeouts (and a few other rarer errors), making debugging more complicated. The error reporting was also not ideal as `wait_code_ok` would raise an unexpected (by its caller) `TimeoutError` rather than `ChromeBrowserException`. Fix those two issues, should hopefully makes these occurrences clearer and easier to diagnose. Forward-Port-Of: odoo/odoo#102344
Before this PR, a websocket would wait for the server to close it with a `SessionExpired` close code to be refreshed after the user logged in/out. Indeed, the server is responsible to check for outdated sessions on incoming/outgoing messages. This is problematic: a user logging in with more than one tab opened, would have to wait to receive its messages. This PR solves this issue by refreshing the connection immediately in this scenario. Forward-Port-Of: odoo/odoo#101385
Original PR description
Before this PR, a websocket would wait for the server to close it with a `SessionExpired` close code to be refreshed after the user logged in/out. Indeed, the server is responsible to check for outdated sessions on incoming/outgoing messages. This is problematic: a user logging in with more than one tab opened, would have to wait to receive its messages. This PR solves this issue by refreshing the connection immediately in this scenario. Forward-Port-Of: odoo/odoo#101385
Enterprise PR: https://github.com/odoo/enterprise/pull/31939 Forward-Port-Of: odoo/odoo#102253
Original PR description
Enterprise PR: https://github.com/odoo/enterprise/pull/31939 Forward-Port-Of: odoo/odoo#102253
"Storage Category Capacity" menu appears as long as the debug mode is on, even if the "Storage Category" isn't selected in the settings and the corresponding group isn't set. Since this menu is accessible from the Storage Category form anyway, we move the link to this table in the settings (where we can safely display it in debug AND with the setting activated), and we remove it from the menu. Part of task-2985735 --- I confirm I have signed the CLA and read the PR guidelines at www.od
Original PR description
"Storage Category Capacity" menu appears as long as the debug mode is on, even if the "Storage Category" isn't selected in the settings and the corresponding group isn't set. Since this menu is accessible from the Storage Category form anyway, we move the link to this table in the settings (where we can safely display it in debug AND with the setting activated), and we remove it from the menu. Part of task-2985735 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101749
Forward-Port-Of: odoo/odoo#102339
Original PR description
Forward-Port-Of: odoo/odoo#102339
There was a missing class on the pricelist selector for product pages leading to the pricelist selector simply not being displayed. TaskId-3007737 Forward-Port-Of: odoo/odoo#102361
Original PR description
There was a missing class on the pricelist selector for product pages leading to the pricelist selector simply not being displayed. TaskId-3007737 Forward-Port-Of: odoo/odoo#102361
Closes #102347 Forward-Port-Of: odoo/odoo#102373
Original PR description
Closes #102347 Forward-Port-Of: odoo/odoo#102373
When you are opening the session form in the backend to display what has been done during the session you cannot easily see what was the starting and ending balance of the cash of a session. So we are now displaying those fields in the session form. 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
Original PR description
When you are opening the session form in the backend to display what has been done during the session you cannot easily see what was the starting and ending balance of the cash of a session. So we are now displaying those fields in the session form. 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#102375
The "configure email server" was misplaced, a colspan fix this issues --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102377
Original PR description
The "configure email server" was misplaced, a colspan fix this issues --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102377
Before this commit, the `updateBusPresence` method could have been called many times in a row, resulting in many `update_presence` messages being sent through the socket. This commit solves this issue by throttling this method in order for it to only be called once in `UPDATE_BUS_PRESENCE_DELAY` seconds. Forward-Port-Of: odoo/odoo#102251
Original PR description
Before this commit, the `updateBusPresence` method could have been called many times in a row, resulting in many `update_presence` messages being sent through the socket. This commit solves this issue by throttling this method in order for it to only be called once in `UPDATE_BUS_PRESENCE_DELAY` seconds. Forward-Port-Of: odoo/odoo#102251
- Set striped tables order to 'even' - Adjust padding enterprise: - https://github.com/odoo/enterprise/pull/32336 task-3008334 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102304
Original PR description
- Set striped tables order to 'even' - Adjust padding enterprise: - https://github.com/odoo/enterprise/pull/32336 task-3008334 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102304
Before this commit, it was not possible to edit the path via the model field selector popover input (visible in debug mode). We fix that. Forward-Port-Of: odoo/odoo#102099
Original PR description
Before this commit, it was not possible to edit the path via the model field selector popover input (visible in debug mode). We fix that. Forward-Port-Of: odoo/odoo#102099
Fixes skills display on both employee and applicant page. task-3002256 Forward-Port-Of: odoo/odoo#102125
Original PR description
Fixes skills display on both employee and applicant page. task-3002256 Forward-Port-Of: odoo/odoo#102125
This PR adapts the form views since the merge of #100570. task-3002537 Forward-Port-Of: odoo/odoo#102341
Original PR description
This PR adapts the form views since the merge of #100570. task-3002537 Forward-Port-Of: odoo/odoo#102341
Currently, the user can resequence invoices that are in a locked period. This is not desirable, this commit fixes this. Enterprise PR: https://github.com/odoo/enterprise/pull/31695 Forward-Port-Of: odoo/odoo#102396 Forward-Port-Of: odoo/odoo#100954
Original PR description
Currently, the user can resequence invoices that are in a locked period. This is not desirable, this commit fixes this. Enterprise PR: https://github.com/odoo/enterprise/pull/31695 Forward-Port-Of: odoo/odoo#102396 Forward-Port-Of: odoo/odoo#100954
- Before this commit The carets of autocomplete fields and datepickers inputs is behind the text if the value shown in the input is too long.  - After this commit Fixed.  Forward-Port-Of: odoo/odoo#102335
Original PR description
- Before this commit The carets of autocomplete fields and datepickers inputs is behind the text if the value shown in the input is too long.  - After this commit Fixed.  Forward-Port-Of: odoo/odoo#102335
Due to how we change the reactivity in the UI and the printing changes that kept being computed and set when an order object is created, fetched orders became part of the `ordersToUpdateSet` which is wrong. Only updated orders should be tracked and send to the back end. Also fixed how the transferred order should act when offline then online. Forward-Port-Of: odoo/odoo#102415
Original PR description
Due to how we change the reactivity in the UI and the printing changes that kept being computed and set when an order object is created, fetched orders became part of the `ordersToUpdateSet` which is wrong. Only updated orders should be tracked and send to the back end. Also fixed how the transferred order should act when offline then online. Forward-Port-Of: odoo/odoo#102415
Part of task-2978890 Forward-Port-Of: odoo/odoo#102417
Original PR description
Part of task-2978890 Forward-Port-Of: odoo/odoo#102417
Before the fix, the payable/receivable line would also receive the distribution. The compute function will only add it to the lines of display_type 'product' (as before 7e34030). We now also add it to taxes that don't have `use_in_closing`. 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#10
Original PR description
Before the fix, the payable/receivable line would also receive the distribution. The compute function will only add it to the lines of display_type 'product' (as before 7e34030). We now also add it to taxes that don't have `use_in_closing`. 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#101336
Currently, in a Journal Entry, applying a tax on any journal item doesn't compute the corresponding tax line. We end up in a situation where the move appears balanced but doesn't take into account the taxes applied. Moreover, the move cannot be posted. The solution involves several steps: - Changing a tax on a line now triggers a save. - Changing the debit or credit on a line with taxes will also trigger a save. - The company's suspense account is used for the balancing line. During
Original PR description
Currently, in a Journal Entry, applying a tax on any journal item doesn't compute the corresponding tax line. We end up in a situation where the move appears balanced but doesn't take into account the taxes applied. Moreover, the move cannot be posted. The solution involves several steps: - Changing a tax on a line now triggers a save. - Changing the debit or credit on a line with taxes will also trigger a save. - The company's suspense account is used for the balancing line. During the save, a check is added to see if the move is unbalanced. In that case, a balancing line will automatically be created to ensure the move can be saved. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102040
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#102376
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#102376
If the kanban box template is too simple, with basically no classes to wrap content, the tags would suddenly take too much vertical space and overflow the kanban card. Since the property h-100 doesn't seem to be actually needed, it's removed. Before: <img width="399" alt="Capture d’écran 2022-10-06 à 12 23 54" src="https://user-images.githubusercontent.com/5216993/194290495-0ec14b27-dbd0-4baf-a92e-b8dd21b34e2c.png"> After: <img width="366" alt="Capture d’écran 2022-10-06 à 12 24
Original PR description
If the kanban box template is too simple, with basically no classes to wrap content, the tags would suddenly take too much vertical space and overflow the kanban card. Since the property h-100 doesn't seem to be actually needed, it's removed. Before: <img width="399" alt="Capture d’écran 2022-10-06 à 12 23 54" src="https://user-images.githubusercontent.com/5216993/194290495-0ec14b27-dbd0-4baf-a92e-b8dd21b34e2c.png"> After: <img width="366" alt="Capture d’écran 2022-10-06 à 12 24 01" src="https://user-images.githubusercontent.com/5216993/194290531-c97cb2ee-6160-41e5-98ae-36c5fc6209f3.png"> Forward-Port-Of: odoo/odoo#102386
Going to My profile (user menu item when hr installed), the user name is not fully displayed in the breadcrumb although there is enough space to display it. We fix that by removing a rule that has become apparently useless. Forward-Port-Of: odoo/odoo#102408
Original PR description
Going to My profile (user menu item when hr installed), the user name is not fully displayed in the breadcrumb although there is enough space to display it. We fix that by removing a rule that has become apparently useless. Forward-Port-Of: odoo/odoo#102408
Description of the issue/feature this PR addresses: 1. Adapts the layout of the `Alternatives` tab of the purchase order form to the new grid system. 2. Fixes display of the confirmation mail for receipts in the purchase order form. 3. Adapts the layout of the backorder confirmation wizard to the new grid system. A few fixes of the visuals of the Purchase Order form. Current behavior before PR: Alternatives RFQ:  Confirmation before arrival:  Backorder confirmation:  Desired behavior after PR is merged: Alternatives RFQ:  Confirmation before arrival:  Backorder confirmation:  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102431
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#102432
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#102432
Problem: In the point of sale, when a sale report is printed, the payment methods were written as [object object] because of the new translation behavior. The sql function and the rendering is now written differently in order to see the labels of the payment methods --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102445
Original PR description
Problem: In the point of sale, when a sale report is printed, the payment methods were written as [object object] because of the new translation behavior. The sql function and the rendering is now written differently in order to see the labels of the payment methods --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102445
Before this commit, when reconnecting to a call that was still holding a participantCard of an outdated rtcSession a crash would occur as joining a call removes all your previous rtcSessions while generating a new one while having a `isCausal` on their participantCards. This commit removes this `isCausal` as the rtcSession of a channelMember/participantCard should be able to change over time. Forward-Port-Of: odoo/odoo#102447
Original PR description
Before this commit, when reconnecting to a call that was still holding a participantCard of an outdated rtcSession a crash would occur as joining a call removes all your previous rtcSessions while generating a new one while having a `isCausal` on their participantCards. This commit removes this `isCausal` as the rtcSession of a channelMember/participantCard should be able to change over time. Forward-Port-Of: odoo/odoo#102447
The status indicator for optional plans switches between grey and green and creates a perception that action is required, when in fact, all values are valid. For this reason, the status indicator only applies to mandatory plans (green: ok, orange: editing, red: invalid) The grey status is removed entirely. Forward-Port-Of: odoo/odoo#101733
Original PR description
The status indicator for optional plans switches between grey and green and creates a perception that action is required, when in fact, all values are valid. For this reason, the status indicator only applies to mandatory plans (green: ok, orange: editing, red: invalid) The grey status is removed entirely. Forward-Port-Of: odoo/odoo#101733
When the section and note fields were converted, the section and note text field ignored the list-specialisation of the text field, resulting in a textarea with a minimum height of 50 in list view which causes the line to be too high. It was also not using the o_field_text class which among other things hides the resize handle on the text area which looks weird in list view. This commit fixes that. Forward-Port-Of: odoo/odoo#102325
Original PR description
When the section and note fields were converted, the section and note text field ignored the list-specialisation of the text field, resulting in a textarea with a minimum height of 50 in list view which causes the line to be too high. It was also not using the o_field_text class which among other things hides the resize handle on the text area which looks weird in list view. This commit fixes that. Forward-Port-Of: odoo/odoo#102325
Before this commit, only when using the save button on the profile, the context is reloaded with the new language. If we use the breadcrumb to exit the profile view, the new language is saved, but the context is not reloaded. Forward-Port-Of: odoo/odoo#102419
Original PR description
Before this commit, only when using the save button on the profile, the context is reloaded with the new language. If we use the breadcrumb to exit the profile view, the new language is saved, but the context is not reloaded. Forward-Port-Of: odoo/odoo#102419
Even if the `StateSelectionField` is readonly we doesn't want visual difference and we remove the `disabled` class. This behavior is the same as in 15. We also remove `btn-link` as it's not appear as a link and we had to set `p-0` to avoid the growing of the cell. Steps to reproduce: > Open the helpdesk app > Click on VIP Support tickets > Go to the list view > Add kanban_state column => visual bug Forward-Port-Of: odoo/odoo#102209
Original PR description
Even if the `StateSelectionField` is readonly we doesn't want visual difference and we remove the `disabled` class. This behavior is the same as in 15. We also remove `btn-link` as it's not appear as a link and we had to set `p-0` to avoid the growing of the cell. Steps to reproduce: > Open the helpdesk app > Click on VIP Support tickets > Go to the list view > Add kanban_state column => visual bug Forward-Port-Of: odoo/odoo#102209
This time, for good Forward-Port-Of: odoo/odoo#102345
Original PR description
This time, for good Forward-Port-Of: odoo/odoo#102345
Forward-Port-Of: odoo/odoo#102437
Original PR description
Forward-Port-Of: odoo/odoo#102437
Forward-Port-Of: odoo/odoo#102438
Original PR description
Forward-Port-Of: odoo/odoo#102438
A revert + a simpler correction of the original bug. Forward-Port-Of: odoo/odoo#102454
Original PR description
A revert + a simpler correction of the original bug. Forward-Port-Of: odoo/odoo#102454
Before this commit, in debug=assets, if a test crashed for instance because we try to click on an element that doesn't exist, we tried to load the stacktrace js lib, via loadJS. However, in the test environment, loadJS is patched to go through mockRPC. If in that particular test, mockRPC did an assertion (e.g. assert.step), we entered an infinite loop of loadJS calls, which obviously made the tab crash. With this commit, we ensure to use the real loadJS function when we want to fetch the stac
Original PR description
Before this commit, in debug=assets, if a test crashed for instance because we try to click on an element that doesn't exist, we tried to load the stacktrace js lib, via loadJS. However, in the test environment, loadJS is patched to go through mockRPC. If in that particular test, mockRPC did an assertion (e.g. assert.step), we entered an infinite loop of loadJS calls, which obviously made the tab crash. With this commit, we ensure to use the real loadJS function when we want to fetch the stacktrace lib. 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#102208
Forward-Port-Of: odoo/odoo#101104
Original PR description
Forward-Port-Of: odoo/odoo#101104
Before this PR, the presence service was relying on window events blur/focus to determine whether or not odoo was focused. The issue is that in the website backend, an iframe is used. When this iframe is focused, the window looses the focus and vice versa. This commit fixes this issue by using `window.parent.hasFocus` method. task-3003950 Forward-Port-Of: odoo/odoo#102479
Original PR description
Before this PR, the presence service was relying on window events blur/focus to determine whether or not odoo was focused. The issue is that in the website backend, an iframe is used. When this iframe is focused, the window looses the focus and vice versa. This commit fixes this issue by using `window.parent.hasFocus` method. task-3003950 Forward-Port-Of: odoo/odoo#102479
In this commit we the fix the payment methods form view because it was broken after changing the implementation of the `<group>` element to the new `grid` format in CSS. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102480
Original PR description
In this commit we the fix the payment methods form view because it was broken after changing the implementation of the `<group>` element to the new `grid` format in CSS. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#102480
The commit https://github.com/odoo/odoo/commit/c877cab866f2c1968f4f9aaf8ceebc02fa014eed has recently refactored the css of the kanban column progress bar making the rules for o_legacy_kanban_counter be applied only in legacy kanban views. This lead the style of the progress bars in activity view to be broken. Here we fix that style by copying the rules we want in the file activity_view.scss. Forward-Port-Of: odoo/odoo#102482
Original PR description
The commit https://github.com/odoo/odoo/commit/c877cab866f2c1968f4f9aaf8ceebc02fa014eed has recently refactored the css of the kanban column progress bar making the rules for o_legacy_kanban_counter be applied only in legacy kanban views. This lead the style of the progress bars in activity view to be broken. Here we fix that style by copying the rules we want in the file activity_view.scss. Forward-Port-Of: odoo/odoo#102482
This commit fixes the behavior of the FormView dialog. Since the view is only visible in edition, it is no longer necessary to keep the dialog open after the save has been processed. If the save has been successful, the dialog now closes as expected. It also adapts the code of website, which overrided the save method to do a similar action. Now, the onSaveAction getter is overriden instead, allowing to bring the correct parameters to the doAction call. A test has been added to assert this
Original PR description
This commit fixes the behavior of the FormView dialog. Since the view is only visible in edition, it is no longer necessary to keep the dialog open after the save has been processed. If the save has been successful, the dialog now closes as expected. It also adapts the code of website, which overrided the save method to do a similar action. Now, the onSaveAction getter is overriden instead, allowing to bring the correct parameters to the doAction call. A test has been added to assert this behavior. 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#102182
This PR contains improvements and fixes of the grid mode that was added in [1]. The linked design-themes PR can be found at [2]. [1]: https://github.com/odoo/odoo/pull/93144 [2]: https://github.com/odoo/design-themes/pull/592 task-2973198 Forward-Port-Of: odoo/odoo#99857
Original PR description
This PR contains improvements and fixes of the grid mode that was added in [1]. The linked design-themes PR can be found at [2]. [1]: https://github.com/odoo/odoo/pull/93144 [2]: https://github.com/odoo/design-themes/pull/592 task-2973198 Forward-Port-Of: odoo/odoo#99857
This commit adapts the code of the NewContentModal from website_appointment. Because changes have been made in (1). Now, it is no longer needed to call the doAction from this file, since a method is accessible from the main NewContentModal component. (1): 5b5e9c3155c0a482ba03f0f260d383fa3322127f Community PR: https://github.com/odoo/odoo/pull/102182 Forward-Port-Of: odoo/enterprise#32413
Original PR description
This commit adapts the code of the NewContentModal from website_appointment. Because changes have been made in (1). Now, it is no longer needed to call the doAction from this file, since a method is accessible from the main NewContentModal component. (1): 5b5e9c3155c0a482ba03f0f260d383fa3322127f Community PR: https://github.com/odoo/odoo/pull/102182 Forward-Port-Of: odoo/enterprise#32413
Rename KnowledgeService into KnowledgeCommandsService and simplify its behavior. It now only stores one record at a time, and is not responsible for its contents. Modify form_controller_patch to search less often for a Knowledge compatible record (check at every patch when the resId of the current record in the form view changes) Add some docstring. Task-3004117 Forward-Port-Of: odoo/enterprise#32392
Original PR description
Rename KnowledgeService into KnowledgeCommandsService and simplify its behavior. It now only stores one record at a time, and is not responsible for its contents. Modify form_controller_patch to search less often for a Knowledge compatible record (check at every patch when the resId of the current record in the form view changes) Add some docstring. Task-3004117 Forward-Port-Of: odoo/enterprise#32392
Purpose ======= Allow users to create their structure as they see fit to cover as many use cases as possible => This also allows some simplification of the code as we do not need to handle on-the-fly conversions Specifications ============ Make property fields available as soon as articles have a parent (no need for the article to be an item) => If I want to, I can add property fields on my doc etc Remove the constraint that says that a parent can only have one type of baby (item
Original PR description
Purpose ======= Allow users to create their structure as they see fit to cover as many use cases as possible => This also allows some simplification of the code as we do not need to handle on-the-fly…
Purpose ======= Allow users to create their structure as they see fit to cover as many use cases as possible => This also allows some simplification of the code as we do not need to handle on-the-fly conversions Specifications ============ Make property fields available as soon as articles have a parent (no need for the article to be an item) => If I want to, I can add property fields on my doc etc Remove the constraint that says that a parent can only have one type of baby (item vs "normal) => Can be mixed, it's not an issue Remove the auto-conversions when article change their nature (item vs "normal) => Article items cannot be moved (hide the kebab button) => Drag & dropping normal articles does not convert them ==> Basically the nature of an article is based on where they are created and never changes ==> In 16.1 we'll add a button in the kebab menu but not now That being said, property fields are thus shared by all children of a parent, no matter if they are items or not Task-3004047 Forward-Port-Of: odoo/enterprise#32166
Before this commit, only when using the save button on the profile, the context is reloaded with the new language. If we use the breadcrumb to exit the profile view, the new language is saved, but the context is not reloaded. Community PR : https://github.com/odoo/odoo/pull/102419 Forward-Port-Of: odoo/enterprise#32396
Original PR description
Before this commit, only when using the save button on the profile, the context is reloaded with the new language. If we use the breadcrumb to exit the profile view, the new language is saved, but the context is not reloaded. Community PR : https://github.com/odoo/odoo/pull/102419 Forward-Port-Of: odoo/enterprise#32396
Forward-Port-Of: odoo/enterprise#32405
Original PR description
Forward-Port-Of: odoo/enterprise#32405
…ly copied to SOL Currently in sale_subscription, when using a quotation template composed of multiple lines with the same product but different descriptions, the descriptions are not properly copied. They are all set to the first product's description in the quotation template. This commit fixes this by removing the override of _compute_name which adds some unrequired dependencies causing the method to be called when it's not supposed to. task-3003962 Forward-Port-Of: odoo/enterprise#322
Original PR description
…ly copied to SOL Currently in sale_subscription, when using a quotation template composed of multiple lines with the same product but different descriptions, the descriptions are not properly copied. They are all set to the first product's description in the quotation template. This commit fixes this by removing the override of _compute_name which adds some unrequired dependencies causing the method to be called when it's not supposed to. task-3003962 Forward-Port-Of: odoo/enterprise#32237
As the FieldDate & FieldDateTime mobile app customization (aka. use the platform's native datepicker) applies only on the deprecated legacy Widget implementation and the modern views doesn't use them anymore, we can safely remove them. Similar feature will be reintroduced if needed in a future version (in one form or the other). Note: it only affects Odoo run through the mobile app on Android (iOS already didn't use them due to buggy implementation). Forward-Port-Of: odoo/enterprise#
Original PR description
As the FieldDate & FieldDateTime mobile app customization (aka. use the platform's native datepicker) applies only on the deprecated legacy Widget implementation and the modern views doesn't use them anymore, we can safely remove them. Similar feature will be reintroduced if needed in a future version (in one form or the other). Note: it only affects Odoo run through the mobile app on Android (iOS already didn't use them due to buggy implementation). Forward-Port-Of: odoo/enterprise#32388
Currently lock dates in the future are allowed, they shouldn't. This commit fixes this. Community PR: https://github.com/odoo/odoo/pull/100954 Forward-Port-Of: odoo/enterprise#32380 Forward-Port-Of: odoo/enterprise#31695
Original PR description
Currently lock dates in the future are allowed, they shouldn't. This commit fixes this. Community PR: https://github.com/odoo/odoo/pull/100954 Forward-Port-Of: odoo/enterprise#32380 Forward-Port-Of: odoo/enterprise#31695
The text "You have processed less products than the initial demand" appeared 2 times when picking validation needs backorder confirmation. Due to unconditioned 'detailed-explanation-text'. task: 2985735 Forward-Port-Of: odoo/enterprise#31838
Original PR description
The text "You have processed less products than the initial demand" appeared 2 times when picking validation needs backorder confirmation. Due to unconditioned 'detailed-explanation-text'. task: 2985735 Forward-Port-Of: odoo/enterprise#31838
The payment should only be reconciled in auto_invoice mode. If we are not in auto invoice mode, the payment will be saved and will be reconciled when the invoice is created by the cron. Before this commit, the payment would be reconciled automatically and this would increase the next_invoice_date without actually creating an invoice (even if the transaction was existant). Forward-Port-Of: odoo/enterprise#32377
Original PR description
The payment should only be reconciled in auto_invoice mode. If we are not in auto invoice mode, the payment will be saved and will be reconciled when the invoice is created by the cron. Before this commit, the payment would be reconciled automatically and this would increase the next_invoice_date without actually creating an invoice (even if the transaction was existant). Forward-Port-Of: odoo/enterprise#32377
- Set striped tables order to `odd` - Reduce striped-bg factor community: - https://github.com/odoo/odoo/pull/102304 task-3008334 Forward-Port-Of: odoo/enterprise#32336
Original PR description
- Set striped tables order to `odd` - Reduce striped-bg factor community: - https://github.com/odoo/odoo/pull/102304 task-3008334 Forward-Port-Of: odoo/enterprise#32336
In the Belgian Balance Sheet, the lines "total de l'actif" and "total du passif" had mistakenly been moved at the beginning of their parent section when converting the report to the new model. Forward-Port-Of: odoo/enterprise#32370
Original PR description
In the Belgian Balance Sheet, the lines "total de l'actif" and "total du passif" had mistakenly been moved at the beginning of their parent section when converting the report to the new model. Forward-Port-Of: odoo/enterprise#32370
Task-2998138 Forward-Port-Of: odoo/enterprise#31939
Original PR description
Task-2998138 Forward-Port-Of: odoo/enterprise#31939
Add a secondary "call to action" : Create Batch in payments tree view. Visible when min. 1 payment is selected in the list. In order to do it in stable, the `view_account_payment_tree_inherit_account_batch_payment` is being extended. Therefore, `account_batch_payment_views` needs to be loaded before `account_payment_views`. For that, `view_account_payment_tree_popup_inherit_account_batch_payment` is moved to `account_payment_views`. task-2897152 Forward-Port-Of: odoo/enterprise#31898
Original PR description
Add a secondary "call to action" : Create Batch in payments tree view. Visible when min. 1 payment is selected in the list. In order to do it in stable, the `view_account_payment_tree_inherit_account_batch_payment` is being extended. Therefore, `account_batch_payment_views` needs to be loaded before `account_payment_views`. For that, `view_account_payment_tree_popup_inherit_account_batch_payment` is moved to `account_payment_views`. task-2897152 Forward-Port-Of: odoo/enterprise#31898
TaskId-3008787 Forward-Port-Of: odoo/enterprise#32361
Original PR description
TaskId-3008787 Forward-Port-Of: odoo/enterprise#32361
Forward-Port-Of: odoo/enterprise#31935
Original PR description
Forward-Port-Of: odoo/enterprise#31935
Depreciation board improvements - The entries are not numbered anymore - Any entry related to the asset is shown in chronologic order More robust computation - Depreciation field in the computation board now reflects the balance of the item on the expense account ; not the total of the depreciation entries anymore. - No prorata entry anymore - Cumulative and depreciable value in the depreciation board and in the form view always consistent - Depreciation entries are all posted on the la
Original PR description
Depreciation board improvements - The entries are not numbered anymore - Any entry related to the asset is shown in chronologic order More robust computation - Depreciation field in the computation…
Depreciation board improvements - The entries are not numbered anymore - Any entry related to the asset is shown in chronologic order More robust computation - Depreciation field in the computation board now reflects the balance of the item on the expense account ; not the total of the depreciation entries anymore. - No prorata entry anymore - Cumulative and depreciable value in the depreciation board and in the form view always consistent - Depreciation entries are all posted on the last day of the month/year - Each deprecation entry absorbs any rounding differences - Declining method and monthly depreciation compatibility (OPW-2419286) More intutitive management of imported assets - By defining the asset's lifecycle rather than the computations expected from Odoo, less fields are necessary to import assets. New supported cases - Negative assets management - Daily computation takes into account the number of days in each month. - The period between the last posted depreciation entry and any asset modification gets deprecated, if necessary. And a dynamic preview of this entry is added. Forward-Port-Of: odoo/enterprise#28307
Forward-Port-Of: odoo/enterprise#32354
Original PR description
Forward-Port-Of: odoo/enterprise#32354
During the documents refactor to wowl2 the upload function was wrongfully made to get `tag_ids` as an optional argument. However the route used to upload files does in fact require the argument to work. During the cleanup the `tag_ids` argument was moved from `params` to the main object used call a file upload, since `params` was designed to be used for optional arguments (which there are none now and has been removed), however one of the call to the uploadFiles function was not properly adapte
Original PR description
During the documents refactor to wowl2 the upload function was wrongfully made to get `tag_ids` as an optional argument. However the route used to upload files does in fact require the argument to work. During the cleanup the `tag_ids` argument was moved from `params` to the main object used call a file upload, since `params` was designed to be used for optional arguments (which there are none now and has been removed), however one of the call to the uploadFiles function was not properly adapted and still used the old optional params to provide the tags, this results in the upload button being completely unusable. Forward-Port-Of: odoo/enterprise#32340
Purpose: - Slightly modify the list and kanban views as they will be showed inside articles with the embed feature. - List: Change fields name, add fields, and make some optional. - Kanban: Remove fields, add parent article, show complete name, and make cards a little smaller. Task-2995330 Forward-Port-Of: odoo/enterprise#31932
Original PR description
Purpose: - Slightly modify the list and kanban views as they will be showed inside articles with the embed feature. - List: Change fields name, add fields, and make some optional. - Kanban: Remove fields, add parent article, show complete name, and make cards a little smaller. Task-2995330 Forward-Port-Of: odoo/enterprise#31932
Forward-Port-Of: odoo/enterprise#31561
Original PR description
Forward-Port-Of: odoo/enterprise#31561
…efund Before this commit, the qty_invoiced of subscription added all the related invoices. Refund were added to the qty_invoiced. See this example: a subscription with 2 lines P1, Qty 1 P2, Qty 2 If we invoice both lines, qty invoiced will be equal to Qty 1 and Qty 2 If we refund the invoice, the expected qty_invoiced value is 0 for both lines. Forward-Port-Of: odoo/enterprise#32165 Forward-Port-Of: odoo/enterprise#31908
Original PR description
…efund Before this commit, the qty_invoiced of subscription added all the related invoices. Refund were added to the qty_invoiced. See this example: a subscription with 2 lines P1, Qty 1 P2, Qty 2 If we invoice both lines, qty invoiced will be equal to Qty 1 and Qty 2 If we refund the invoice, the expected qty_invoiced value is 0 for both lines. Forward-Port-Of: odoo/enterprise#32165 Forward-Port-Of: odoo/enterprise#31908
# Current behaviour By default the automatic field Company doesn't fill up, even if set in the settings Signature Item Type. # Steps to reproduce - Install Sign - Activate Developer Mode - Go to Signature Item Type settings and check the Company field. # Reason for the problem The company of a contact depends if it's an individual or company. (individual -> parent_id, company -> commercial_partner_id) # Fix As suggested by PO (dbo) and (sig), we remove the automatic field company_
Original PR description
# Current behaviour By default the automatic field Company doesn't fill up, even if set in the settings Signature Item Type. # Steps to reproduce - Install Sign - Activate Developer Mode - Go to Signature Item Type settings and check the Company field. # Reason for the problem The company of a contact depends if it's an individual or company. (individual -> parent_id, company -> commercial_partner_id) # Fix As suggested by PO (dbo) and (sig), we remove the automatic field company_id.name. # Affected versions - 14.0 - 15.0 - saas-15.2 - saas-15.3 - 16.0 - master --- opw-3001011 Forward-Port-Of: odoo/enterprise#32155
Previously, in the Bank Statement tree view: - The bank reconciliation widget was opened when clicking on any line - This prevented fields from being editable inline And now, in the same view - The widget can still be opened by clicking on the name column - Other fields that aren't readonly can be edited inline Forward-Port-Of: odoo/enterprise#31677
Original PR description
Previously, in the Bank Statement tree view: - The bank reconciliation widget was opened when clicking on any line - This prevented fields from being editable inline And now, in the same view - The widget can still be opened by clicking on the name column - Other fields that aren't readonly can be edited inline Forward-Port-Of: odoo/enterprise#31677
The label for field l10n_cl_last_uid is confusing. We changed to explain that the Id corresponds to the last message UID read by odoo from the IMAP mail. Forward-Port-Of: odoo/enterprise#31683 Forward-Port-Of: odoo/enterprise#29619
Original PR description
The label for field l10n_cl_last_uid is confusing. We changed to explain that the Id corresponds to the last message UID read by odoo from the IMAP mail. Forward-Port-Of: odoo/enterprise#31683 Forward-Port-Of: odoo/enterprise#29619
Specifications: Improve rename on click when article is untitled Previously, when a user clicked on the name of an article, the article was renamed using the article's title in the body only if its name was "untitled" in the user's language. Now, an exception has been added: the article is also renamed if the name of the article is "Untitled" (in English). Specifications: Use new emoji list for random emoji picker Instead of using the old and small list of emojis for picking an em
Original PR description
Specifications: Improve rename on click when article is untitled Previously, when a user clicked on the name of an article, the article was renamed using the article's title in the body only if its…
Specifications: Improve rename on click when article is untitled Previously, when a user clicked on the name of an article, the article was renamed using the article's title in the body only if its name was "untitled" in the user's language. Now, an exception has been added: the article is also renamed if the name of the article is "Untitled" (in English). Specifications: Use new emoji list for random emoji picker Instead of using the old and small list of emojis for picking an emoji at random when clicking on the "Add icon" button, use the new one which contains much more emojis, and which is currently used for the emoji picker. The list of disallowed emojis has been updated accordingly, removing some emojis of it as the chances of picking them at random are very small, but adding some that we really do not want to show (eg. the middle finger). Specifications: various * add back png icon, svg is not sufficient; * fix glitchs in invite model layout; Task-3004122 Forward-Port-Of: odoo/enterprise#32315
t-esc directive has been deprecated. This commit replaces remaining occurrences in the modules under our responsiblity. Was only noticed recently during runs in dev mode because the deprecation warnings are only posted when odoo is launched in dev mode. "Found deprecated directive @t-esc=%r in template %r. Replace by @t-out" in base/models/ir_qweb.py Community PR: odoo/odoo#101886 Forward-Port-Of: odoo/enterprise#32273
Original PR description
t-esc directive has been deprecated. This commit replaces remaining occurrences in the modules under our responsiblity. Was only noticed recently during runs in dev mode because the deprecation warnings are only posted when odoo is launched in dev mode. "Found deprecated directive @t-esc=%r in template %r. Replace by @t-out" in base/models/ir_qweb.py Community PR: odoo/odoo#101886 Forward-Port-Of: odoo/enterprise#32273
Enterprise part of odoo/odoo#102045 Forward-Port-Of: odoo/enterprise#32243
Original PR description
Enterprise part of odoo/odoo#102045 Forward-Port-Of: odoo/enterprise#32243
Following https://github.com/odoo/enterprise/pull/31529, uniform font-weights across versions in order to get "predictable" visual results. Community: - https://github.com/odoo/odoo/pull/102132 task-3006942 Forward-Port-Of: odoo/enterprise#32272
Original PR description
Following https://github.com/odoo/enterprise/pull/31529, uniform font-weights across versions in order to get "predictable" visual results. Community: - https://github.com/odoo/odoo/pull/102132 task-3006942 Forward-Port-Of: odoo/enterprise#32272
Enterprise counterpart of https://github.com/odoo/odoo/pull/100492 Adds the settings in the chart configuration panel. task 2888350 Forward-Port-Of: odoo/enterprise#31466
Original PR description
Enterprise counterpart of https://github.com/odoo/odoo/pull/100492 Adds the settings in the chart configuration panel. task 2888350 Forward-Port-Of: odoo/enterprise#31466
Always generate a Factur-X xml and embed it when a PDF is created. But no edi.document is created, no warnings will be displayed on the invoice, and the PDF is not PDF/A-3. The only purpose here is the Odoo interoperability. Rename the 'Factur-X' option to 'Factur-X PDF/A-3' and make it only visible for FR and DE companies. This 'Factur-X PDF/A-3' option will trigger the regular account.edi flow: create an edi.document and show warnings on the move if errors are detected. When a PDF is pri
Original PR description
Always generate a Factur-X xml and embed it when a PDF is created. But no edi.document is created, no warnings will be displayed on the invoice, and the PDF is not PDF/A-3. The only purpose here is the Odoo interoperability. Rename the 'Factur-X' option to 'Factur-X PDF/A-3' and make it only visible for FR and DE companies. This 'Factur-X PDF/A-3' option will trigger the regular account.edi flow: create an edi.document and show warnings on the move if errors are detected. When a PDF is printed, embed the Factur-X xml and make the PDF a PDF/A-3. Thus, it can be used on Chorus Pro. task-2957808 https://github.com/odoo/odoo/pull/99699 https://github.com/odoo/upgrade/pull/3940 Forward-Port-Of: odoo/enterprise#31851
LU BS, P&L and Annual Tax Report were broken after the reportalypse and the "always edit" update. - Exporting XML files was not possible because `get_lu_electronic_report_values` was moved to `l10n_lu.report.handler` as `get_electronic_report_values` - Creating the Annual Tax Report was not possible because we are calculating how much still needs to be allocated for monthly totals in the annual report. Monthly totals are not stored and do not exist when computing the amount to be allocated whe
Original PR description
LU BS, P&L and Annual Tax Report were broken after the reportalypse and the "always edit" update. - Exporting XML files was not possible because `get_lu_electronic_report_values` was moved to `l10n_lu.report.handler` as `get_electronic_report_values` - Creating the Annual Tax Report was not possible because we are calculating how much still needs to be allocated for monthly totals in the annual report. Monthly totals are not stored and do not exist when computing the amount to be allocated when trying to open the report in the "always edit" mode. - Notebook pages don't wrap in the Annual Tax Report form view resulting in an ugly view. Now monthly totals are calculated first right before computing the totals to be allocated. Getting report values was adjusted to reportalypse changes. Forward-Port-Of: odoo/enterprise#31807
Forward-Port-Of: odoo/enterprise#31992
Original PR description
Forward-Port-Of: odoo/enterprise#31992