Thursday, July 29, 2021
3 changes · master
Enhancements to existing features
Several reporting screens now include list views, making it easier for users to open detailed records directly from pivot and graph reports. This improves analysis workflows across sales, accounting, purchasing, projects, POS, fleet, timesheets, CRM, membership, and website sales reporting.
Original PR description
PURPOSE currently, there are pivot views on reporting models those do not have a dedicated listview and therefore disabled it. The purpose of this commit is to add those listviews that will allow the user to drill down from the pivot views themselves. SPECIFICATION 1. we have removed 'disabled_linking' attribute from pivot views as listed in pad 2. also, now we have dedicated list views for the following models in reporting - account.invoice.report - fleet.vehicle.cost.report - hr.timesheet.attendance.report - report.pos.order - purchase.report - project.profitability.report - report.project.task.user - sale.report LINKS PR #72394 task-id:2547881
Users can now drill down from key reporting pivot and graph views into clear list views instead of hitting disabled links. This makes reports across HR, sales, helpdesk, field service, and project planning easier to investigate and act on directly from dashboards or spreadsheets.
Original PR description
PURPOSE currently, there are pivot views on reporting models those do not have a dedicated listview and therefore disabled it. The purpose of this commit is to add those list views that will allow the user to drill down from the pivot views themselves. SPECIFICATION 1. we have removed 'disabled_linking' attribute from pivot views as listed in pad 2.also, now we have dedicated list views for the following models in reporting - helpdesk.sla.report.analysis - hr.appraisal.report - hr.contract.employee.report - hr.payroll.report - hr.recruitment.report - hr.referral.report - hr.work.entry.report - project.timesheet.forecast.report.analysis - report.project.task.user..fsm - sale.rental.report - sale.subscription.report LINKS PR #19122 task-id:2547881
Resolved issues and error corrections
Odoo keyboard shortcuts now use the physical key being pressed instead of the character produced by the user's current keyboard layout. This means shortcuts such as Alt+S work consistently for users typing with non-Latin layouts, reducing frustration and layout switching.
Original PR description
Description of the issue/feature this PR addresses: When users work with odoo with local keyboard layout most of shortcuts don't work. This is happened because of hotkey_service uses `event.key` to…
Description of the issue/feature this PR addresses: When users work with odoo with local keyboard layout most of shortcuts don't work. This is happened because of hotkey_service uses `event.key` to determine shortcut. But with non-latin keyboard layout `event.key` is localized. Non-english users have to switch keyboard layout to english to use shortcut, then they have to switch back to enter text. It's annoying. Some users just think that shortcuts in odoo doesn't work at all because they use english layout very rarely. This PR changes hostkey_service so it uses `event.code` to determine pressed key. Current behavior before PR: With non-latin keyboard layout most of shotcuts don't work. F.x. `Alt+S` doesn't work for russian keyboard layout becase hotkey_service interprets this shortcut as `Alt+Ы`. Desired behavior after PR is merged: Shortcuts registered in hotkey_service don't depend on keyboard layout. So pressing `Alt+S` on any keyboard layout will trigger appropriate event listener. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr