Daily updates from Odoo
Navigate
Branch
Tuesday, May 24, 2022
18 changes
Enhancements to existing features
This update adjusts internal VoIP dialing panel tests so they work with upcoming changes in the messaging app environment. It helps keep quality checks reliable during future platform updates, with no direct change for end users.
Original PR description
This PR prepares the ground for the one introducing the wowlEnv in the discuss app. Indeed, the start helper won't return widgets anymore. This means we need to adapt those tests to stop calling widget methods and rely on a more realistic behavior. The voip dialing panel tests have been adapted to ease the wowlEnv integration. task-2582313
The email marketing themes now use refreshed images for the redesigned event snippet. This keeps event mailings visually aligned with the new two-event layout and provides more appropriate default visuals across themes.
Original PR description
The event snippet in mass_mailing needed refreshing. What was a 3 column block for a single event is now a 2 column block for 2 events. This PR is for the images linked to that snippet in mass_mailing_themes community PR: https://github.com/odoo/odoo/pull/87059 task-2714386
This update simplifies internal automated tests by replacing an unnecessary test reference with a direct document reference. It helps reduce future development complexity for upcoming Discuss app changes, with no expected impact on day-to-day users.
Original PR description
*: account_invoice_extract, documents. The target returned by the mail's test utils start method is useless since it's almost the same thing than querying document. Let's remove it and replace it by document. This will reduce the diff in the PR introducing the new environment in the discuss app. task-2582313 community: https://github.com/odoo/odoo/pull/92077
The Documents spreadsheet component has been updated to a newer version. Charts can now adapt text color to their background, improving readability and making spreadsheet-based reports easier to view.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/b3c80809 [IMP] chart: dynamic font color based on the background color https://github.com/odoo/o-spreadsheet/commit/c7ba8297 [IMP] helpers: introduce color conversion helpers https://github.com/odoo/o-spreadsheet/commit/879d9844 [REF] overlay: compute coordinates directly top-left of the grid https://github.com/odoo/o-spreadsheet/commit/c60ebd2e [REF] sheet: remove start and end on headers
The department board in Appraisals now follows the refreshed visual style used in Recruitment. This creates a more consistent and polished experience for managers viewing department information.
Original PR description
The recruitment kanban view was redesigned and it looks good, so it was decided to implement the same design on the department kanban view. This commit adapts the hr_appraisal overwrite of this view. task-2849418
Resolved issues and error corrections
Fixes a crash that could happen when users tried to insert a pivot table from another spreadsheet sheet after reloading the page. This helps users continue working with spreadsheet reports reliably, even when some pivot data has not been loaded yet.
Original PR description
- Insert two pivots on a spreadsheet, one on the first sheet and one on the second - Then reload the page and try to insert the second pivot (which is not loaded) in the first sheet. => boom Task 2844664
Spreadsheet list formulas now recognize date and datetime fields as dates instead of plain text. This allows users to apply the expected date formatting and improves the accuracy and readability of spreadsheet reports.
Original PR description
.. and datetime. Currently, formulas `LIST` yield the server value of fields date and datetime, which are strings. As such, the o_spreadsheet lib will tag the cell with such content as a string; which prevents a proper formatting. To solve this, we now convert the server values to a number for values realted to date and datetime fields. Task 2857297
Code cleanup and technical improvements
SEPA direct debit payment settings are now calculated automatically instead of being stored separately. This makes it easier to support the feature across payment providers and avoids extra migration work during upgrades.
Original PR description
Computing the fields instead of storing them allows to implement the feature for each provider more easily, without needing a migration script. task-2841744 See also: - https://github.com/odoo/odoo/pull/91961 - https://github.com/odoo/upgrade/pull/3535
Miscellaneous changes
The design tab allows the customization of the separators' colors but this is currently broken because it gets overridden by the default style of the snippet, which has higher specificity. Community PR: https://github.com/odoo/odoo/pull/92150 Forward-Port-Of: odoo/enterprise#27711
Original PR description
The design tab allows the customization of the separators' colors but this is currently broken because it gets overridden by the default style of the snippet, which has higher specificity. Community PR: https://github.com/odoo/odoo/pull/92150 Forward-Port-Of: odoo/enterprise#27711
We don't need the DIAN fields when we create a debit/credit note, however it is mandatory when creating other invoices. Step to reproduce the issue: 1. Install Accounting, l10n_co and l10n_co_edi modules 2. Go to Accounting > Customers > Credit Notes and create one 3. Save then Confirm You will see that a pop-up is displayed to fill the "Resolucion DIAN" in the appropriate Journal. These fields are in fact not required for Credit/Debit Notes. Solution: The condition concerning the D
Original PR description
We don't need the DIAN fields when we create a debit/credit note, however it is mandatory when creating other invoices. Step to reproduce the issue: 1. Install Accounting, l10n_co and l10n_co_edi modules 2. Go to Accounting > Customers > Credit Notes and create one 3. Save then Confirm You will see that a pop-up is displayed to fill the "Resolucion DIAN" in the appropriate Journal. These fields are in fact not required for Credit/Debit Notes. Solution: The condition concerning the DIAN fields has been updated to ignore the case of Debit/Credit Notes. opw-2780428 Forward-Port-Of: odoo/enterprise#27056
Forward-Port-Of: odoo/enterprise#27609
Original PR description
Forward-Port-Of: odoo/enterprise#27609
There was a bug when using links to odoo menus, they didn't keep the breadcrumb. Odoo task 2819501 Forward-Port-Of: odoo/enterprise#27684 Forward-Port-Of: odoo/enterprise#27171
Original PR description
There was a bug when using links to odoo menus, they didn't keep the breadcrumb. Odoo task 2819501 Forward-Port-Of: odoo/enterprise#27684 Forward-Port-Of: odoo/enterprise#27171
Purpose ======= There is an exempted allowance for people using a bicycle to go to work. It should be declared on a specific payslip line + on the 281.10 declaration. TASKID: 2859694 Forward-Port-Of: odoo/enterprise#27593
Original PR description
Purpose ======= There is an exempted allowance for people using a bicycle to go to work. It should be declared on a specific payslip line + on the 281.10 declaration. TASKID: 2859694 Forward-Port-Of: odoo/enterprise#27593
Community PR: https://github.com/odoo/odoo/pull/88476 task-2821155 Forward-Port-Of: odoo/enterprise#26110
Original PR description
Community PR: https://github.com/odoo/odoo/pull/88476 task-2821155 Forward-Port-Of: odoo/enterprise#26110
Current behavior: When using Fiskaly in a company located in Deutschland, if you start a PoS session and try to pay the Customer Account of any customer. You get an unknown error Steps to reproduce: - Setup a company in Deutschland - Setup Fiskaly - Create a PoS with a payment method Identified by customer - Start PoS session go in the customer list and click on the cart logo - Try to validate the payment with any payment method - You get an error opw-2852603 Forward-Port-Of: odo
Original PR description
Current behavior: When using Fiskaly in a company located in Deutschland, if you start a PoS session and try to pay the Customer Account of any customer. You get an unknown error Steps to reproduce: - Setup a company in Deutschland - Setup Fiskaly - Create a PoS with a payment method Identified by customer - Start PoS session go in the customer list and click on the cart logo - Try to validate the payment with any payment method - You get an error opw-2852603 Forward-Port-Of: odoo/enterprise#27590
To reproduce ============ - on a online sync bank account - create a new journal (from type to create) when saving, a Validation Error is raised "You cannot have two journals associated with the same Online Account.". But when reloading the page (F5), we found out that the journal was added to the record. this bug can be reproduced an other way, by duplicating a journal that is linked to an online account, when checking this online account we find that it has two journals (the origi
Original PR description
To reproduce ============ - on a online sync bank account - create a new journal (from type to create) when saving, a Validation Error is raised "You cannot have two journals associated with the same…
To reproduce ============ - on a online sync bank account - create a new journal (from type to create) when saving, a Validation Error is raised "You cannot have two journals associated with the same Online Account.". But when reloading the page (F5), we found out that the journal was added to the record. this bug can be reproduced an other way, by duplicating a journal that is linked to an online account, when checking this online account we find that it has two journals (the original and the copy). Purpose ======= For the first case, the issue is caused by not setting a constraint on `account_online_account_id` in `account_journal` to check if the online account already has a journal or not. For the second case, an online account should have only one journal, so when duplicating a journal we must not copy the `account_online_account_id`. Specification ============= to solve the issue we add constraint on `account_online_account_id` and give it the attribute `copy=False` opw-2851216 Forward-Port-Of: odoo/enterprise#27702 Forward-Port-Of: odoo/enterprise#27673
Steps to reproduce: - In Marketing Automation - Campaigns - Select the demo campaign - Click on "Launch a test" - Select Brandon - Send the two mails from the campaign - Redo all the steps with a new Test but the same contact Issue: - The mails won't be sent Cause: - Since for this campaign we already sent these mails to Brandon, the mails will be considered as duplicate in: https://github.com/odoo/odoo/blob/11b7d89114178fa43545fb8e6224cb4ccbcf8ec1/addons/mail/wizard/mail_compose_
Original PR description
Steps to reproduce: - In Marketing Automation - Campaigns - Select the demo campaign - Click on "Launch a test" - Select Brandon - Send the two mails from the campaign - Redo all the steps with a new…
Steps to reproduce: - In Marketing Automation - Campaigns - Select the demo campaign - Click on "Launch a test" - Select Brandon - Send the two mails from the campaign - Redo all the steps with a new Test but the same contact Issue: - The mails won't be sent Cause: - Since for this campaign we already sent these mails to Brandon, the mails will be considered as duplicate in: https://github.com/odoo/odoo/blob/11b7d89114178fa43545fb8e6224cb4ccbcf8ec1/addons/mail/wizard/mail_compose_message.py#L499 Solution: We want to make sure that: - when doing a test, since there is only one linked partner to it, we can send as many mails as we launch tests. -> repeated tests make sense as we want to fine tune campaigns and maybe get feedback from actual customers - when launching the actual campaign, there are no duplicates (normal flow) but that eventual test-customers receive the final campaign In order to do that, we have to filter out from the seen_list https://github.com/odoo/odoo/blob/9b25a4b5a782146e8c0b41eb75ceea7ac3cd3abf/addons/mass_mailing/models/mailing.py#L736 the test-records. opw-2810298 Forward-Port-Of: odoo/enterprise#26624
Part of task# 2717840. Currently, fiscal country can be only changed in Accounting settings. Should be also available in Invoicing settings. Forward-Port-Of: odoo/enterprise#27326
Original PR description
Part of task# 2717840. Currently, fiscal country can be only changed in Accounting settings. Should be also available in Invoicing settings. Forward-Port-Of: odoo/enterprise#27326