Daily updates from Odoo
Navigate
Branch
Wednesday, October 23, 2019
35 changes
Enhancements to existing features
This update lets Odoo screens specify which file types should be accepted when users upload files. It improves the upload experience by guiding users toward the right format, such as XML files, and reducing accidental wrong-file selections.
Original PR description
Description of the issue/feature this PR addresses:
Offer users a better experince with specific file inputs.
Current behavior before PR:
It is not possible to adjust the accept attribute of the input.
Desired behavior after PR is merged:
`<field name="file_xml" widget="binary" filename="filename_xml" options="{'accept': 'text/xml'}" />`
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prTheme modules can now correctly keep their customization visibility setting during installation and updates. This prevents warning messages during setup and avoids update failures, making theme maintenance more reliable.
Original PR description
Before this commit, having a `customize_show` on an ir.ui.view record in a theme module would be ignored when creating the theme.ir.ui.view as the field would not exists. Actually it would log a warning on create (module install) and raise a traceback on module update (theme update).
Asset creation can now use the quantity on an accounting line to generate multiple assets instead of only one. This helps businesses record and manage purchases of several identical assets more accurately and with less manual work.
Helpdesk SLA policies can now be targeted by ticket tags in addition to ticket type. This helps teams apply the right service commitments to more specific categories of requests, while leaving policies without tags applicable to all tickets as before.
Original PR description
Purpose ======= Tags are useful to flag the various types of tickets handled by a given helpdesk team. It would be a great help to apply the SLA Policies based on this information. Specifications =========== Add a "Ticket Tags" field below the "Ticket Type" on the SLA Policies form view. Do not make it mandatory. If no tags are specified, the SLA should be applied on all tickets. You should be able to select one or more Helpdesk tags Helpdesk tags comes as an additional criterion a ticket have to meet to have the SLA applied. e.g. for an SLA with ticket_type_id=Foo and tag_ids=Bar,Bou The ticket must have the same ticket type AND at least both tags.
This update appears to adjust asset generation so records can be created based on quantity, helping businesses manage multiple assets more accurately from a single transaction. The limited commit detail suggests a focused functional change with moderate business impact for accounting asset workflows.
Helpdesk SLA policies can now be defined using minutes in addition to days and hours. This gives teams more precise control over response and resolution targets, especially for urgent support commitments.
Original PR description
Prior to this commit, the SLA policies were defined in number of days and/or hours. This commit adds support for minutes as well. TaskID: 2077690
Resolved issues and error corrections
Corrected how the Engineering Change Order button is added to product pages. This prevents Odoo Studio from crashing when users edit the product form, improving reliability for product maintenance workflows.
Original PR description
The stat button for the action `mrp_eco_action_product_tmpl` was improperly injected in the product template views, causing studio to crash when editing the product template form view. TaskID: 2052317
Features or functions removed from Odoo
This change keeps a single chart of accounts for the China localization in Odoo Master and removes the separate standard China accounting module. This reduces maintenance effort and helps ensure future updates focus on one consistent accounting setup.
Original PR description
Hi, Desired behavior after PR is merged: 1、 After discussion with Jerry , Laura , eg. We decided keey only one CoA for Odoo master version. So i modiffed the addons/l10n_cn/data/account_tax_group_data.xml to rm some tax group. 2、 Deleted the addons/l10n_cn_standard module @lap-odoo @mart-e -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
An unused stock transfer wizard file was removed because it was no longer imported or active. This cleans up leftover code in the stock module and reduces maintenance overhead without changing normal user workflows.
Original PR description
related to rev eddc695ac35b01bc4414223a724937a60db2dda8 the file is not imported but still present
Code cleanup and technical improvements
This update cleans up older email-related code and prepares the mail system for future speed improvements. It should have little direct impact on day-to-day users, but helps make email handling more reliable and easier to improve over time.
This update tidies the internal stock picking completion process and ensures it is used through the standard validation flow. It helps reduce maintenance risk across inventory, manufacturing, purchasing, sales, delivery, and point of sale operations without changing day-to-day user behavior.
This change restructures how stock transfers are marked as done, making that process internal to reduce unintended use by related apps. It helps keep delivery, marketplace, helpdesk, field service, and quality workflows aligned while preserving expected behavior through updated tests.
Miscellaneous changes
Task: https://www.odoo.com/web#id=2092346&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.2b70144873cc95ceb76208a3daa03c33 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#39256
Original PR description
Task: https://www.odoo.com/web#id=2092346&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.2b70144873cc95ceb76208a3daa03c33 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#39256
When a BoM is using a component with a quantity required set to 0, tracebacks were occuring when computing the available quantities for the kit. fixes #38807 Forward-Port-Of: odoo/odoo#38890
Original PR description
When a BoM is using a component with a quantity required set to 0, tracebacks were occuring when computing the available quantities for the kit. fixes #38807 Forward-Port-Of: odoo/odoo#38890
Before this commit, when clicking inside a snippet which is already enabled, it was disabled then re-enabled... which had the side effect of calling onBlur/onFocus methods. This can be a problem with some onFocus/onBlur implementation relying on the old behavior. Forward-Port-Of: odoo/odoo#39250
Original PR description
Before this commit, when clicking inside a snippet which is already enabled, it was disabled then re-enabled... which had the side effect of calling onBlur/onFocus methods. This can be a problem with some onFocus/onBlur implementation relying on the old behavior. Forward-Port-Of: odoo/odoo#39250
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#37043
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#37043
The goal is to improve the project's overview: 1/ Switch tooltips 2/ Increase tags size TaskID: 2086664 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#38804
Original PR description
The goal is to improve the project's overview:
1/ Switch tooltips
2/ Increase tags size
TaskID: 2086664
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#38804Description of the issue/feature this PR addresses: Fixes https://github.com/odoo/odoo/issues/38992 Current behavior before PR: See https://github.com/odoo/odoo/issues/38992 Desired behavior after PR is merged: This commit adds a default value for non-stored compute field according to new ORM on v13 and only compute when there is production_id. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39071
Original PR description
Description of the issue/feature this PR addresses: Fixes https://github.com/odoo/odoo/issues/38992 Current behavior before PR: See https://github.com/odoo/odoo/issues/38992 Desired behavior after PR is merged: This commit adds a default value for non-stored compute field according to new ORM on v13 and only compute when there is production_id. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39071
The nightly clickall runbot fail due to a crash of the underlying chrome browser used to run the test suite. The problem is related to the resources the browser is using. We leverage the problem by starting one dedicated browser per app. Forward-Port-Of: odoo/odoo#39135
Original PR description
The nightly clickall runbot fail due to a crash of the underlying chrome browser used to run the test suite. The problem is related to the resources the browser is using. We leverage the problem by starting one dedicated browser per app. Forward-Port-Of: odoo/odoo#39135
opw-[2089868](https://www.odoo.com/web?debug#id=2089868&model=project.task&view_type=form&menu_id=5200) Forward-Port-Of: odoo/odoo#39215 Forward-Port-Of: odoo/odoo#39203
Original PR description
opw-[2089868](https://www.odoo.com/web?debug#id=2089868&model=project.task&view_type=form&menu_id=5200) Forward-Port-Of: odoo/odoo#39215 Forward-Port-Of: odoo/odoo#39203
Since saas-12.3, deferred actions use native promises. This has the annoying side-effect of force-deferring promises even if they are resolved at once... and we relied on the opposite behavior for some call made in _setActive or option methods. In master, we should review the async logic of snippet options. Right now we will rely on the fact those promises are resolved at once but that we need to avoid for their "async part" anyway. The _setActive method and the option methods are thus
Original PR description
Since saas-12.3, deferred actions use native promises. This has the annoying side-effect of force-deferring promises even if they are resolved at once... and we relied on the opposite behavior for some call made in _setActive or option methods. In master, we should review the async logic of snippet options. Right now we will rely on the fact those promises are resolved at once but that we need to avoid for their "async part" anyway. The _setActive method and the option methods are thus still working synchronously in stable, despite the new force-deferring promises. Also, with old promises, when we waited for the resolution of multiple deferred, the resolve handler received the multiple results as individual arguments. Now it receives all the results in an array as a single argument. The resolution of action demands had to be adapted. Forward-Port-Of: odoo/odoo#39134 Forward-Port-Of: odoo/odoo#39116
The default `compute_sudo=True` makes sense for recomputing stored fields that are indirectly related to a business operation. This ensures that the recomputation of the field does not break an operation that is not aware of the fields to recompute. However, computing non-stored fields in superuser mode is usually not necessary. It even leads to unexpected values: counting a partner's sales orders does not give the same result in superuser mode as in normal mode. That is why non-stor
Original PR description
The default `compute_sudo=True` makes sense for recomputing stored fields that are indirectly related to a business operation. This ensures that the recomputation of the field does not break an operation that is not aware of the fields to recompute. However, computing non-stored fields in superuser mode is usually not necessary. It even leads to unexpected values: counting a partner's sales orders does not give the same result in superuser mode as in normal mode. That is why non-stored fields are not computed in superuser mode by default. Forward-Port-Of: odoo/odoo#38805
The basic ORM methods should not silently discard unknown fields, as they may be a sign of broken code. Forward-Port-Of: odoo/odoo#37094
Original PR description
The basic ORM methods should not silently discard unknown fields, as they may be a sign of broken code. Forward-Port-Of: odoo/odoo#37094
Was comparing b'0x02' and '0x02' Forward-Port-Of: odoo/odoo#38407
Original PR description
Was comparing b'0x02' and '0x02' Forward-Port-Of: odoo/odoo#38407
This commits fixes user duplication. Suppose there is a monetary field, with a currency_field that is a related. When going through model's _create, we do: `if field.type in ('one2many', 'many2many'): self.env.cache.set(record, field, ())` knowing that thse values are false, with the intent to clean them later: `for record, field in cachetoclear` However, when setting the scalar values, we go through: `accessing cache_value = field.convert_to_cache(value, record)` In the case of t
Original PR description
This commits fixes user duplication. Suppose there is a monetary field, with a currency_field that is a related. When going through model's _create, we do: `if field.type in ('one2many',…
This commits fixes user duplication.
Suppose there is a monetary field, with a currency_field that is a related.
When going through model's _create, we do:
`if field.type in ('one2many', 'many2many'):
self.env.cache.set(record, field, ())`
knowing that thse values are false, with the intent to clean them later:
`for record, field in cachetoclear`
However, when setting the scalar values, we go through:
`accessing cache_value = field.convert_to_cache(value, record)`
In the case of the monetary field, this depends on another field value
(the currency_field). If it is a related, we can access its value.
However, at this point, if we check any access rights, we might use the value
of a relational in cache for which the value is incorrectly set to False.
In the case of the user, this is what happens: it inherits its currency_id
from partner, as well as its debit_limit which depends on it.
When the access if checked, company_ids is set to False in cache.
So when going through the rule 'user rule', which checks that the company_ids
intersects with the env.companies.ids, the result is always False.
In some way this is essentially hiding the problem, but the true fix is
probably not feasible in stable.
opw 2086661
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#38818There are two lines: 14 - Bénéfice (Perte) reporté(e) One in 'Bilan' and the other in 'Compte de résultats'. To be coherent, the latter's formula needs to be: balance = BE_9906.balance + BE_791.balance - BE_691_2.balance i.e. subtract the total of the 691 section. opw 2082071 Forward-Port-Of: odoo/enterprise#6244 Forward-Port-Of: odoo/enterprise#6063
Original PR description
There are two lines: 14 - Bénéfice (Perte) reporté(e) One in 'Bilan' and the other in 'Compte de résultats'. To be coherent, the latter's formula needs to be: balance = BE_9906.balance + BE_791.balance - BE_691_2.balance i.e. subtract the total of the 691 section. opw 2082071 Forward-Port-Of: odoo/enterprise#6244 Forward-Port-Of: odoo/enterprise#6063
This commit aims at reducing the number of chatter messages when adjusting the quantity of a product required for a field service task. Before, each time the quantity of a product was modified, a message was logged in the chatter. Now it only logs once the product is initially added. TaskID: 2088929 Forward-Port-Of: odoo/enterprise#6230
Original PR description
This commit aims at reducing the number of chatter messages when adjusting the quantity of a product required for a field service task. Before, each time the quantity of a product was modified, a message was logged in the chatter. Now it only logs once the product is initially added. TaskID: 2088929 Forward-Port-Of: odoo/enterprise#6230
In the next case: 1. Create a company (Company by default) for Mexico 2. Create a vendor bill, with tax 16% 3. Create a new company, also for Mexico 4. Try to get the DIOT with the second company This returns the next traceback: ``` The requested operation ("read" on "Tax" (account.tax)) was rejected because of the following rules: - Tax multi-company Note: this might be a multi-company issue. (Records: IVA(16%) COMPRAS (id=10), User: Mitchell Admin (id=2)) ``` The error is
Original PR description
In the next case:
1. Create a company (Company by default) for Mexico
2. Create a vendor bill, with tax 16%
3. Create a new company, also for Mexico
4. Try to get the DIOT with the second company
This returns the next traceback:
```
The requested operation ("read" on "Tax" (account.tax)) was rejected
because of the following rules:
- Tax multi-company
Note: this might be a multi-company issue.
(Records: IVA(16%) COMPRAS (id=10), User: Mitchell Admin (id=2))
```
The error is because of search all the ``account.tax.repartition.line``,
with the tags for DIOT report, but not search only the company records.
Now the domain was improved to get only the records with the same user
company (The DIOT report do not have multicompany options)
OPW #2085147
Forward-Port-Of: odoo/enterprise#6359It make non sense to have gantt view for allocations. Forward-Port-Of: odoo/enterprise#6362
Original PR description
It make non sense to have gantt view for allocations. Forward-Port-Of: odoo/enterprise#6362
The datev export format of the `l10n_de_reports` module makes use of the `aml_only` context key. By using this context key, it is expected that a list of AML ids is returned by `_get_lines`. We add back the support for this context key, since post-filtering the lines in `l10n_de_reports` is much more processing. opw-2090156 opw-2089209 Forward-Port-Of: odoo/enterprise#6343
Original PR description
The datev export format of the `l10n_de_reports` module makes use of the `aml_only` context key. By using this context key, it is expected that a list of AML ids is returned by `_get_lines`. We add back the support for this context key, since post-filtering the lines in `l10n_de_reports` is much more processing. opw-2090156 opw-2089209 Forward-Port-Of: odoo/enterprise#6343
Task: https://www.odoo.com/web#id=2069038&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.f3b0c84b0ab87c69495f9ea7ba5497b9 Description: Previously only SLA policies with exactly equal priority were being applied on a ticket. Hence Changed the behavior to apply all the SLA policies having equal or lower minimum priority than on the ticket. Forward-Port-Of: odoo/enterprise#6055
Original PR description
Task: https://www.odoo.com/web#id=2069038&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.f3b0c84b0ab87c69495f9ea7ba5497b9 Description: Previously only SLA policies with exactly equal priority were being applied on a ticket. Hence Changed the behavior to apply all the SLA policies having equal or lower minimum priority than on the ticket. Forward-Port-Of: odoo/enterprise#6055
- Go to Quality > Quality Control > Quality Alerts - Click on create, add a title => a sequence is added to the name - Go the the kanban view, use the 'Quick add' option => the sequence is not added to the name This is because the 'Quick add' fills in the nale, so the sequence is not added automatically. opw-2082782 Forward-Port-Of: odoo/enterprise#6328
Original PR description
- Go to Quality > Quality Control > Quality Alerts - Click on create, add a title => a sequence is added to the name - Go the the kanban view, use the 'Quick add' option => the sequence is not added to the name This is because the 'Quick add' fills in the nale, so the sequence is not added automatically. opw-2082782 Forward-Port-Of: odoo/enterprise#6328
Matching pull request for odoo/odoo#38805. Forward-Port-Of: odoo/enterprise#6320
Original PR description
Matching pull request for odoo/odoo#38805. Forward-Port-Of: odoo/enterprise#6320
Create an object that will, once in a x2m, display a form view in a modal i.e. Create an expense with an attachment Create an expense report with that expense line, click on the line to display the expense in a form-modal Before this commit, the attachment is displayed but its size is too big After this commit the size is reduced, that way, fields of the modal are usable In either case, the preview container is resizable OPW 2083510 Forward-Port-Of: odoo/enterprise#6333 Forward-
Original PR description
Create an object that will, once in a x2m, display a form view in a modal i.e. Create an expense with an attachment Create an expense report with that expense line, click on the line to display the expense in a form-modal Before this commit, the attachment is displayed but its size is too big After this commit the size is reduced, that way, fields of the modal are usable In either case, the preview container is resizable OPW 2083510 Forward-Port-Of: odoo/enterprise#6333 Forward-Port-Of: odoo/enterprise#6319
A rate request for fedex GROUND_HOME_DELIVERY will return nothing. It's due to different options that are not provided to easypost: - residential flag on addresses. - saturday_delivery on shipment. It's unfortunately impossible to add fields on delivery carrier in order to manage those options. However it could be imporved in master. opw-2081066 Forward-Port-Of: odoo/enterprise#6130 Forward-Port-Of: odoo/enterprise#6016
Original PR description
A rate request for fedex GROUND_HOME_DELIVERY will return nothing. It's due to different options that are not provided to easypost: - residential flag on addresses. - saturday_delivery on shipment. It's unfortunately impossible to add fields on delivery carrier in order to manage those options. However it could be imporved in master. opw-2081066 Forward-Port-Of: odoo/enterprise#6130 Forward-Port-Of: odoo/enterprise#6016