Daily updates from Odoo
Monday, June 15, 2020
3 changes · master
Enhancements to existing features
A new timer bar makes it easier for users to start, track, and enter timesheets, including support for quicker keyboard-based entry. The timer functionality is now available as an Enterprise component and integrates with related service, field service, and sales timesheet workflows.
Original PR description
Ease the onboarding of the Timesheets app Ease the encoding of Timesheets using the timer and keyboard keys Move timer to enterprise TaskId: 2217930
Manufacturing teams can now edit production orders more easily from list views and define operations directly on the Bill of Materials screen. The update also streamlines how work orders, serial or lot production, back-orders, and quality steps are handled, reducing extra navigation and manual steps.
Original PR description
Ease manufacturing order edition in allowing to edit in the tree view. Consider that one manufacturing order = 1LN/SN and create back-orders in case several of them should be produced in the same MO. Ease definition of operations and their different steps by allowing to do it in the same BoM screen. joint work Simon Lejeune sle@openerp.com joint work Arnold Moyaux arm@odoo.com joint work William Henrotin whe@odoo.com joint work =?UTF-8?q?R=C3=A9my=20Voet=20=28ryv=29?= ryv@odoo.com joint work yhu-odoo yhu@odoo.com joint work "Tiffany Chang (tic)" tic@odoo.com task-2241471
Code cleanup and technical improvements
This refactor rewrites key messaging areas such as Discuss, chatter, chat windows, and the messaging menu while aiming to keep day-to-day behavior mostly unchanged. It modernizes the underlying interface code to make future improvements easier and more consistent across Odoo apps.
Original PR description
This commit is a significant rewriting of client-side discuss, chatter, chat window, and messaging menu using OWL. The behavior should be broadly the same, with some slight functional changes here…
This commit is a significant rewriting of client-side discuss, chatter, chat window, and messaging menu using OWL. The behavior should be broadly the same, with some slight functional changes here and there. From a technical standpoint, the code of messaging is mainly organized in 2 main groups of modules: - models, which are logical entities that depict the client-side state of messaging as a whole. - components, which are in charge of displaying information from models. This refactoring also introduces new JS guidelines regarding folder structure (/static) and naming rules for JS modules. Community PR: odoo/odoo#39023 Enterprise PR: #6249 Task-1914207 This PR is a collaborative work by Alexandre, Julien, Sébastien and Xavier, with the precious help of Lucas to speed it up towards the end. Co-authored-by: Alexandre Kühn <aku@odoo.com> Co-authored-by: Julien Giannone <jgi@odoo.com> Co-authored-by: Lucas Perais <lpe@odoo.com> Co-authored-by: Sébastien Theys <seb@odoo.com> Co-authored-by: Xavier Dubuc <xdu@odoo.com>