Friday, December 11, 2020
6 changes · master
Enhancements to existing features
The Calendar app gets a refreshed interface that makes meeting status and attendance easier to understand at a glance. Organizers, attendee filters, invitations, and event display behavior are improved so users can manage meetings more reliably and with less confusion.
Original PR description
Description of the issue/feature this PR addresses: Improve the quality of the Calendar application by updating the User Interface and improving the User Experience. Task ID 2196775 Current behavior before PR: Desired behavior after PR is merged: See specs -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Module installations and upgrades now show shorter, more focused error messages when an XML view is broken. This helps developers identify the problem faster by showing the relevant file and nearby lines instead of long internal tracebacks.
Original PR description
When installing/upgrading a module with broken xml views, the module installation fails with an error message that should help the developer locate and correct the error. Before this commit, a…
When installing/upgrading a module with broken xml views, the module installation fails with an error message that should help the developer locate and correct the error. Before this commit, a 3-level traceback was thrown at the developer: 1. The initial ValueError containing the original error message and some view context information. 2. The noisy re-cast of the ValueError to a ValidationError with no additionnal information. 3. An additionnal re-cast of the exception to add the original source file path plus the entire XML source code that failed to be parsed. We argue the error contains too much noise as developers are mostly interrested in correcting their erronous tag of their view, they are not interrested in `ir_ui_view` internals. The new exception report is much less talkative, the two tracebacks from `ir_ui_view` are logged at the `DEBUG` level. The new exception still contains the original error message with some context on the view record and the original source file path but it only show 5 lines of XML around the erronous tag. Task: 2366612 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
The quick create card in Kanban views now keeps its action buttons on one line, even in languages with longer translations. The Discard action is shown as a compact grey trash icon, reducing visual clutter and preventing awkward wrapping.
Original PR description
PURPOSE All buttons of the quick create kanban card fit in a single row in all languages. SPECIFICATIONS Current While everything looks nice and tidy in English. The layout of our quick create cards quickly suffers once one switches to another language for which those words are longer. To be Replace the Discard button by a thrash button in grey and aligned on the right Add some css to make sure the 3 buttons always fit in a single line => if not, crop LINKS PR Task 2373130 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Error reports shown during module installation or upgrades are now shorter and easier to act on when XML views are broken. Instead of overwhelming users with long internal tracebacks and full XML content, the message highlights the original problem, file location, and nearby lines needed to fix it.
Original PR description
When installing/upgrading a module with broken xml views, the module installation fails with an error message that should help the developer locate and correct the error. Before this commit, a…
When installing/upgrading a module with broken xml views, the module installation fails with an error message that should help the developer locate and correct the error. Before this commit, a 3-level traceback was thrown at the developer: 1. The initial ValueError containing the original error message and some view context information. 2. The noisy re-cast of the ValueError to a ValidationError with no additionnal information. 3. An additionnal re-cast of the exception to add the original source file path plus the entire XML source code that failed to be parsed. We argue the error contains too much noise as developers are mostly interrested in correcting their erronous tag of their view, they are not interrested in `ir_ui_view` internals. The new exception report is much less talkative, the two tracebacks from `ir_ui_view` are logged at the `DEBUG` level. The new exception still contains the original error message with some context on the view record and the original source file path but it only show 5 lines of XML around the erronous tag. Task: 2366612
Helpdesk teams can now create field service interventions in the right default project and automatically use the customer delivery address. Teams can also choose the correct worksheet when creating an intervention, helping field staff receive the right instructions and documentation.
The Gantt view now displays more cleanly on small screens, with better scrolling and a simpler range selector. This makes planning schedules easier to review and navigate from mobile devices.
Original PR description
Before, gantt view on a small screen looks very weird. Now, gantt view looks properly in a small screen with scrolling and better range button UI with dropdown selection Task ID: 2053857