Daily updates from Odoo
Navigate
Branch
Tuesday, March 24, 2020
9 changes
Enhancements to existing features
Planning kanban cards now show a user-slash icon when a slot has no employee assigned, instead of the previous camera icon. The hover text also says "Unassigned," making staffing gaps easier to recognize at a glance.
Original PR description
If there are no employee selected for a slot, show user-slash icon instead of camera icon. Add 'Unassigned' in hover. Task ID 2221250
Company and settings forms now show localization fields only to users for the relevant country. This reduces clutter and confusion for businesses operating outside those local requirements, while also adjusting related Argentine invoicing view references after underlying field changes.
Original PR description
<b>Task:</b> https://www.odoo.com/web?#id=2049977&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 <b>Pad:</b> https://pad.odoo.com/p/r.e20dfeb073ab9b4ba1fd559834032724
Users can now move a shift into a task section in the Gantt view even when that task belongs to a different project. The shift is automatically transferred to the task's project, reducing manual corrections and keeping planning data consistent.
Original PR description
If the user drags & drops a shift under a task section (in Gantt view) which is not part of the project already set on the shift, transfer the shift to the new task's project. Task ID: 2212327
Graph views are now easier to read on mobile devices when they contain many data points. Users can scroll horizontally instead of having all content squeezed into a small screen, keeping labels and values legible.
Original PR description
Purpose The graph view is not readable on mobile when there's too many datas. There's no scroll so everything tries to fit in a super small screen. This task aim to improve the readability of the Graph View on small devices. Specifications Add an horizontal scroll to the Graph view on mobile and define a min-width for each row: the text and the data should stay readable. LINKS: PR #9387 Task-id 1962669
Resolved issues and error corrections
Projects created from a helpdesk team now receive the correct billable setting. This helps ensure time tracking and customer billing behavior matches the team configuration, reducing manual corrections.
Original PR description
The allow_billable value wasn't set correctly when a project was created from a helpdesk team. Task-2199650
Code cleanup and technical improvements
Email, SMS, and related communication templates now use a shared rendering service instead of separate internal paths. This simplifies maintenance and keeps link handling and shortening consistent across affected business apps, with no intended change for end users.
Original PR description
PURPOSE Merge rendering tools used in mail and sms templates and move them directly in mail.render.mixin SPECIFICATIONS Clean rendering methods API and calls. Ensure they are private. Improve naming and docstrings to ease understanding. Move rendering methods on mail.render.mixin. It makes no senss to have to create a void mail.template recordset just to invoke jinjna rendering engine. Now rendering will be available * either directly through inherit; * either by calling env['mail.render.mixin']._render_template(); Move local to global links convertion as well as links shortening tool methods on mail.render.mixin . That way this mixin holds tools related to rendering and its post-processing. This impacts mail.template, sms.template and mailing.mailing as side effect without any functional change. LINKS Task ID 1963529 Community PR odoo/odoo#32397 Enterprise PR odoo/enterprise#8634 Upgrade PR odoo/upgrade#911
CRM lead and sales team fields now update through a more consistent stored-field approach instead of separate onchange/default logic. This should preserve existing behavior while making lead assignment, conversion flows, and website CRM scoring easier to maintain and more reliable.
Original PR description
PURPOSE Try to move from onchange / default_get to stored editable computed fields. Behavior should be the same (computed or set by user), with support of create / write / onchange field update…
PURPOSE Try to move from onchange / default_get to stored editable computed fields. Behavior should be the same (computed or set by user), with support of create / write / onchange field update without additional code. USE EDITABLE STORED FIELDS Update classic fields updated in some cases by onchange and/or default methods by fields with store=True, readonly=False. It means their value comes either from manual user input, either from trigger based computation. Remove onchange and default_get when possible, leading to an unique computation method and clearing fields definition. Also clean some fields definition inconsistencies, notably required fields that should instead be correctly computed or default that have no real meaning. CLEAN MODELS IN WEBSITE CRM SCORE Purpose of this merge is also to clean models in website crm score. Future tasks will improve the use of sales team in crm and first steps is to clean a bit models linked to sales team. LINKS Task ID 2088565 (crm: from onchange to compute) Community PR odoo/odoo#41955 Enterprise PR odoo/enterprise#7322 Upgrade PR odoo/upgrade#781
Miscellaneous changes
Steps to reproduce: - install helpdesk - make sure you have multiple companies selected - go to helpdesk > tickets > all tickets > create - add a name and leave the team blank Previous behavior: the list is empty Current behavior: the list shows the teams related to the selected companies opw-2221541 Forward-Port-Of: odoo/enterprise#9402
Original PR description
Steps to reproduce: - install helpdesk - make sure you have multiple companies selected - go to helpdesk > tickets > all tickets > create - add a name and leave the team blank Previous behavior: the list is empty Current behavior: the list shows the teams related to the selected companies opw-2221541 Forward-Port-Of: odoo/enterprise#9402
### Issue - Admin => UTC+1 - Install CRM - Create a lead at midnight - Check it in cohort view If date = 23/03/2020 it will be 22/03/2020 (UTC) ### Cause We disabled the timezone conversion for a bug which seems not present anymore ### Solution Remove `with_context(tz=False)` **OPW-2178724** Forward-Port-Of: odoo/enterprise#9424
Original PR description
### Issue - Admin => UTC+1 - Install CRM - Create a lead at midnight - Check it in cohort view If date = 23/03/2020 it will be 22/03/2020 (UTC) ### Cause We disabled the timezone conversion for a bug which seems not present anymore ### Solution Remove `with_context(tz=False)` **OPW-2178724** Forward-Port-Of: odoo/enterprise#9424