Search
Navigate
Branch
Tuesday, October 20, 2020
12 changes
New functionality added to Odoo
The Studio report editor now includes a resize handle for text editing areas. This gives users more control over their workspace when editing report content, making longer text easier to review and adjust.
Original PR description
Odoo Community PR: https://github.com/odoo/odoo/pull/60267 Jabberwock PR: https://github.com/odoo-dev/jabberwock/pull/446
Resolved issues and error corrections
This update improves how marketing automation campaigns handle the reset of the “Unicity based on” field. It helps ensure campaign settings stay consistent automatically, reducing the chance of incorrect configuration after related changes.
Original PR description
Task: https://www.odoo.com/web?#id=2300427&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720
Miscellaneous changes
Issue - Install 'Documents - Click 'Request' button - Try to submit the form without value in the due date selection Cause The due date type is undefined Solution Add the required argument to the selection to prevent a user from being able to send the form if he does not choose a type opw-2361875 Forward-Port-Of: odoo/enterprise#14194
Original PR description
Issue
- Install 'Documents
- Click 'Request' button
- Try to submit the form without value in the due date selection
Cause
The due date type is undefined
Solution
Add the required argument to the selection to prevent a user from being able to send the form if he does not choose a type
opw-2361875
Forward-Port-Of: odoo/enterprise#14194TLDR: wage_with_holidays and final_yearly_costs fields were dependent on each other STEPS: * Open a contract * Click Edit * Set some positive value on field holidays ("Paid Time Off") * Save and click Edit * Change field wage_with_holidays ("Wage update with holidays retenues") * Unfocus (e.g. click Tab button) BEFORE: The field is reset to original value AFTER: The field keeps its value, other fields are recomputed accordingly Forward-Port-Of: odoo/enterprise#14112
Original PR description
TLDR: wage_with_holidays and final_yearly_costs fields were dependent on each other
STEPS:
* Open a contract
* Click Edit
* Set some positive value on field holidays ("Paid Time Off")
* Save and click Edit
* Change field wage_with_holidays ("Wage update with holidays retenues")
* Unfocus (e.g. click Tab button)
BEFORE: The field is reset to original value
AFTER: The field keeps its value, other fields are recomputed accordingly
Forward-Port-Of: odoo/enterprise#14112Behavior prior to the fix: On a database with the BE localization installed, the Accounting Intrastat report installed, and a BE company configured, exporting the Intrastat report to XML with the "Partners with VAT Numbers Only" option checked includes all invoices, even the ones without a partner with VAT number. Behavior after the fix: The invoices (and refunds) associated with partners without a VAT number are correctly excluded. opw-2365940 Forward-Port-Of: odoo/enterprise#
Original PR description
Behavior prior to the fix: On a database with the BE localization installed, the Accounting Intrastat report installed, and a BE company configured, exporting the Intrastat report to XML with the "Partners with VAT Numbers Only" option checked includes all invoices, even the ones without a partner with VAT number. Behavior after the fix: The invoices (and refunds) associated with partners without a VAT number are correctly excluded. opw-2365940 Forward-Port-Of: odoo/enterprise#14213
Since commit a0e01a202de78ed0e5e904477e8de024c5af95c5, we rely on the origin sale order to fetch the shipping address (and to keep consistency the invoice-partner_id) of the original sale order of the subscription. This causes an issue when we change the partner_id of the subscription afterwards. This commit addresses the issue by only relying on the sale order information when its partner_id is the same as the subscription. Forward-Port-Of: odoo/enterprise#14215 Forward-Port-Of: odoo/e
Original PR description
Since commit a0e01a202de78ed0e5e904477e8de024c5af95c5, we rely on the origin sale order to fetch the shipping address (and to keep consistency the invoice-partner_id) of the original sale order of the subscription. This causes an issue when we change the partner_id of the subscription afterwards. This commit addresses the issue by only relying on the sale order information when its partner_id is the same as the subscription. Forward-Port-Of: odoo/enterprise#14215 Forward-Port-Of: odoo/enterprise#14190
Before this commit, a test didn't respect the account constraint of "You cannot have more than one account with "Current Year Earnings" as type". Forward-Port-Of: odoo/enterprise#14202
Original PR description
Before this commit, a test didn't respect the account constraint of "You cannot have more than one account with "Current Year Earnings" as type". Forward-Port-Of: odoo/enterprise#14202
TLDR: mod 347 in spanish accounting cannot be applied for intracomunitario bills, so hide the field to don't confuse users STEPS: * Install Spanish accounting * Add a supplier with Regimen intracomunitario as Fiscal position. * Create a vendor bill and check the tab AEAT BEFORE: it shows field "Regular operation for the model 347", but intracommunitary operations shouldn't appear here as they should be on the model 349. AFTER: the field is hidden EXPLANATION: from l10n_es_rep
Original PR description
TLDR: mod 347 in spanish accounting cannot be applied for intracomunitario bills, so hide the field to don't confuse users STEPS: * Install Spanish accounting * Add a supplier with Regimen intracomunitario as Fiscal position. * Create a vendor bill and check the tab AEAT BEFORE: it shows field "Regular operation for the model 347", but intracommunitary operations shouldn't appear here as they should be on the model 349. AFTER: the field is hidden EXPLANATION: from l10n_es_reports_mod349_available field description: "True if and only if the invoice must be reported on mod 349 report, i.e. it concerns an intracommunitary operation". So we can just use this field and don't need for new field for mod 347 (i.e. l10n_es_reports_mod347_available) Forward-Port-Of: odoo/enterprise#14207 Forward-Port-Of: odoo/enterprise#14191
The button text colors were forced to the default link color while that color should only be forced for links which are not buttons. Note: this fix will not impact existing mail templates thanks to transcoding. That's why it is possible to fix safely in stable versions. Related to https://github.com/odoo/odoo/pull/59963 Forward-Port-Of: odoo/enterprise#14178 Forward-Port-Of: odoo/enterprise#14056
Original PR description
The button text colors were forced to the default link color while that color should only be forced for links which are not buttons. Note: this fix will not impact existing mail templates thanks to transcoding. That's why it is possible to fix safely in stable versions. Related to https://github.com/odoo/odoo/pull/59963 Forward-Port-Of: odoo/enterprise#14178 Forward-Port-Of: odoo/enterprise#14056
Have a subscription template with 'Create Invoice' in 'send after successful payment' Have a customer DEMO with payment token set up (i.e. with stripe) Setup a subscription with such template and customer. Open the subscription Force the scheduled action 'Sale Subscription: generate recurring invoices and payments' Generated invoice for the subscription will be in draft, thus preventing auto-reconciling with the automated payment opw-2338989 Forward-Port-Of: odoo/enterprise#14029 F
Original PR description
Have a subscription template with 'Create Invoice' in 'send after successful payment' Have a customer DEMO with payment token set up (i.e. with stripe) Setup a subscription with such template and customer. Open the subscription Force the scheduled action 'Sale Subscription: generate recurring invoices and payments' Generated invoice for the subscription will be in draft, thus preventing auto-reconciling with the automated payment opw-2338989 Forward-Port-Of: odoo/enterprise#14029 Forward-Port-Of: odoo/enterprise#13986
The widget is intended for informative fields only, i.e. the fields do not need to be editable. It is not the case for the fields deadline and date_deadline. Forward-Port-Of: odoo/enterprise#14174
Original PR description
The widget is intended for informative fields only, i.e. the fields do not need to be editable. It is not the case for the fields deadline and date_deadline. Forward-Port-Of: odoo/enterprise#14174
Steps to reproduce the bug: - Install l10n_be_intrastat module - Let's consider a company C in Belgium and a vendor V in France - Let's consider a product P with weight and measurement (10kg for 1m3) - Create vendor bill VB for V - Create a line L with P, quantity=0.0 and set intrastat method on L - Set intrastat delivery in the tab "other info - Post VB - Go to the intrastat report for this period and export it in xml Bug: It was imposible to import the xml file with lines with
Original PR description
Steps to reproduce the bug: - Install l10n_be_intrastat module - Let's consider a company C in Belgium and a vendor V in France - Let's consider a product P with weight and measurement (10kg for 1m3) - Create vendor bill VB for V - Create a line L with P, quantity=0.0 and set intrastat method on L - Set intrastat delivery in the tab "other info - Post VB - Go to the intrastat report for this period and export it in xml Bug: It was imposible to import the xml file with lines with quantity = 0.0 PS: this use case is often met when the invoicing policy of a product is based on delivery Invoicing a PO with several products and partial deliveries can lead to invoiced lines with 0.0 as quantity opw:2352286 Forward-Port-Of: odoo/enterprise#14186