Search
Navigate
Branch
Monday, March 7, 2022
12 changes
New functionality added to Odoo
This change adds a connection between employee contracts and timesheets so overtime can be calculated correctly in the timesheet grid. It improves accuracy when employees have one or more contracts during the period being reviewed.
Original PR description
WIP Adds a new module to link `hr_timesheet` and `hr_contract` together in order to correctly compute overtime in the grid view. TaskId-2652259
Enhancements to existing features
Project users can more easily create budget items from the budget shortcut and see how planned work compares with allocated hours in grouped task planning views. This helps managers spot workload or budget gaps faster and keep project planning aligned with available capacity.
Original PR description
The purpose of this commit, is to make generic improvements in project. In this commit, following changes are made: - enable creation of new budget items from 'budget' stat button - task gantt view, groupby project: add progress bar representing planned hours vs allocated hours Related Community PR: [odoo/odoo#82019](https://github.com/odoo/odoo/pull/82019) task-2692856 Co-authored-by: Krina Oza <kro@odoo.com>
Miscellaneous changes
…rt was displaying wrong data Before this commit, when the user opened the salesmen dashboard, the default date filter was set to 'last month' but the data from current month were displayed. When the filter was manually changed, the correct data were displayed. This commit esure that the data of the previous month are displayed when opening the dashboard with default value. Forward-Port-Of: odoo/enterprise#25056
Original PR description
…rt was displaying wrong data Before this commit, when the user opened the salesmen dashboard, the default date filter was set to 'last month' but the data from current month were displayed. When the filter was manually changed, the correct data were displayed. This commit esure that the data of the previous month are displayed when opening the dashboard with default value. Forward-Port-Of: odoo/enterprise#25056
Documents can now have access rules set directly on each file, making it easier to decide who can read or edit sensitive business documents. Files can either follow their workspace rules or use specific read, write, or owner-only access, giving teams clearer control over document sharing.
Original PR description
== From https://github.com/odoo/enterprise/pull/16787 == *documents_account,documents_hr,documents_product,documents_project, documents_sign,documents_spreadsheet This commit makes the following…
== From https://github.com/odoo/enterprise/pull/16787 == *documents_account,documents_hr,documents_product,documents_project, documents_sign,documents_spreadsheet This commit makes the following changes: - Add a more granular option to control the access to documents: the new `access` field allows a per-document control of the access rights. - `folder_id` is no longer a required field on `documents.document` and on `documents.share`. - Spreadsheets do not have default folders anymore and their `access` defaults as `owner`. Task ID: 2257514 Documents now have one more `access` option: `workspace`, this is the default value when creating/adding a file into a folder and signifies that the access rules are those of the folder. `readonly` and `write` now give their respective access regardless of the user's rights on the folder. This is to make sure that the statement `Anyone can read` or `Anyone can write` are actually correct. For old behaviour the user has to use the `workspace` access. This pr also speeds up some tests from documents, see commits
Prior to this commit: - Opening the project form / project update kanban views takes about 82 ms as account_analytic_id is used in a domain. After this commit: - Opening the project form / project update kanban views takes about 4 ms as the domain is on an indexed field. Related PRs: - odoo/odoo#85513 Forward-Port-Of: odoo/enterprise#24828
Original PR description
Prior to this commit: - Opening the project form / project update kanban views takes about 82 ms as account_analytic_id is used in a domain. After this commit: - Opening the project form / project update kanban views takes about 4 ms as the domain is on an indexed field. Related PRs: - odoo/odoo#85513 Forward-Port-Of: odoo/enterprise#24828
Steps to reproduce the bug: - Install `”delivery_usps”` - Go to any transfer > Additional info tab > add “USPS” as Carrier - Validate Bug: Traceback is triggered, since the V15.1, `move_lines` was renamed `move_ids` in `stock.picking` : https://github.com/odoo/odoo/pull/78732/files#diff-79cbc763115661182c02285c07320098510f5686700359ddee67443b4893dc30R321 opw-2777926 Forward-Port-Of: odoo/enterprise#24999 Forward-Port-Of: odoo/enterprise#24957
Original PR description
Steps to reproduce the bug: - Install `”delivery_usps”` - Go to any transfer > Additional info tab > add “USPS” as Carrier - Validate Bug: Traceback is triggered, since the V15.1, `move_lines` was renamed `move_ids` in `stock.picking` : https://github.com/odoo/odoo/pull/78732/files#diff-79cbc763115661182c02285c07320098510f5686700359ddee67443b4893dc30R321 opw-2777926 Forward-Port-Of: odoo/enterprise#24999 Forward-Port-Of: odoo/enterprise#24957
Before this commit there is no clean/easy way to override the domain. By adding it in a subdomain it can be easily overriden to expand/modify the domain to search in. To give a specific case: a fix was made for OPW `2739521` in which the domain was changed. We'd like to backport this for one of our customers in V14 but now have to take over the whole `_get_documents` function which is tricky & dangerous to miss future changes. See also https://github.com/odoo/enterprise/pull/24322 Forward-
Original PR description
Before this commit there is no clean/easy way to override the domain. By adding it in a subdomain it can be easily overriden to expand/modify the domain to search in. To give a specific case: a fix was made for OPW `2739521` in which the domain was changed. We'd like to backport this for one of our customers in V14 but now have to take over the whole `_get_documents` function which is tricky & dangerous to miss future changes. See also https://github.com/odoo/enterprise/pull/24322 Forward-Port-Of: odoo/enterprise#24646
#### Some useful context: In Mexico, there is only one fixed tax, and it appears very rarely. It is called the 'IEPS', and applies to fossil fuels, e.g., gasoline, diesel, fuel oil etc. A fixed amount is charged per liter / ton of fuel. (see https://www.infoautonomos.mx/obligaciones-fiscales/impuesto-especial-sobre-produccion-servicios-ieps/#IEPS_2020_Gasolina_y_diesel) In the CFDI, this fixed tax must be reported as follows: - `TipoFactor="Cuota"` - `TasaOCuota="(tax amount / base amo
Original PR description
#### Some useful context: In Mexico, there is only one fixed tax, and it appears very rarely. It is called the 'IEPS', and applies to fossil fuels, e.g., gasoline, diesel, fuel oil etc. A fixed…
#### Some useful context: In Mexico, there is only one fixed tax, and it appears very rarely. It is called the 'IEPS', and applies to fossil fuels, e.g., gasoline, diesel, fuel oil etc. A fixed amount is charged per liter / ton of fuel. (see https://www.infoautonomos.mx/obligaciones-fiscales/impuesto-especial-sobre-produccion-servicios-ieps/#IEPS_2020_Gasolina_y_diesel) In the CFDI, this fixed tax must be reported as follows: - `TipoFactor="Cuota"` - `TasaOCuota="(tax amount / base amount)"` - `Importe="(tax amount)"` The PAC performs a verification based on the `TipoFactor`, `TasaOCuota` and `Importe` fields. (see this table: https://sf.ezoiccdn.com/ezoimgfmt/www.cfdi.org.mx/wp-content/uploads/2020/02/Tabla-de-Valores-de-Tasa-o-Cuota-1024x670.png?ezimgfmt=ng:webp/ngcb1 found on https://www.cfdi.org.mx/catalogos-de-cfdi/tasa-o-cuota-de-impuestos/) If the `TipoFactor` field is "Tasa", the PAC checks that the `TasaOCuota` amount is one of several authorized values If the `TipoFactor` field is "Cuota", the PAC rather checks that the `TasaOCuota` amount is comprised between 0 and 43.770. In addition, the PAC checks that the `Importe` field is equal to the base amount times the `TasaOCuota` field, rounded either up or down. #### The issue: At the moment, instead of setting `TasaOCuota="(tax amount / base amount)"`, we set `TasaOCuota="(tax.amount / 100)"`. This is correct for percentage of price taxes, but not for fixed taxes. And this causes PAC validation errors as can be seen in this video, taken on a fresh v15 database: https://drive.google.com/file/d/1APaeAi--RUbGtPXgRcyG_1Fyy9xtmn34/view?usp=sharing This is also the issue in opw-2724805 #### The solution: Correctly set the `TasaOCuota` field when the `tax.l10n_mx_tax_type` is 'Cuota'. #### Does it work? Yes (tested on fresh local v15 db) - see this video: https://drive.google.com/file/d/1g276TBI8wB4MT4XNj63KvyeiyTGt6zc2/view?usp=sharing (also see this video where I try changing the computation in the code and seeing that it then doesn't pass the PAC's validation): https://drive.google.com/file/d/1PmGKBdg0GhwlTgcEG_ur2GlAR-8HYQ4u/view?usp=sharing Forward-Port-Of: odoo/enterprise#24451
PURPOSE Cleanup slots generation and availability computation to improve performances. SPECIFICATIONS Prefetch data used to compute availability in batch: meetings, work hours. Avoid fetching useless data depending on appointment type configuration. Improve coding style to reduce query counters. This merge contains several commits. Each improves part of the slots generation algorithm, notably to extract code preparing data, then improve it in various ways. This work as been do
Original PR description
PURPOSE Cleanup slots generation and availability computation to improve performances. SPECIFICATIONS Prefetch data used to compute availability in batch: meetings, work hours. Avoid fetching useless data depending on appointment type configuration. Improve coding style to reduce query counters. This merge contains several commits. Each improves part of the slots generation algorithm, notably to extract code preparing data, then improve it in various ways. This work as been done while keeping in mind master functional improvements currently under work as well as preparing a backport to 15.0. See individual commits for more details. LINKS Task-2766574 (Appointment: improve performance) Task-2631088 (Appointment: profile and add performance tests) Forward-Port-Of: odoo/enterprise#24919
The chosen default behaviour for the Journal Groups options in the Accounting reports used to be that if no previous options were to be retrieved, the first existing Journal Group would be selected. task 261733 changed this default behaviour. This PR re-introduces it. task-2749426 Forward-Port-Of: odoo/enterprise#23903
Original PR description
The chosen default behaviour for the Journal Groups options in the Accounting reports used to be that if no previous options were to be retrieved, the first existing Journal Group would be selected. task 261733 changed this default behaviour. This PR re-introduces it. task-2749426 Forward-Port-Of: odoo/enterprise#23903
For the data in the csv export file for DateV, the customers and the suppliers are supposed to have different prefixes for the contra-account field. Before the fix, all the partners had the same prefix. After the fix, the vendors will use another prefix, the previous prefix will only be used for the customers. Forward-Port-Of: odoo/enterprise#24948 Forward-Port-Of: odoo/enterprise#22806
Original PR description
For the data in the csv export file for DateV, the customers and the suppliers are supposed to have different prefixes for the contra-account field. Before the fix, all the partners had the same prefix. After the fix, the vendors will use another prefix, the previous prefix will only be used for the customers. Forward-Port-Of: odoo/enterprise#24948 Forward-Port-Of: odoo/enterprise#22806
Since https://github.com/odoo/enterprise/pull/24234 Steps: Use three dots in a list view to 'Add custom field' For example in 'sale.order' A modal is displayed to tell us to install studio even if it is already done. This is due to the fact that the file `list_renderer_desktop.js` which contains the function to offer the user to install studio: `_onAddCustomFieldClick` https://github.com/odoo/enterprise/blob/f397e419de166ab4ab061dee44b31d75311aff0c/web_enterprise/static/src/l
Original PR description
Since https://github.com/odoo/enterprise/pull/24234 Steps: Use three dots in a list view to 'Add custom field' For example in 'sale.order' A modal is displayed to tell us to install studio even if it…
Since https://github.com/odoo/enterprise/pull/24234 Steps: Use three dots in a list view to 'Add custom field' For example in 'sale.order' A modal is displayed to tell us to install studio even if it is already done. This is due to the fact that the file `list_renderer_desktop.js` which contains the function to offer the user to install studio: `_onAddCustomFieldClick` https://github.com/odoo/enterprise/blob/f397e419de166ab4ab061dee44b31d75311aff0c/web_enterprise/static/src/legacy/js/views/list/list_renderer_desktop.js#L72-L75 is loaded after `list_renderer_eager.js` which contains the override of `_onAddCustomFieldClick` to open studio if it is already installed) https://github.com/odoo/enterprise/blob/8bcb2338cc91f190ae068ad0731bcc52867952cf/web_studio/static/src/legacy/js/views/renderers/list_renderer_eager.js#L23-L26 A solution would be to force web_studio to be loaded after `list_renderer_desktop` by adding a dependency to it https://github.com/odoo/enterprise/blob/8bcb2338cc91f190ae068ad0731bcc52867952cf/web_studio/static/src/legacy/js/views/renderers/list_renderer_eager.js#L14-L15 opw-2775063 Forward-Port-Of: odoo/enterprise#24823