Wednesday, June 30, 2021
9 changes · master
Enhancements to existing features
Calendar year view popovers now display the event duration before the event name. This makes the time information easier to see when event names are long and would otherwise hide or cut off the duration.
Original PR description
In calendar year mode, the duration will appear before the event name because if the event name is too long, the duration does not appear. Like: crop the shift name if it becomes too long to display on one line. then the duration is cropped. TaskID:- 2502245
Live chat channels now show a simpler happiness indicator focused on the happy rating percentage, making channel satisfaction easier to understand at a glance. Rating buttons are hidden when no ratings exist, and clicking ratings now opens only the ratings for the selected channel.
Original PR description
**PURPOSE** In livechat, rating emojis(happy, neutral and sad) display with percentage of how happy visitors are with the particular channel, click on that will show all ratings of livechat channels and stat button is visible while creation, if it has no rating. **SPECIFICATION** Add one computed field "rating_count" for the model 'rating.parent.mixin' which shows the total rating amount of a particular channel and based on that field invisible the stat button when the count is 0. Also, display only happy face emoji with the percentage of happiness on the kanban view of livechat channel, click on that will only display ratings of the particular channel. Task- 2471714
Planning screens now show clearer guidance about shifts and employee schedules. The email planning form and shift dates were made easier to read, and planning lookups now focus on a shorter recent period for faster, more relevant results.
Original PR description
Generic Improvements In this commit: - changed the helper message in schedule and my planning menus - In send planning by email form: - changed the arrow for Period field - add many2many_avatar_employee widget for the employee_ids field - reduce the nb of days taken into account by the group_expand from 30 days to 7 days TaskId: 2531446
Field service teams can now send task reports in batches instead of opening each task individually. The update skips tasks without report content, shows a clear notification when nothing can be sent, and improves report layout and button visibility.
Original PR description
Currently, send report is only available in the form view of the fsm task so purpose of the task is to support the send report in batch so in this commit, did the below changes: - worksheet report: hide the contact label if the user_id is false - make the 'send report' action work in batch - skip tasks for which worksheet_template_id is false or that have no worksheet, no timesheets, and no products - display a yellow toast notification when there is no report to send that states: "There are no reports to send. - form view: display the 'send report' and the 'sign report' buttons at the same time TaskID: 2579394
This update improves day-to-day Helpdesk workflows by making website forms publish correctly, opening edits in the right app, and keeping sales information when creating field service tasks. It also improves administration with clearer settings, better list organization, kanban views, and archive options for helpdesk records.
Original PR description
…nts in helpdesk Currently, in the helpdesk module, - fsm integration: the sale_line_id set on the ticket is not propagated to the fsm task - after publishing the website, clicking on the edit button…
…nts in helpdesk Currently, in the helpdesk module, - fsm integration: the sale_line_id set on the ticket is not propagated to the fsm task - after publishing the website, clicking on the edit button opens the helpdesk form under website instead of the helpdesk app - sla tags on tickets: currently when we click on the tags, the color picker dropdown is shown - in settings: when enabling the 'website form' feature, the helpdesk team is not published by default on the website - in settings: team members: there is a 'keep empty...' label in the description of the feature and the field is not required - the kanban view is not implemented in the helpdesk team, stages, and sla policies menus - the helpdesk.tag, helpdesk.ticket.type and helpdesk.stage does not have any active field and corresponding archive filter So in this commit, - I have propagated the sale_line_id set on the ticket to the fsm task - clicking on the edit button opens the helpdesk form view under the helpdesk app instead of the website one - the sla tags are not clickable, so the color cannot be modified - when enabling the 'website form' feature, the helpdesk team is now published by default on the website - inside settings: team members: the 'keep empty...' label is removed from the description of the feature and the field is marked required now - the kanban view is implemented for the helpdesk team, stages, and sla policies menus - added active field and corresponding archived filter in the helpdesk.tag, helpdesk.ticket.type and helpdesk.stage TaskID: 2464407
Resolved issues and error corrections
This fixes an issue where filtered Kanban columns could incorrectly appear empty after a card was moved to another stage. Users can now move records while filters are active and still see accurate remaining records and activity counters.
Original PR description
Currently, In kanban state when we filter the record and move it to another stage, then the previous column counter drops to zero and remaining records are not displaying So in this commit, if we move the record to other stage then the previous column records which are not match to current filter are displayed TaskId: 2454209 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
Miscellaneous changes
When selling several times a product in a POS, if the volume and weight of this product are defined, the sales report will be incorrect To reproduce the error: 1. Create a product P: - Product Type: Consumable - Available in POS: True - Weight: 1 - Volume: 1 2. Start a POS session 3. Sell 3 x P 4. Sell 1 x P 5. In Sales > Reporting > Sales, select the pivot view 6. Remove all filters and add this one: - Product Variant: P 7. In Measures, select "Gross Weight"
Original PR description
When selling several times a product in a POS, if the volume and weight of this product are defined, the sales report will be incorrect To reproduce the error: 1. Create a product P: - Product Type:…
When selling several times a product in a POS, if the volume and weight
of this product are defined, the sales report will be incorrect
To reproduce the error:
1. Create a product P:
- Product Type: Consumable
- Available in POS: True
- Weight: 1
- Volume: 1
2. Start a POS session
3. Sell 3 x P
4. Sell 1 x P
5. In Sales > Reporting > Sales, select the pivot view
6. Remove all filters and add this one:
- Product Variant: P
7. In Measures, select "Gross Weight" and "Volume"
Error: Total weight and volume are incorrect, they are equal to 8
instead of 4
For each POS order line, an SQL request computes several fields to
generate the associated sale report. Among them, here is how the volume
is computed:
https://github.com/odoo/odoo/blob/056246665f02c331ba0589618cf030482709f1da/addons/pos_sale/report/sale_report.py#L60-L63
So, let's say we are generating the sale report associated with the POS
order line of step 3. Since there are not enough constraints in the
volume calculation, the SQL request will select all POS order lines with
product P (even those associated with other orders than the one in step
3) and add up all the volumes. Therefore, the volume of the sale report
associated with the POS order line from step 3 will be `3 + 1 = 4` which
is incorrect (it should be 3). Same thing will happen with the sale
report associated with the POS order line of step 4 (its volume will be
4 instead of 1). As a result, on pivot view, the volume displayed will
be the sum of these values, i.e. `4 + 4 = 8`, which is incorrect
The nested SQL request is actually useless and the volume can be
directly computed.
The problem is the same with the weight.
OPW-2527163
Forward-Port-Of: odoo/odoo#72845Fixed an issue in Planning where the “Open Shifts” row was unavailable when sample data was shown. Users can now create a new shift from that row even before real planning data exists, making setup smoother.
Original PR description
BUG Since odoo/enterprise@44f6134, the "Open Shifts" empty line is disabled when sample data is displayed. This prevents people from creating a new shift from this empty line. IMPLEMENTED FIX The sampla data target selector for the planning gantt renderer has been adapted to ensure the "Open Shifts" empty line does not get disabled in sample data mode.
When a custom module is in 'to upgrade' state, and the new version has a new dependency that is not yet installed, Odoo refuses to upgrade it, and says the new dependency is unmet. This commit fixes this by calling button_upgrade() in this situation too, so as to recursively mark all dependencies for upgrade/installation. This situation arises in a version migration scenarios. Custom modules are in 'to upgrade' state when the database comes back from the Odoo migration service. If one of t
Original PR description
When a custom module is in 'to upgrade' state, and the new version has a new dependency that is not yet installed, Odoo refuses to upgrade it, and says the new dependency is unmet. This commit fixes this by calling button_upgrade() in this situation too, so as to recursively mark all dependencies for upgrade/installation. This situation arises in a version migration scenarios. Custom modules are in 'to upgrade' state when the database comes back from the Odoo migration service. If one of these custom modules has a new dependency after migration, it refuses to upgrade. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#72661