Monday, February 24, 2020
55 changes · master
New functionality added to Odoo
Project users can now apply a set of example Kanban stages directly to an existing project from the examples dialog. This saves manual setup time by creating the selected stages automatically while keeping any existing stages in place.
Original PR description
when a user opens kanban examples in project, user had to create stages manually, by this pr a button is added in kanban examples modal 'use it in my project, when user clicks on this button automatically all stages of an example are created in project with one click. if some stages already exists in project new stages will be added next to existing stages. task-2179536 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
Updates made while editing a new record now apply consistently to related parent records in inherited data models. This reduces unexpected behavior during form changes and helps keep linked business data in sync before saving.
Original PR description
This makes the behavior of `onchange()` consistent in the case of inherited models (with `_inherits`).
Resolved issues and error corrections
This fixes a checkout issue where the available states could be calculated using a different address type than the country list. Customers should now see matching country and state options when entering billing or shipping details, reducing checkout confusion when delivery features are installed.
Original PR description
Description of the issue/feature this PR addresses: List of states and countries in Payment page may be incorrect when website_sale_delivery is installed Current behavior before PR: List of states is always computed for "shipping" mode, while list of countries [may be billing](https://github.com/odoo/odoo/blob/e19227d3ba9c9296bfc0c221ac70a863a571b9a6/addons/website_sale/controllers/main.py#L656) Desired behavior after PR is merged: Use the same mode for states as for countries -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @it-projects-llc
Miscellaneous changes
This commit set an index on column `picking_id` of table `stock_move_line`. Many sql requests on stock_move_line have picking_id in their where-clause. On a database filled with 1M pickings, reading a picking of 10 stock_move_lines is 60 times faster. 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:
Original PR description
This commit set an index on column `picking_id` of table `stock_move_line`. Many sql requests on stock_move_line have picking_id in their where-clause. On a database filled with 1M pickings, reading a picking of 10 stock_move_lines is 60 times faster. 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#46131
New employee records now start with the gender field left blank instead of automatically selecting male. This avoids incorrect assumptions in HR data entry and helps ensure employee information is completed intentionally.
Original PR description
Pad:https://pad.odoo.com/p/r.a01ab56e8346d56713e51055c151f84d Task:https://www.odoo.com/web#id=2165484&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720
Saving a new time off request from the dashboard pop-up now closes the dialog immediately. This removes an extra click for employees and makes the request process smoother.
Original PR description
Purpose When you create a new "time off" request from the pop-up window, no need to click twice to close the dialog. Specifications close the dialog when the first time that we click on save button. Task-id: 2183096 PR: #45137
The help tooltip explaining automatic email deletion has been clarified across email-related screens. This makes it easier for users to understand what the setting does before enabling or disabling it.
Original PR description
PURPOSE The message for help tooltip of auto_delete field is not sufficiently clear for user to understand. SPECIFICATIONS Improving message for help tooltip by adding some extra details in it so user can easily understand about it for models mail.mail, mail.template and wizard mail_compose_message. LINKS PR https://github.com/odoo/odoo/pull/45063 Task-2055702 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 update improves how several website content areas handle requests and routing, building on an earlier correction that was limited by stable-release constraints. Business users should see more consistent behavior across blogs, events, forums, and mail channel pages, reducing friction for visitors browsing public website content.
Original PR description
* website_blog, website_event_track, website_forum, website_mail_channel 7dd7043 was introduced in stable as a fix, which obviously had some stable policy preventing some changes. This commit improves that commit in master. task-2119086
Analytic default rules are now included directly in Accounting, Expenses, and Purchasing instead of requiring separate add-on modules. This reduces setup steps after enabling analytics and helps teams apply analytic tracking consistently across these business flows.
Original PR description
Merge account_analytic_default into account Merge account_analytic_default_hr_expense into hr Merge account_analytic_default_purchase into purchase Prevent having to manually install default modules after activating analytics Task: 2182900
Access rights screens now let users group record rules by the related business object, matching the grouping already available for model access rights. This makes it easier for administrators to review and organize security rules when managing permissions.
Original PR description
Before this commit, There was no option to Group Record rules by Object. 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
Sales orders with dropshipping lines now provide a direct way to open the related purchase order. This saves time for users who need to track or manage the purchase generated from a dropship sale.
Original PR description
When you create a sale order with some line with dropshipping, you not a direct access to the purchase generared. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Belgian payroll users can now download fiche 281.10 and 281.45 files directly from the generation wizard instead of automatically posting them on employee records. When the Documents app is installed, these files can also be stored in a dedicated Payroll folder for access by employees and payroll teams.
Original PR description
Currently, fiches 281.45 and 281.10 are posted on the employee chatter. Storing those files is not necessary. This commit allows to directly download the files from the generation wizard. To keep a copy of the generated files, a Documents integration will shortly be developped.
The salary configurator no longer assumes an employee is male when no gender is recorded. Users must now choose a gender before submitting, improving data accuracy in salary and contract setup.
Original PR description
Pad:https://pad.odoo.com/p/r.a01ab56e8346d56713e51055c151f84d Task:https://www.odoo.com/web#id=2165484&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720
Recruitment stages can now be marked as not hired, keeping those candidates off the referral dashboard. These stages also stop referral points from being awarded for unsuccessful applications, while normal point tracking resumes if the candidate later moves back into an eligible stage.
Original PR description
Add a boolean on recruitment stage to said that is a 'not hired stage'. When it's true: 1. this recruitment stage will not be display on referral dashboard. 2. this stage give no points (neither if this stage is at the end of process, and we go for example from stage seq 4 to this stage with sequence 10, no points will bre gived). And after, if we go to normal stage with sequence 6, we will received points for stage 5 and 6. taskID: 2165770
Timesheet descriptions are now easier to enter, with a larger text area and helpful placeholder text in the timesheet form. Helpdesk ticket timesheets no longer require a description, reducing friction when logging time on support work.
Original PR description
Before commit: The description field did was displayed as input box with label in timesheet form view. After commit, description field will be displayed as text box with placeholder Before, description field is required in list view of timesheet in helpdesk ticket. After Commit, description field not required for ticket time sheet. Taskid : 2176065
This fixes an issue where employee expense analytics information could be erased when no default analytic account was found. It keeps expense entries more reliable and prevents related expense tests from failing when the analytic default integration is installed.
Original PR description
_onchange_product_id used to set hr_expense analytic_account_id & analytic_tag_ids to False if it could not find a default analytic account. Installing account_analytic_default_hr_expense made odoo/addons/hr_expense/tests/test_expenses.py tests fail - changed function name (no need to be a _onchange_product_id override) - removed super() & return - check if account_get() returns something Related to task 2182900
The checkout address form now shows state options based on whether the customer is editing a billing or shipping address. This prevents delivery restrictions from incorrectly hiding billing states or showing unavailable shipping states, helping customers complete checkout with the right address choices.
Original PR description
All states would be listed in shipping mode Only restricted states would be listed in billing mode See commits for more details
This fixes an internal issue in Point of Sale order updates by removing an incorrect marker from the order write process. The change helps ensure POS order changes are handled as intended, reducing the risk of unexpected behavior for users.
Original PR description
Follow-up on 118190f3b3ecde11d7bcb46301af0e016d6ea19f Remove the wrong decorator from the write method. 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 removes an incorrect setup marker from the Alipay payment update process. It helps ensure Alipay payment settings can be saved using the intended standard behavior, reducing the risk of unexpected errors for administrators.
Original PR description
Remove the wrong decorator from the write method. 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
Fixed an issue that caused an error when users grouped timesheets by date in the grid view. Date grouping remains available where it is useful, such as list views, while the grid now avoids the problematic behavior.
Original PR description
Before this commit, when we try to make a group by date in timesheet grid, we have a traceback. This group by date is useless in grid view but very useful for list view. Now, when we make a group by date in the timesheet grid, we don't apply the group_expand. TaskID: 2169272
If IoT Box is in access point mode and a server is configured the box try to reach the server. But in access point mode all requests are redirected to the box So now before return `True` in function `get_odoo_server_url` we verify if the service `hostapd` is inactive 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 F
Original PR description
If IoT Box is in access point mode and a server is configured the box try to reach the server. But in access point mode all requests are redirected to the box So now before return `True` in function `get_odoo_server_url` we verify if the service `hostapd` is inactive 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#46105
- The form view on `res.users` displays information about how many record rules, ACL and groups are applied to the users. In some cases the current users may not have the required access rights to compute those values. To fix this issue, the computed fields are now computed in `compute_sudo` mode -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46098 Forward-Port-Of: odoo/odoo#45634
Original PR description
- The form view on `res.users` displays information about
how many record rules, ACL and groups are applied to the users.
In some cases the current users may not have the required
access rights to compute those values.
To fix this issue, the computed fields are now computed
in `compute_sudo` mode
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#46098
Forward-Port-Of: odoo/odoo#45634Update the blackbox from v11 in v13. We had to make a new driver to be able to use the blackbox with the iotbox. We also had to make the new features compatible with the blackbox. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45961 Forward-Port-Of: odoo/odoo#39833
Original PR description
Update the blackbox from v11 in v13. We had to make a new driver to be able to use the blackbox with the iotbox. We also had to make the new features compatible with the blackbox. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45961 Forward-Port-Of: odoo/odoo#39833
Before this commit: When logged in and navigating on a frontend page, the accessible `ir.ui.menu` would be loaded in qcontext. Loading those menus performs alot of SQL request, up to ~2.000 requests on big databases such as Odoo.com for an user with a lot of access rights. Note that this qcontext computation in frontend was pointless in enterprise as the applications menu in frontend redirect to the backend without using it. This commit removes that computation from the qcontext. The
Original PR description
Before this commit: When logged in and navigating on a frontend page, the accessible `ir.ui.menu` would be loaded in qcontext. Loading those menus performs alot of SQL request, up to ~2.000 requests on big databases such as Odoo.com for an user with a lot of access rights. Note that this qcontext computation in frontend was pointless in enterprise as the applications menu in frontend redirect to the backend without using it. This commit removes that computation from the qcontext. The menus will be computed and loaded only when the user really needs it, when he is about to open the application menu. Forward-Port-Of: odoo/odoo#46044 Forward-Port-Of: odoo/odoo#45839
Every records created from frontend should have the website_id set to the current website. Most was done with 066cfc9598a3, but forum was missing it. Fixes #45749 Forward-Port-Of: odoo/odoo#46006 Forward-Port-Of: odoo/odoo#45982
Original PR description
Every records created from frontend should have the website_id set to the current website. Most was done with 066cfc9598a3, but forum was missing it. Fixes #45749 Forward-Port-Of: odoo/odoo#46006 Forward-Port-Of: odoo/odoo#45982
When creating a new user on-the-fly on the employee detail page (HR Settings/Related User), if the employee is never linked with a user before, the new created user will not be linked with the employee automatically and we have to select the user again. With this commit, the new created user will be linked with the employee automatically. Fixes #44442 Forward-Port-Of: odoo/odoo#45411
Original PR description
When creating a new user on-the-fly on the employee detail page (HR Settings/Related User), if the employee is never linked with a user before, the new created user will not be linked with the employee automatically and we have to select the user again. With this commit, the new created user will be linked with the employee automatically. Fixes #44442 Forward-Port-Of: odoo/odoo#45411
Since the commit e95ccf0 invalid client-side domain will raise the error So purpose of the task is to fix the invalid client-side domain. Task: 2196805 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45680
Original PR description
Since the commit e95ccf0 invalid client-side domain will raise the error So purpose of the task is to fix the invalid client-side domain. Task: 2196805 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45680
For a upgrade the IoT Box perform a "git reset hard" And after we restart odoo. But it is not enough and we need to reboot the IoT Box 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#46079
Original PR description
For a upgrade the IoT Box perform a "git reset hard" And after we restart odoo. But it is not enough and we need to reboot the IoT Box 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#46079
- Activate the multi-step reception - Create a Subcontracting BOM for product P and supplier S. - Create a PO for S with P - Validate the PO - Validate the input transfer - Validate the internal transfer A error is raised because a mandatory field is not set. The root cause comes from the INT move being flagged as a subcontract move, while it shouldn't be. Indeed, only the input move should be flagged as subcontract. We force the `is_subcontract` value to `False` when a move is c
Original PR description
- Activate the multi-step reception - Create a Subcontracting BOM for product P and supplier S. - Create a PO for S with P - Validate the PO - Validate the input transfer - Validate the internal transfer A error is raised because a mandatory field is not set. The root cause comes from the INT move being flagged as a subcontract move, while it shouldn't be. Indeed, only the input move should be flagged as subcontract. We force the `is_subcontract` value to `False` when a move is copied in the context of a stock rule. opw-2193009 opw-2202727 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#46053
related to 896e36e Fixes #41813 Forward-Port-Of: odoo/odoo#46071 Forward-Port-Of: odoo/odoo#46021
Original PR description
related to 896e36e Fixes #41813 Forward-Port-Of: odoo/odoo#46071 Forward-Port-Of: odoo/odoo#46021
If you have a currency with 3 decimals, when you show a list view grouped, you might have result like: [group partner 1 : amount : 4.4€] - amount : 1.11€ - amount : 3.33€ which is a little odd, it is not that odd since the groupings are an approximation (eg. you could have a line in EUR and a line in USD and the grouping value would be the sum of both line). But there is no way to specify another precision, and since this is a grouping it could be of line of
Original PR description
If you have a currency with 3 decimals, when you show a list view
grouped, you might have result like:
[group partner 1 : amount : 4.4€]
- amount : 1.11€
- amount : 3.33€
which is a little odd, it is not that odd since the groupings are an
approximation (eg. you could have a line in EUR and a line in USD and
the grouping value would be the sum of both line).
But there is no way to specify another precision, and since this is a
grouping it could be of line of different currencies so we can't use the
lines currency to decide.
With this changeset, having for example:
<field name="amount" digits="[69,3]"/>
with `digits` attribute is taken into account for the aggregate value
and it would be displayed with 3 decimals.
Without the fix, the added test fails with:
aggregates monetary use digits attribute if available
Expected: "2000.000", Result: "2000.00"
opw-2195042
Forward-Port-Of: odoo/odoo#45983
Forward-Port-Of: odoo/odoo#45545Steps to reproduce the bug: - Install Manufacturing - Go to General Settings/Inventory and tick Units of Measure - Create a product P (storable) with UOM kg - Create a Bill of Material for this product: e.g. 1 kg - Add a component C with UOM "kg", but in the BOM uses "g" - Create a MO for P, Mark as todo, Produce - Click on C to change the quantities (e.g. change the first line to 900 g) - Add a second line with 0.1 kg (as the uom of C is in kg, you are forced to set in kg) Bug:
Original PR description
Steps to reproduce the bug: - Install Manufacturing - Go to General Settings/Inventory and tick Units of Measure - Create a product P (storable) with UOM kg - Create a Bill of Material for this product: e.g. 1 kg - Add a component C with UOM "kg", but in the BOM uses "g" - Create a MO for P, Mark as todo, Produce - Click on C to change the quantities (e.g. change the first line to 900 g) - Add a second line with 0.1 kg (as the uom of C is in kg, you are forced to set in kg) Bug: The consumed quantity for C in the MO was 900.1 g instead of 1000 g. opw:2181892 Forward-Port-Of: odoo/odoo#45737
fixes #19696 Forward-Port-Of: odoo/odoo#46048
Original PR description
fixes #19696 Forward-Port-Of: odoo/odoo#46048
PURPOSE The SMS confirmation settings have the right and meaning full name. SPECIFICATIONS Currently, SMS confirmation settings have name looks like a technical name so, user can not understand the feature what is it dose and what is its use. The main goal is to give a correct and meaning full name to SMS confirmation settings. To do that we modify the name of SMS confirmation settings "SMS Validation with stock move" to "SMS Validation". LINKS PR#46018 Task 2185325
Original PR description
PURPOSE The SMS confirmation settings have the right and meaning full name. SPECIFICATIONS Currently, SMS confirmation settings have name looks like a technical name so, user can not understand the feature what is it dose and what is its use. The main goal is to give a correct and meaning full name to SMS confirmation settings. To do that we modify the name of SMS confirmation settings "SMS Validation with stock move" to "SMS Validation". LINKS PR#46018 Task 2185325 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46018
Followup on 82ce815a8c4c978b3372282d88559282d32d4b07 When Content (`slide.slide`) is duplicated, public_views should not be copied for obvious reasons. 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#46011
Original PR description
Followup on 82ce815a8c4c978b3372282d88559282d32d4b07 When Content (`slide.slide`) is duplicated, public_views should not be copied for obvious reasons. 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#46011
This commit fixes an issue that raised an error when trying to create a slide.slide of type "category" on the slide.slide kanban view. Since it's not possible to disable the "group creation" on the kanban for a single filter, we disable it globally. At the same time, we removed the capability to drag and drop slides in that view. It was not very useful and could mess up the records by changing the slide type without changing the associated data (video link, presentation file, ...).
Original PR description
This commit fixes an issue that raised an error when trying to create a slide.slide of type "category" on the slide.slide kanban view. Since it's not possible to disable the "group creation" on the kanban for a single filter, we disable it globally. At the same time, we removed the capability to drag and drop slides in that view. It was not very useful and could mess up the records by changing the slide type without changing the associated data (video link, presentation file, ...). Issue #45452 Task 2201878 Forward-Port-Of: odoo/odoo#45930
It has been replaced by a button in the languages list & form views `Activate Language and Update Translations` Forward-Port-Of: odoo/odoo#46028
Original PR description
It has been replaced by a button in the languages list & form views `Activate Language and Update Translations` Forward-Port-Of: odoo/odoo#46028
Task 2198528 The xml id was duplicated, leading to a missing rule. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45598
Original PR description
Task 2198528 The xml id was duplicated, leading to a missing rule. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45598
Fix account type on 108.01.01 & 108.02.01 According to the SAT catalog must be an account of Current Assets Fix the account type and the tag on 811.01.01 According to the SAT catalog must be an account of Expenses, and the tag must be 811.01 <img width="843" alt="Screen Shot 2020-02-12 at 11 02 04" src="https://user-images.githubusercontent.com/7606656/74372728-c301c280-4da0-11ea-9f8d-c726fec07765.png"> -- I confirm I have signed the CLA and read the PR guidelines at www.odo
Original PR description
Fix account type on 108.01.01 & 108.02.01 According to the SAT catalog must be an account of Current Assets Fix the account type and the tag on 811.01.01 According to the SAT catalog must be an account of Expenses, and the tag must be 811.01 <img width="843" alt="Screen Shot 2020-02-12 at 11 02 04" src="https://user-images.githubusercontent.com/7606656/74372728-c301c280-4da0-11ea-9f8d-c726fec07765.png"> -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45741 Forward-Port-Of: odoo/odoo#45245
Previous scheme would just print `Array(2)` because it's an array of length 2 which is bloody useless. After some investigation remote arrays are simply serialized as remote objects with indices as property names. So we can ignore the names and serialize just the property values to get something resembling an array literal. Forward-Port-Of: odoo/odoo#46024
Original PR description
Previous scheme would just print `Array(2)` because it's an array of length 2 which is bloody useless. After some investigation remote arrays are simply serialized as remote objects with indices as property names. So we can ignore the names and serialize just the property values to get something resembling an array literal. Forward-Port-Of: odoo/odoo#46024
The automaticResponseURL should not be the same as the one the customer uses, as this might mess up with the payment processing page when the customer actually returns. Add some logging while I'm here, and remove a useless write on a non-existing field that generates log warnings (but nothing else). Forward-Port-Of: odoo/odoo#46019
Original PR description
The automaticResponseURL should not be the same as the one the customer uses, as this might mess up with the payment processing page when the customer actually returns. Add some logging while I'm here, and remove a useless write on a non-existing field that generates log warnings (but nothing else). Forward-Port-Of: odoo/odoo#46019
In the POS interface, when searching through a large catalog of products (~80000 in our test), the interface used to freeze for 5-10 seconds before returning search results. After profiling the issue, we noticed that the unaccent'ing of product names was done in the search loop. Moving the unaccent outside the search loop (at product catalog initialization) solves the issue. We also change the timer before triggering a search: 70 ms after any keypress is too short. In practice, thi
Original PR description
In the POS interface, when searching through a large catalog of products (~80000 in our test), the interface used to freeze for 5-10 seconds before returning search results. After profiling the issue, we noticed that the unaccent'ing of product names was done in the search loop. Moving the unaccent outside the search loop (at product catalog initialization) solves the issue. We also change the timer before triggering a search: 70 ms after any keypress is too short. In practice, this would trigger a search at every keypress. 200 ms appears to be a good compromise between UI interactivity and saving useless computations opw-[2185087](https://www.odoo.com/web#id=2185087&model=project.task&view_type=form&cids=&menu_id=5200)-rim fixes 9ee9724a10fc5e835d8d42da0e9e83fe687848d8 Forward-Port-Of: odoo/odoo#45734
Description of the issue/feature this PR addresses: Spelling error in deployment documentation Current behavior before PR: 1Go Desired behavior after PR is merged: 1GB -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45756
Original PR description
Description of the issue/feature this PR addresses: Spelling error in deployment documentation Current behavior before PR: 1Go Desired behavior after PR is merged: 1GB -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45756
See individual commits for more details. opw-2169863 Forward-Port-Of: odoo/odoo#45521 Forward-Port-Of: odoo/odoo#44534
Original PR description
See individual commits for more details. opw-2169863 Forward-Port-Of: odoo/odoo#45521 Forward-Port-Of: odoo/odoo#44534
On the partners page, the class is not fully applied to the logos because 'img-fluid' is applied first via the 'image' widget. This cause max-width to be overriden with the value 100%, breaking the partners page layout. Forward-Port-Of: odoo/odoo#45445
Original PR description
On the partners page, the class is not fully applied to the logos because 'img-fluid' is applied first via the 'image' widget. This cause max-width to be overriden with the value 100%, breaking the partners page layout. Forward-Port-Of: odoo/odoo#45445
Steps to reproduce the bug: - Install website_crm_score - Add Mitchell Admin in 2 sales teams - Create a quote - Play with the ordering of sales teams sequences Bug: The default sales team will be different at quote creation, partner selection, etc. and will basically be unpredictable (while you would expect it to take the first team the salesperson is a member of in the order of the sequence) The problem is an inconsistent use of the _get_default_team_id method and the sales te
Original PR description
Steps to reproduce the bug: - Install website_crm_score - Add Mitchell Admin in 2 sales teams - Create a quote - Play with the ordering of sales teams sequences Bug: The default sales team will be different at quote creation, partner selection, etc. and will basically be unpredictable (while you would expect it to take the first team the salesperson is a member of in the order of the sequence) The problem is an inconsistent use of the _get_default_team_id method and the sales team of a user. Since the website score module add the possibility to have a user member of more than one team, using the team of the user is bad. You should use the method all the time for consistent results. opw:2196934 Forward-Port-Of: odoo/odoo#45618
Check commit message for details, issues are unrelated. Forward-Port-Of: odoo/enterprise#8711
Original PR description
Check commit message for details, issues are unrelated. Forward-Port-Of: odoo/enterprise#8711
Update the blackbox from v11 in v13. We had to make a new driver to be able to use the blackbox with the iotbox. We also had to make the new features compatible with the blackbox. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#8645 Forward-Port-Of: odoo/enterprise#6566
Original PR description
Update the blackbox from v11 in v13. We had to make a new driver to be able to use the blackbox with the iotbox. We also had to make the new features compatible with the blackbox. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#8645 Forward-Port-Of: odoo/enterprise#6566
Currently when select record multiple record from expense list view, and from action menu click on 'Create Report' will generate traceback. So fix the traceback by handling multiple record in server action method. After this commit, Traceback will not be generated when select multiple record and click on 'create report'. Taskid: 2196805 Forward-Port-Of: odoo/enterprise#8544
Original PR description
Currently when select record multiple record from expense list view, and from action menu click on 'Create Report' will generate traceback. So fix the traceback by handling multiple record in server action method. After this commit, Traceback will not be generated when select multiple record and click on 'create report'. Taskid: 2196805 Forward-Port-Of: odoo/enterprise#8544
The service type FEDEX_EXPRESS_SAVER was not supported. We add it to the list of supported service types for Fedex. opw 2179876 Forward-Port-Of: odoo/enterprise#8660
Original PR description
The service type FEDEX_EXPRESS_SAVER was not supported. We add it to the list of supported service types for Fedex. opw 2179876 Forward-Port-Of: odoo/enterprise#8660
* If we try to import the accounting entries through multiple files (i.e. one per fiscal year), we might encounter this case: 3 lines are reconciled; the first 2 are in one file and the last one in another file. Because we try the reconciliation at the end of every import, we will have one of the first 2 lines that is marked as reconciled, the other still with an open amount. When we import the second file, we are trying to reconcile all the 3 lines because they had the same matching numb
Original PR description
* If we try to import the accounting entries through multiple files (i.e. one per fiscal year), we might encounter this case: 3 lines are reconciled; the first 2 are in one file and the last one in another file. Because we try the reconciliation at the end of every import, we will have one of the first 2 lines that is marked as reconciled, the other still with an open amount. When we import the second file, we are trying to reconcile all the 3 lines because they had the same matching number in winbooks, but it will raise an error because one line is already reconciled. We should only take the line that was with an open amount to reconcile it with the third line. * Another issue is that taxes with the same name might change the amount through the years. Forward-Port-Of: odoo/enterprise#8677
[CLEAN] hr_appraisal: use group_expand group_expand work also with selection field use that feature instead of overriding the method read_group [FIX] hr_appraisal: Fix test Create a calendar.event to check that date_final_interview is correctly set not the other way around [FIX] hr_appraisal: Fix final interview The only way to set the final interview date in the flow is to create a meeting. Thus the method schedule final meeting based on the da
Original PR description
[CLEAN] hr_appraisal: use group_expand group_expand work also with selection field use that feature instead of overriding the method read_group [FIX] hr_appraisal: Fix test Create a calendar.event to…
[CLEAN] hr_appraisal: use group_expand
group_expand work also with selection field
use that feature instead of overriding the method read_group
[FIX] hr_appraisal: Fix test
Create a calendar.event to check that date_final_interview is correctly set
not the other way around
[FIX] hr_appraisal: Fix final interview
The only way to set the final interview date in the flow
is to create a meeting. Thus the method schedule final meeting
based on the date_final_interview is not necessary anymore
and was introduicing a bug
You create a meeting, the hour were overwritten to 00:00:00
Do not trigger schedule_final_meeting when writing on date_final_interview
Method schedule_final_meeting is not used anymore but since it's public
it cannot be removed on a stable version
Fix: method create of calendar.event
Use field on the created event instead of the value in the context
Check the record appraisal really exist
browse(ID) is always evaluated to True even if the ID
does not exist in database
[FIX] appraisal: appraisal cron generation
Make appraisal_date = last_appraisal_date consistent
next_appraisal_date = last_appraisal_date + x Months
Generate appraisal x days before the next_appraisal_date
Remove useless flag periodic_appraisal_created (TODO remove field in master)
deadline on the appraisal set the appraisal_date (aka last_appraisal_date)
deadline is set x days after the generation of the appraisal
(aka at the next_appraisal_date)
remove constraint that appraisal_date cannot be set in the past
doesn't make sense since it's the last_appraisal_date
[ADD] hr_appraisal: Add many test_case
- appraisal_generation
When appraisal date is just enouth in the past
- noappraisal_generation
When appraisal date is not enough in the past
- appraisal_generation_in_the_past
When appraisal date is far in the past
- check_appraisal_date_no_appraisal
For new employee
- check_appraisal_date_appraisal_past_year
For an employee with a recent appraisal
No new appraisal generated
- check_appraisal_date_appraisal_long_time_ago
For an employee with a old enough appraisal
new appraisal generated
- check_manual_appraisal_set_appraisal_date
- request_appraisal_from_employee
- request_appraisal_from_user
Forward-Port-Of: odoo/enterprise#8485
Forward-Port-Of: odoo/enterprise#8412PURPOSE The worksheet should always be displayed on the tablet view, also if there is no quality check. SPECIFICATIONS The worksheet set on the manufacturing operation isn't displayed by default, because the worksheet is displayed when the work orders have an 'is_first_step' and the 'is_fist_step' is enabled when there is a quality check. The main goal is to display worksheets on tablet view. To do that, we make the first step enabled also if there is a not quality check.
Original PR description
PURPOSE The worksheet should always be displayed on the tablet view, also if there is no quality check. SPECIFICATIONS The worksheet set on the manufacturing operation isn't displayed by default, because the worksheet is displayed when the work orders have an 'is_first_step' and the 'is_fist_step' is enabled when there is a quality check. The main goal is to display worksheets on tablet view. To do that, we make the first step enabled also if there is a not quality check. LINKS PR 8458 Task 2188543 Forward-Port-Of: odoo/enterprise#8458
- Create a BOM using a routing with several steps, e.g. 'Secondary Assembly' - Make sure the 'Next Operation' is set to 'Once all products are processed' - Create an Plan a MO - Go to Manufacturing > Overview > Assembly Station 1 - Remove the 'Ready' or 'In Progress' filter - Click on the 'Testing' or 'Long time assembly' WO of your MO The WO is set as 'In Progress' automatically. This is because `button_start` is triggered automatically, while in this case it was not expected
Original PR description
- Create a BOM using a routing with several steps, e.g. 'Secondary Assembly' - Make sure the 'Next Operation' is set to 'Once all products are processed' - Create an Plan a MO - Go to Manufacturing > Overview > Assembly Station 1 - Remove the 'Ready' or 'In Progress' filter - Click on the 'Testing' or 'Long time assembly' WO of your MO The WO is set as 'In Progress' automatically. This is because `button_start` is triggered automatically, while in this case it was not expected to start the WO. We start the WO only if its state is 'Ready' or 'In Progress'. opw-2194681 Forward-Port-Of: odoo/enterprise#8630
It was impossible to select the generic tax report because of the option management. Forward-Port-Of: odoo/enterprise#8642 Forward-Port-Of: odoo/enterprise#8570
Original PR description
It was impossible to select the generic tax report because of the option management. Forward-Port-Of: odoo/enterprise#8642 Forward-Port-Of: odoo/enterprise#8570