Tuesday, December 22, 2020
13 changes · master
Enhancements to existing features
The web interface now uses a clearer sorting icon for drag handles in editable lists and export field ordering. The cursor also changes to indicate when items can be grabbed and when they are being dragged, making reordering feel more intuitive for users.
Original PR description
PURPOSE
Our current drag handle icon (fa-arrows) would be more adapted for moving items in a two-dimensional space (left/right and up/down). The purpose of this task is to improve the icon of the 'handle' widget
SPEC
change the fa-arrows icon to fa-sort
when hover set cursor: grab
when dragging the row set cursor: grabbing
TASK 2413274
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThe drag handle icon in form list cells is now centered, making rows easier to scan and interact with. This small visual polish improves consistency and readability in the Enterprise interface.
Original PR description
Display handle icon in center in cell. TASK 2413274
Miscellaneous changes
In the Barcode app, if the user is on a delivery order, adds a product and then decreases the product's quantity, when validating the order, the backorder window is displayed. To reproduce the error: (Need sale_management,stock_barcode) 1. Go to Sales 2. Create a SO - Add one Product P 3. Save, Confirm 4. Check the generated delivery reference R 4. Go to Barcode > Operations > Delivery Orders > R 5. Complete the P's quantity 6. Add Product - Select a Product P_extra - Set a qu
Original PR description
In the Barcode app, if the user is on a delivery order, adds a product and then decreases the product's quantity, when validating the order, the backorder window is displayed. To reproduce the error:…
In the Barcode app, if the user is on a delivery order, adds a product and then decreases the product's quantity, when validating the order, the backorder window is displayed. To reproduce the error: (Need sale_management,stock_barcode) 1. Go to Sales 2. Create a SO - Add one Product P 3. Save, Confirm 4. Check the generated delivery reference R 4. Go to Barcode > Operations > Delivery Orders > R 5. Complete the P's quantity 6. Add Product - Select a Product P_extra - Set a quantity (e.g., 1) 7. Confirm 8. Edit the P_extra's line - Decrease the quantity (e.g., 0) 9. Confirm 10. Validate => A window is displayed so the user can create a backorder for the missing P_extra. Since the SO does not contains any P_extra, proposing to create a backorder does not make sense. When adding an extra product to the delivery, it creates a stock move line with the `product_uom_qty` set to 0. Since there isn't any stock move associated, it also creates a new one. Here is the issue: the `product_uom_qty` of the stock move is defined thanks to the `qty_done` of the extra product. Later, when validating the delivery, the server uses the `product_uom_qty` of the stock move to check if a backorder is needed. This the reason why, if the user decreased the quantity, the backorder proposition is displayed: the `qty_done` is less than the `product_uom_qty`. OPW-2411461 Forward-Port-Of: odoo/odoo#63542
…ut currency When you remove the 'company_id' on a crm.lead, you also remove the computed 'company_currency'. When trying to view this kind of leads in the website_crm_partner_assign portal page, it would raise an error while trying to display the planned_revenue in the missing currency. Now, we display the number without any currency sign, which is a "best effort" solution, just the same as on the crm.lead form view. So it will look like "9000 at 47%" instead of "$9000 at 47%". T
Original PR description
…ut currency When you remove the 'company_id' on a crm.lead, you also remove the computed 'company_currency'. When trying to view this kind of leads in the website_crm_partner_assign portal page, it would raise an error while trying to display the planned_revenue in the missing currency. Now, we display the number without any currency sign, which is a "best effort" solution, just the same as on the crm.lead form view. So it will look like "9000 at 47%" instead of "$9000 at 47%". Task 2416841 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#63626 Forward-Port-Of: odoo/odoo#63552
PURPOSE On a list view, if something is shown in between the list and the control panel, the scroll bar is always shown. SPEC scrollbar should not be displayed if something shown in between list and control panel. TASK 2334044 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#58138
Original PR description
PURPOSE On a list view, if something is shown in between the list and the control panel, the scroll bar is always shown. SPEC scrollbar should not be displayed if something shown in between list and control panel. TASK 2334044 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#58138
This commit fixes the ticket sale start date to be considered inclusive. Indeed, before this commit, if the sales of a ticket starts on the 1st of December, people arriving on the website at that exact date will NOT be able to buy tickets although they should be. They will have to wait for the next day to be able to buy tickets. A small test was added to ensure this behavior. Task 2415917 Description of the issue/feature this PR addresses: Current behavior before PR: Desired
Original PR description
This commit fixes the ticket sale start date to be considered inclusive. Indeed, before this commit, if the sales of a ticket starts on the 1st of December, people arriving on the website at that exact date will NOT be able to buy tickets although they should be. They will have to wait for the next day to be able to buy tickets. A small test was added to ensure this behavior. Task 2415917 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#63512
When you create a new record, you will have in this order: - default_get - onchange (can trigger a warning) - _pushController => close all dialogs since ea2207a This is an issue since the possible warning is directly hidden to the user. Without the change, the added test failed with: Warning modal should be opened "executing a window action with onchange warning do not hide it": Found 0 elements to click on, instead of 1 opw-2342273 opw-2374051 Forward-Port-Of: odoo/odoo
Original PR description
When you create a new record, you will have in this order: - default_get - onchange (can trigger a warning) - _pushController => close all dialogs since ea2207a This is an issue since the possible warning is directly hidden to the user. Without the change, the added test failed with: Warning modal should be opened "executing a window action with onchange warning do not hide it": Found 0 elements to click on, instead of 1 opw-2342273 opw-2374051 Forward-Port-Of: odoo/odoo#63270 Forward-Port-Of: odoo/odoo#61732
### Goal of the PR This PR is in the continuity of odoo#62360. ### Details - Display remaining hours in task sales_line_id (name_get + task form view) - Remove internal reference from services demo data - Display sol in project timesheets list if project is billable - Remove use of non_allow_billable in timesheets as it has been removed from project and task in previous PR (see above) - Only recompute planned_hours for service product - Determine the correct SOL for timesheet - S
Original PR description
### Goal of the PR This PR is in the continuity of odoo#62360. ### Details - Display remaining hours in task sales_line_id (name_get + task form view) - Remove internal reference from services demo…
### Goal of the PR This PR is in the continuity of odoo#62360. ### Details - Display remaining hours in task sales_line_id (name_get + task form view) - Remove internal reference from services demo data - Display sol in project timesheets list if project is billable - Remove use of non_allow_billable in timesheets as it has been removed from project and task in previous PR (see above) - Only recompute planned_hours for service product - Determine the correct SOL for timesheet - Set the last SOL of customer on timesheet if none is set on task or project - Allow edition of so_line in timesheet - Restrict SOL on project to sale lines with a service product - Use same widget on partner_id many2One than in sale.order (using ranking) - Remove timesheets table in SO and invoice portal.They were added in previous PR (see above). This introduces the use of links to /my/timesheets/. - Review portal timesheets (my/timesheets/ and link from orders and invoices) - Activate group_uom "Units of Measure" on sale_timesheet install - Hide partner phone number in task form view - Only determine SOL of task and timesheet if allow_billable=True - Filter SOL in task so that it matches the SOL of the project SO - Display red label if remaining hours is negative - Change SO compute behavior - Only open SO for salesman on project overview task-2409761 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#63667 Forward-Port-Of: odoo/odoo#62900
Purpose ======= This PR is the continuity of #15025. ## Details * Update demo data: * remove internal reference from services, * add 'Hours' uom on some services products. * Hide SO and show SOL in task and ticket. * Link task with SOL rather than SO. * Optionaly display task_id on SO Lines * Review the form view of helpdesk.ticket * Update the visibility SOL in ticket * Allow edition of so_line in timesheets * Display so_line only if it is billable * Remaining hours on S
Original PR description
Purpose ======= This PR is the continuity of #15025. ## Details * Update demo data: * remove internal reference from services, * add 'Hours' uom on some services products. * Hide SO and show SOL in…
Purpose ======= This PR is the continuity of #15025. ## Details * Update demo data: * remove internal reference from services, * add 'Hours' uom on some services products. * Hide SO and show SOL in task and ticket. * Link task with SOL rather than SO. * Optionaly display task_id on SO Lines * Review the form view of helpdesk.ticket * Update the visibility SOL in ticket * Allow edition of so_line in timesheets * Display so_line only if it is billable * Remaining hours on SO in ticket. * Helpdesk: recompute the quantity delivered in SOL when the SOL changed in timesheets of ticket. * Mainly link the stat button with the SOL of ticket * Sort partners in ticket, task and project form views by their ranking as it is the case in sale.order form view * Add timesheets on ticket in portal * Set SOL based on customer in task and ticket. * Determine SOL only if allow_billable=True. * Compute the so_line for others timesheets, when these timesheets are not visible by the user and he changes the SOL in ticket form view. * Filter SOL in task and ticket view form when the SO is defined in the linked project. * Display partner address in FSM task. * Fix view dependency issue. * Add SOL in tree view of timesheets. * Replace the preprocess and postprocess for SOL in timesheets by a compute. Related PR: odoo/odoo#62900 task-2409761 Forward-Port-Of: odoo/enterprise#15407 Forward-Port-Of: odoo/enterprise#15264
PURPOSE Map marker popup is not displayed fully when clicking on map sidebar, popup should be displayed fully when clicking on map sidebar. SPEC Show map popup fully and center map relative to popup height. TASK 2304982 Forward-Port-Of: odoo/enterprise#14092
Original PR description
PURPOSE Map marker popup is not displayed fully when clicking on map sidebar, popup should be displayed fully when clicking on map sidebar. SPEC Show map popup fully and center map relative to popup height. TASK 2304982 Forward-Port-Of: odoo/enterprise#14092
PURPOSE Adding long note on planning.slot and hovering on gantt pill flickers pill itself. SPEC Adding long note or whenever content of popover is big, popover should not flicker pill. TASK 2348608 Forward-Port-Of: odoo/enterprise#13887
Original PR description
PURPOSE Adding long note on planning.slot and hovering on gantt pill flickers pill itself. SPEC Adding long note or whenever content of popover is big, popover should not flicker pill. TASK 2348608 Forward-Port-Of: odoo/enterprise#13887
When an employee is no longer working on the company, the employee get inactivate, archiving the employee record. Sometimes the company must pay one or more payslips to that employee, for example for the time worked on the current payslip period, or for other concepts. This case of use is very common, for example the profit sharing. Maybe those employees or no longer working in the company. When it is necessary to add an archived employee in a batch, it is posible to add it, howeve
Original PR description
When an employee is no longer working on the company, the employee get inactivate, archiving the employee record. Sometimes the company must pay one or more payslips to that employee, for example for the time worked on the current payslip period, or for other concepts. This case of use is very common, for example the profit sharing. Maybe those employees or no longer working in the company. When it is necessary to add an archived employee in a batch, it is posible to add it, however when confirmation button is clicked, the archived employee is deleted and the payslips is not created. Now it is possible to add archived employees to a batch and create their payslips. Note: I backported commit feca7e8f318a9c4c77184f8052d3e64303988ea2, and added a commit for a unit test on top of it. Forward-Port-Of: odoo/enterprise#15371 Forward-Port-Of: odoo/enterprise#15358
PURPOSE Resequencing of the menu through studio should work smoothly. SPEC Set proper parent_id while resequencing menus. TASK 2365375 Forward-Port-Of: odoo/enterprise#14237
Original PR description
PURPOSE Resequencing of the menu through studio should work smoothly. SPEC Set proper parent_id while resequencing menus. TASK 2365375 Forward-Port-Of: odoo/enterprise#14237