Tuesday, September 12, 2023
42 changes · master
Enhancements to existing features
Mail-related test coverage now runs in a multi-company setup by default and avoids repeated gateway setup. This improves confidence that future mail alias behavior will work correctly for businesses operating multiple companies.
Original PR description
Purpose of this merge is to further cleanup and prepare tests for multi-company enabled aliases, notably * activate multi-company environment by default in all mail tests; * avoid multiple init of gateway parameters; * fix leftover of bad alias management; Followup of odoo/odoo# 130768 and odoo/enterprise# 45204 Followup of Task-3453577 (TestMail: Update Alias/Gateway tests for MC) Followup of Task-3453343 (Mail: Cleanup Alias Usage) Prepares Task-36879 (Mail: Support MultiCompany Aliases)
This update removes obsolete code and pending cleanup notes that are no longer planned, while moving an employee departure reason into the main HR area for broader reuse. It also simplifies some internal session and work-entry logic, helping keep the system easier to maintain without introducing major user-facing changes.
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
This change prevents the system from repeatedly logging the same warning about long database constraint names when unrelated constraints are added later. It keeps logs cleaner and makes important operational messages easier to spot without changing business workflows.
Original PR description
This way, we avoid spamming the log each time new constraints are added in the constraint's table. **Description of the issue/feature this PR addresses:** - Install/update module A defines a constraint with a long name -> A log is shown. - Install/update module B introduces a different constraint in the same model. -> Same log as before is shown again. This commit avoids that unneeded log repetition. **Current behavior before PR:** When a table contains a hashed "long named constraint", each time a new constraint is added (from some other module), the same log is spammed. **Desired behavior after PR is merged:** We avoid spamming same log each time new other constraints are added. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mail-related tests now run in a controlled multi-company setup by default, reducing duplicate setup and making future multi-company email alias support more reliable. The update also tightens how aliases are accessed and updated in Studio so existing document-owned aliases are not changed unintentionally.
Original PR description
Purpose of this merge is to further cleanup and prepare tests for multi-company enabled aliases, notably * activate multi-company environment by default in all mail tests; * avoid multiple init of gateway parameters; * fix leftover of bad alias management; Followup of odoo/odoo# 130768 and odoo/enterprise# 45204 Followup of Task-3453577 (TestMail: Update Alias/Gateway tests for MC) Followup of Task-3453343 (Mail: Cleanup Alias Usage) Prepares Task-36879 (Mail: Support MultiCompany Aliases)
Resolved issues and error corrections
Users can once again drag and drop invoice files onto journals from the accounting dashboard. The fix restores the upload target after a recent interface change caused uploads to fail with an error message.
Original PR description
When trying to drop an invoice on a journal on the journal dashboard, it fails with a message "Could not upload files". The issue is that commit 6f95be6884a59665ca7d8a809e7aaa17695fa9b0 changed a CSS class where the upload functionality depended on, making it fail. This commit fixes this issue by adapting the CSS selector of the upload field. [task-3496997](https://www.odoo.com/web#id=3496997&cids=1&menu_id=4720&action=333&active_id=967&model=project.task&view_type=form) --- 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 removes obsolete helper code from the web module that is no longer used. It helps keep the codebase simpler and easier to maintain without changing the user experience.
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
Miscellaneous changes
Currently, when a journal is created during import, we just use the journal name as the code. However, that gets truncated to 5 characters on create, which can conflict with existing journals. The import should be as flexible as possible, as it's better to let users import and fix things after the import rather than debug the import file. - If there is a journal with a shortcode that matches the truncated name of the new journal, just use the existing journal (enterprise PR) - If the shortcode
Original PR description
Currently, when a journal is created during import, we just use the journal name as the code. However, that gets truncated to 5 characters on create, which can conflict with existing journals. The import should be as flexible as possible, as it's better to let users import and fix things after the import rather than debug the import file. - If there is a journal with a shortcode that matches the truncated name of the new journal, just use the existing journal (enterprise PR) - If the shortcode conflict arises within the imported file (so the journals don't exist before the import), keep track of the codes in `vals_list`. The `get_next_bank_cash_default_code` is modified to avoid duplicating code. See also odoo/enterprise#46101 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#134917 Forward-Port-Of: odoo/odoo#132715
This fixes an issue in self-ordering where changing the quantity of a combo meal could show or charge the wrong price. Prices now update accurately, helping avoid customer confusion and incorrect order totals.
Original PR description
When changing the quantity of a combo, the price was not correctly updated due to a miscomputation in the backend. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The domain selector layout has been adjusted so it fills its available space instead of being squeezed by the page layout. This improves readability and makes the interface behave more consistently for users configuring filters or search conditions.
Original PR description
This commit adjusts the width of the domain selector to fill the entirety of its parent so that its dimensions are not restricted by the flex display
Fixes an issue where starting a survey could show two countdown timers at the same time. This reduces confusion for survey participants and keeps the survey experience clear and consistent.
Original PR description
This commit fix a bug introduced by 910897fc97d87b08f01627094ec8c159f5267628 which displayed two timers when starting a survey. Task-3497526 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an issue where selected analytic filter items in financial reports could show incorrect or missing names. This helps users clearly identify the filters applied to their reports and reduces confusion when reviewing report results.
Original PR description
Since the new relational model (odoo/odoo@65c8f41), the display name of the item selected in the analytic filters was not fetched correctly as the active fields were not properly set.
An obsolete part of the Documents sharing dialog was removed after its functionality had already been taken out. This is a low-risk cleanup that simplifies maintenance without changing the user experience.
Original PR description
Purpose ======= In 20f3126f603a98fb4cc540e89ea41ea6d6ae6b49 , all the code of `ShareFormViewDialog` has been removed, but not the class itself. This commit removes `ShareFormViewDialog` because it's not useful now. Task-3495430
The rental date selection on the website now uses Odoo's own date picker instead of an older third-party component. This reduces reliance on outdated external libraries and helps keep the rental shopping experience easier to maintain over time.
Original PR description
When converting the webclient to owl, we wrote our own daterange picker, this commit converts uses of the moment-based daterange picker library to use our own instead. Since the daterange picker library depends on both jQuery and momentjs, this is also a step towards eventual removal of those libraries that we no longer need. Community: https://github.com/odoo/odoo/pull/134647
- Issue-: Broken the portal view because of totals. - Why the problem occurred: The col and margin both class are removed in below commit- https://github.com/odoo/odoo/commit/22c47fb003c7cfaccb732de5b8ea7277b9dade54 - Fix: We re-induced col and margin class task-3442343 Forward-Port-Of: odoo/odoo#131533
Original PR description
- Issue-:
Broken the portal view because of totals.
- Why the problem occurred:
The col and margin both class are removed in below commit- https://github.com/odoo/odoo/commit/22c47fb003c7cfaccb732de5b8ea7277b9dade54
- Fix:
We re-induced col and margin class
task-3442343
Forward-Port-Of: odoo/odoo#131533Since commit [1], which converted the wysiwyg to Owl, trying to customize the Google Map API key causes a traceback. Steps to reproduce: - In edit mode, go to the "Theme" tab. - Click on the Google Map "Custom Key" button. => A traceback appears. It happens because when getting the parent with the `this.getParent()` call, the parent is now a `WysiwygAdapterComponent` component and so, calling the `trigger_up` function on it does not work anymore. This commit triggers the `gmap_api_k
Original PR description
Since commit [1], which converted the wysiwyg to Owl, trying to customize the Google Map API key causes a traceback. Steps to reproduce: - In edit mode, go to the "Theme" tab. - Click on the Google Map "Custom Key" button. => A traceback appears. It happens because when getting the parent with the `this.getParent()` call, the parent is now a `WysiwygAdapterComponent` component and so, calling the `trigger_up` function on it does not work anymore. This commit triggers the `gmap_api_key_request` event in a way that is compatible with the Owl component. [1]: https://github.com/odoo/odoo/commit/76d4f9811b756f0e57b0a33dbba534c900c7fe15 opw-3489976 Forward-Port-Of: odoo/odoo#134860
Since 0eff29409dd24af84fea29a885128d0a817991a9, the behavior was unpredictable when clicking on multiple companies before a reload. This simplifies the implementation and the behavior: * the behavior is always the same even if there were already multiple companies selected: if one wants to add new companies they should use the check box instead. * there is no more confusion due to the storage of the symetrical difference when toggling multiple companies and their children before the reload.
Original PR description
Since 0eff29409dd24af84fea29a885128d0a817991a9, the behavior was unpredictable when clicking on multiple companies before a reload. This simplifies the implementation and the behavior: * the behavior is always the same even if there were already multiple companies selected: if one wants to add new companies they should use the check box instead. * there is no more confusion due to the storage of the symetrical difference when toggling multiple companies and their children before the reload. Forward-Port-Of: odoo/odoo#133647
For model_terms translated fields if a translation for a lang(fr_FR) has never been defined before this commit when update translations for both en_US and fr_FR, the new translation for fr_FR cannot be saved. after this commit new translations can be correctly saved when en_US and fr_FR are updated at the same time. 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 an
Original PR description
For model_terms translated fields if a translation for a lang(fr_FR) has never been defined before this commit when update translations for both en_US and fr_FR, the new translation for fr_FR cannot be saved. after this commit new translations can be correctly saved when en_US and fr_FR are updated at the same time. 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#132540
[FIX] auth_signup: False is different than NULL in SQL Step: - Setup one app free trial - Create user on a trial database - Go to the signup generated (token valid) - Signup/Reset password Actual result: Token is "false" Expected result: Token is False/Null/None Cause by #113753 opw-3482042 opw-3484705 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#133948
Original PR description
[FIX] auth_signup: False is different than NULL in SQL Step: - Setup one app free trial - Create user on a trial database - Go to the signup generated (token valid) - Signup/Reset password Actual result: Token is "false" Expected result: Token is False/Null/None Cause by #113753 opw-3482042 opw-3484705 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#133948
Steps to reproduce: - Set "To Check" for a bill in the Bill list view - go back to the dashboard Issue: There won't be the "To Check" shortcut as it was the case in 15.0 opw-3455414 Forward-Port-Of: odoo/odoo#133296
Original PR description
Steps to reproduce: - Set "To Check" for a bill in the Bill list view - go back to the dashboard Issue: There won't be the "To Check" shortcut as it was the case in 15.0 opw-3455414 Forward-Port-Of: odoo/odoo#133296
The aim of this commit is to prevent reconciliation with credit note to be triggered when a reversed move is reset to draft Context: reconciliation between credit note and invoice (same for vendor bill) Previous to this commit: Post invoice Create and post credit note Reset to draft both the invoice and the credit note Post (confirm) again the credit note -> User error due to attempt of reconciliation between credit note and draft invoice After this commit: The credit note is poste
Original PR description
The aim of this commit is to prevent reconciliation with credit note to be triggered when a reversed move is reset to draft Context: reconciliation between credit note and invoice (same for vendor bill) Previous to this commit: Post invoice Create and post credit note Reset to draft both the invoice and the credit note Post (confirm) again the credit note -> User error due to attempt of reconciliation between credit note and draft invoice After this commit: The credit note is posted but not reconciled when the original move is in draft task-3492197 Forward-Port-Of: odoo/odoo#134336
During this pr (https://github.com/odoo/odoo/pull/121413), we have made a few css changes on the din5008 format, some of them needed to be revert because they broke the layout. task: 3495712 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#134907 Forward-Port-Of: odoo/odoo#134775
Original PR description
During this pr (https://github.com/odoo/odoo/pull/121413), we have made a few css changes on the din5008 format, some of them needed to be revert because they broke the layout. task: 3495712 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#134907 Forward-Port-Of: odoo/odoo#134775
in the following commit https://github.com/odoo/odoo/commit/f8654b3501aca6e5d77ced5f73cb351c61684cd2 , we fixed the feature to mass export edi documents from the journal entries list view. However, we forgot to include the Spain localization edi documents to be included in the export. task-3477482 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#132936
Original PR description
in the following commit https://github.com/odoo/odoo/commit/f8654b3501aca6e5d77ced5f73cb351c61684cd2 , we fixed the feature to mass export edi documents from the journal entries list view. However, we forgot to include the Spain localization edi documents to be included in the export. task-3477482 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#132936
Before: when attempting to print an invoice, the downloaded file had the generic name "Invoice". Now: downloaded files have the correct invoice number as names. task-3477659 Forward-Port-Of: odoo/odoo#134148
Original PR description
Before: when attempting to print an invoice, the downloaded file had the generic name "Invoice". Now: downloaded files have the correct invoice number as names. task-3477659 Forward-Port-Of: odoo/odoo#134148
Replace commas by semicolons so the linter stops complaining. opw-3235288 Forward-Port-Of: odoo/odoo#134429 Forward-Port-Of: odoo/odoo#134334
Original PR description
Replace commas by semicolons so the linter stops complaining. opw-3235288 Forward-Port-Of: odoo/odoo#134429 Forward-Port-Of: odoo/odoo#134334
Have a form view with a view button. Make some changes in the form s.t. the create/write rpc will return an error. Before this commit, the "oh snap" dialog was displayed, providing 2 choices to the user: stay here (basically, close the error dialog and do nothing else) or discard (discard changes, and continue the flow). In this case, the flow is to do the "call_button" as we clicked on a view button. It means that if the user clicked on discard, we still call the method/action, even though the
Original PR description
Have a form view with a view button. Make some changes in the form s.t. the create/write rpc will return an error. Before this commit, the "oh snap" dialog was displayed, providing 2 choices to the…
Have a form view with a view button. Make some changes in the form s.t. the create/write rpc will return an error. Before this commit, the "oh snap" dialog was displayed, providing 2 choices to the user: stay here (basically, close the error dialog and do nothing else) or discard (discard changes, and continue the flow). In this case, the flow is to do the "call_button" as we clicked on a view button. It means that if the user clicked on discard, we still call the method/action, even though the record was invalid (and maybe not even existing if it was a new record). This can cause other issues afterwards. The "oh snap" dialog was designed for navigation flows (e.g. menu, breadcrumbs...), when the user tries to leave the form view. It doesn't fit very well with flows involving the current record that couldn't been saved. This commit thus prevents the "oh snap" dialog from being displayed if the save preceeding a call_button fails. The error returned by the save is simply displayed in a basic dialog that can only be closed. opw~3395109 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#134932 Forward-Port-Of: odoo/odoo#134783
In 16.1 and before, when you used the Send & Print, you could manually remove the attachments when using the Send by Email. Even though the use case is weird (sending an invoice by email without attaching the document), we have feedback of user actively using that option before. task: 3476700 opw: 3378840 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#134970 Forward-Port-Of: odoo/odoo#132869
Original PR description
In 16.1 and before, when you used the Send & Print, you could manually remove the attachments when using the Send by Email. Even though the use case is weird (sending an invoice by email without attaching the document), we have feedback of user actively using that option before. task: 3476700 opw: 3378840 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#134970 Forward-Port-Of: odoo/odoo#132869
before this commit, the uninstall and upgrade option is not shown in the kanban. introduced in: https://github.com/odoo/odoo/commit/5b68871097df5e7a13966dee4c650d1f34f9e7c1 * open apps kanban * click on kanban menu(3 dots) of installed app * upgrade and uninstall button is not shown after this commit, the upgrade and uninstall button will be shown in the apps kanban menu depending on the state of the app --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.co
Original PR description
before this commit, the uninstall and upgrade option is not shown in the kanban. introduced in: https://github.com/odoo/odoo/commit/5b68871097df5e7a13966dee4c650d1f34f9e7c1 * open apps kanban * click on kanban menu(3 dots) of installed app * upgrade and uninstall button is not shown after this commit, the upgrade and uninstall button will be shown in the apps kanban menu depending on the state of the app --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#134990 Forward-Port-Of: odoo/odoo#134963
Because why not? We often need to re-render the user interface from python, but limited to call a browser reload (redirect to current URL). With this simple client action tag `soft_reload` - we can quickly reload the UI, without a hard refresh. An example use case can be seen in the next commit - which will be removed if this PR is accepted Forward-Port-Of: odoo/odoo#134813 Forward-Port-Of: odoo/odoo#133643
Original PR description
Because why not? We often need to re-render the user interface from python, but limited to call a browser reload (redirect to current URL). With this simple client action tag `soft_reload` - we can quickly reload the UI, without a hard refresh. An example use case can be seen in the next commit - which will be removed if this PR is accepted Forward-Port-Of: odoo/odoo#134813 Forward-Port-Of: odoo/odoo#133643
Steps to reproduce: - Install `calendar` module - With demo user, go to calendar and create a new event - With admin user, go to the calendar and try to edit the event Issue: Admin can't edit the event. Cause: Only allowing the user who created the event or who is in the attendees list to edit it. Solution: Allow to edit the event if user is admin (or created the event or is in attendees list). opw-3185743 Forward-Port-Of: odoo/odoo#133504
Original PR description
Steps to reproduce: - Install `calendar` module - With demo user, go to calendar and create a new event - With admin user, go to the calendar and try to edit the event Issue: Admin can't edit the event. Cause: Only allowing the user who created the event or who is in the attendees list to edit it. Solution: Allow to edit the event if user is admin (or created the event or is in attendees list). opw-3185743 Forward-Port-Of: odoo/odoo#133504
During the owl refactoring (https://github.com/odoo/enterprise/commit/d2d4f5e04042eb420f0f4c566269d1148baf84f7) a rebase broke the display of the cash basis filter on the pdf header, since the logic of filters is in python the template needed to be moved. task: 3482310 Forward-Port-Of: odoo/enterprise#46926
Original PR description
During the owl refactoring (https://github.com/odoo/enterprise/commit/d2d4f5e04042eb420f0f4c566269d1148baf84f7) a rebase broke the display of the cash basis filter on the pdf header, since the logic of filters is in python the template needed to be moved. task: 3482310 Forward-Port-Of: odoo/enterprise#46926
Step to reproduce: - Install account_asset module - Go to Accounting > Configuration > Accounting > Chart of Accounts - Open account 151000 Fixed Assets - In 'Automation' tab, set 'Automate Asset' to 'create in draft' and set a model to 'Asset Model' - Create a new BILL - Add a line (without selecting a product) with a label and a price - Validate the bill - Go to Accounting > Management > Assets - Open asset just created and check the chatter Issue: The link
Original PR description
Step to reproduce: - Install account_asset module - Go to Accounting > Configuration > Accounting > Chart of Accounts - Open account 151000 Fixed Assets - In 'Automation' tab, set 'Automate Asset' to 'create in draft' and set a model to 'Asset Model' - Create a new BILL - Add a line (without selecting a product) with a label and a price - Validate the bill - Go to Accounting > Management > Assets - Open asset just created and check the chatter Issue: The link is display in brut text. Cause: Escaping (using 'escape') the link who broke it. Solution: Use Markup to display the link correctly. opw-3453873 Forward-Port-Of: odoo/enterprise#45905
Step: Install WhatsApp app Create a template with header type of image/document now click on Submit For Approval Issue: _upload_demo_document() takes 2 positional arguments but 3 were given Forward-Port-Of: odoo/enterprise#47205
Original PR description
Step: Install WhatsApp app Create a template with header type of image/document now click on Submit For Approval Issue: _upload_demo_document() takes 2 positional arguments but 3 were given Forward-Port-Of: odoo/enterprise#47205
Before this change, we considered that a resource booked in an appointment type could be booked in an other at the same time. Now, we consider all bookings - of other appointment types too - when evaluating whether a resource is available. Task-3460526 Forward-Port-Of: odoo/enterprise#45577
Original PR description
Before this change, we considered that a resource booked in an appointment type could be booked in an other at the same time. Now, we consider all bookings - of other appointment types too - when evaluating whether a resource is available. Task-3460526 Forward-Port-Of: odoo/enterprise#45577
- Fix IRAS Audit File error generation due to method: _general_ledger_query_values() not present anymore - Adding the source document on journal items that involves exchange gain/loss account. The source of document should be coming from the invoice/bill that registers the payment 2921938 I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr) Forward-Port-Of: odoo/enterprise#47252 Forward-Port-Of: odoo/enterprise#37383
Original PR description
- Fix IRAS Audit File error generation due to method: _general_ledger_query_values() not present anymore - Adding the source document on journal items that involves exchange gain/loss account. The source of document should be coming from the invoice/bill that registers the payment 2921938 I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr) Forward-Port-Of: odoo/enterprise#47252 Forward-Port-Of: odoo/enterprise#37383
The format changed in 2023. Most values were already changed, but the version was not. But we also put the values of the company in the right field now. We don't remove them from the 'DatenLieferant', as some people could rely on it, and it does nothing when exporting it by hand. task-3486730 Forward-Port-Of: odoo/enterprise#47181 Forward-Port-Of: odoo/enterprise#46605
Original PR description
The format changed in 2023. Most values were already changed, but the version was not. But we also put the values of the company in the right field now. We don't remove them from the 'DatenLieferant', as some people could rely on it, and it does nothing when exporting it by hand. task-3486730 Forward-Port-Of: odoo/enterprise#47181 Forward-Port-Of: odoo/enterprise#46605
Before, in BTInterface.py we were using gatt.DeviceManager.run function which was calling GObject.MainLoop() function which was deprecated and was provoking a warning in the logs. This PR overrides the gatt.DeviceManager.run function to fix the deprecation warning and remove it from the logs. [task-3081272](https://www.odoo.com/web#id=3081272&cids=1&menu_id=4720&action=333&active_id=1428&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#31739
Original PR description
Before, in BTInterface.py we were using gatt.DeviceManager.run function which was calling GObject.MainLoop() function which was deprecated and was provoking a warning in the logs. This PR overrides the gatt.DeviceManager.run function to fix the deprecation warning and remove it from the logs. [task-3081272](https://www.odoo.com/web#id=3081272&cids=1&menu_id=4720&action=333&active_id=1428&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#31739
The unrealized currencies gain& loss report excludes the entries posted on a bank & cash journal. Probably because being liquidity transactions, they are considered realized. Rather than excluding purely and simply the journal entries posted on the bank & cash journals, we will now rely on the currency on the account(s). task: 3489749 Forward-Port-Of: odoo/enterprise#47141 Forward-Port-Of: odoo/enterprise#46696
Original PR description
The unrealized currencies gain& loss report excludes the entries posted on a bank & cash journal. Probably because being liquidity transactions, they are considered realized. Rather than excluding purely and simply the journal entries posted on the bank & cash journals, we will now rely on the currency on the account(s). task: 3489749 Forward-Port-Of: odoo/enterprise#47141 Forward-Port-Of: odoo/enterprise#46696
Changes 'JRNL' to 'Journal' in partner ledger report and 'Totals' to 'Total' in deferred reports. Forward-Port-Of: odoo/enterprise#46672
Original PR description
Changes 'JRNL' to 'Journal' in partner ledger report and 'Totals' to 'Total' in deferred reports. Forward-Port-Of: odoo/enterprise#46672
Slightly change the color of the 'line_level_0' background color. Forward-Port-Of: odoo/enterprise#46676
Original PR description
Slightly change the color of the 'line_level_0' background color. Forward-Port-Of: odoo/enterprise#46676
In order to fix a behavior in the company selector, the API of the company service has been simplified. Forward-Port-Of: odoo/enterprise#47021
Original PR description
In order to fix a behavior in the company selector, the API of the company service has been simplified. Forward-Port-Of: odoo/enterprise#47021
The fix introduced in https://github.com/odoo/enterprise/pull/44538 is missing a sudo, which prevents portal users from accessing the portal page of a project with shared documents. This PR fixes this issue. Forward-Port-Of: odoo/enterprise#47220
Original PR description
The fix introduced in https://github.com/odoo/enterprise/pull/44538 is missing a sudo, which prevents portal users from accessing the portal page of a project with shared documents. This PR fixes this issue. Forward-Port-Of: odoo/enterprise#47220
Currently, when a journal is created during import, we just use the journal name as the code. However, that gets truncated to 5 characters on create, which can conflict with existing journals. The import should be as flexible as possible, as it's better to let users import and fix things after the import rather than debug the import file. If there is a journal with a shortcode that matches the truncated name of the new journal, just use the existing journal See also odoo/odoo#132715 Forw
Original PR description
Currently, when a journal is created during import, we just use the journal name as the code. However, that gets truncated to 5 characters on create, which can conflict with existing journals. The import should be as flexible as possible, as it's better to let users import and fix things after the import rather than debug the import file. If there is a journal with a shortcode that matches the truncated name of the new journal, just use the existing journal See also odoo/odoo#132715 Forward-Port-Of: odoo/enterprise#47173 Forward-Port-Of: odoo/enterprise#46101