Odoo Changelog — 2020-01-23

Thursday, January 23, 2020

3 changes · master

Improvements(2)

Enhancements to existing features

[IMP] mrp: change workorder plan behavior

CoremastermrpMEDIUM

Manufacturing work orders are now planned to avoid unnecessary overlaps between jobs, reducing inefficient task switching on the shop floor. The update also improves schedule conflict detection, required date handling, and work order view usability.

Original PR description

[IMP] mrp: change workorder plan behavior

Before the auto-planning of workorder autorize overlaps between then.
E. g. if a workorder begin in now + 30 min with a duration of 60 minutes
and we try to plan a new workorder now, this one will be plan now
until now + 120 min (30 min + 30 min).
In our case we don't want that this behavior by default,
(because in real case, it is not efficient to work on job A during
30 min, after change to pass to a other job B, and rework on A after
the job B).
But in a other hand, we need to accept overlaps with no-working hours
intervals. Then, rewritte the _plan_workorders method to take
these in account.

[IMP] mrp: improve small details of WO views/model

- Now, the fields date_planned_start and date_planned_finished is
required in views, because it was strongly related to the leave date_to, date_from
which are required.
- Change the name get in case of single WO in MO and replace the dot
by a dash.
- Improve the WO views to be more responsible when it is open from the
gantt view.
- Change name of a Operation in the demo data

[FIX] mrp: truncate millisecond to check overlaps

In some flows, a planned_datetime_start/finished will contains
milliseconds. In these cases, we can detect overlaps/conflicts between
workorders but these conflicts can't be see in the web interface
(because datetime is round when it is display).
Then, change the conflicts computation to remove milliseconds
in search of conflicts.

task-2169447

#manufacturing#work-orders#planning#scheduling

Master multicompany fix jud

PR #7448

Enterprisemasterhr_appraisalindustry_fsm_reportMEDIUM

This update improves how employee appraisals and field service worksheet templates behave when several companies use the same system. It helps ensure users see company-appropriate appraisal information and lets businesses assign worksheet templates to specific companies, reducing mistakes in multi-company operations.

#multi-company#appraisals#field-service#worksheets

Bug Fixes(1)

Resolved issues and error corrections

[FIX] pad: set collaborative pad editor name

PR #43647

Coremasteraccountproductweb_editorwebpayment_stripe_scapayment_payumoneyl10n_be_intrastatMEDIUM

This update fixes several business-facing issues across Odoo, including cleaner price list formatting, more consistent payment records after cancellation, and faster accounting setup checks on large databases. It also improves payment testing links, video autoplay behavior, and progress bar editing stability.

Original PR description

Task: https://www.odoo.com/web#id=2154331&action=327&model=project.task&view_type=form&menu_id=4720
Pad: https://pad.odoo.com/p/r.f9c119c6725985b33681500e5119ce69

#accounting#payments#reporting#performance#translations

[IMP] mrp: change workorder plan behavior Before the auto-planning of workorder autorize overlaps between then. E. g. if a workorder begin in now + 30 min with a duration of 60 minutes and we try to plan a new workorder now, this one will be plan now until now + 120 min (30 min + 30 min). In our case we don't want that this behavior by default, (because in real case, it is not efficient to work on job A during 30 min, after change to pass to a other job B, and rework on A after the job B). But in a other hand, we need to accept overlaps with no-working hours intervals. Then, rewritte the _plan_workorders method to take these in account. [IMP] mrp: improve small details of WO views/model - Now, the fields date_planned_start and date_planned_finished is required in views, because it was strongly related to the leave date_to, date_from which are required. - Change the name get in case of single WO in MO and replace the dot by a dash. - Improve the WO views to be more responsible when it is open from the gantt view. - Change name of a Operation in the demo data [FIX] mrp: truncate millisecond to check overlaps In some flows, a planned_datetime_start/finished will contains milliseconds. In these cases, we can detect overlaps/conflicts between workorders but these conflicts can't be see in the web interface (because datetime is round when it is display). Then, change the conflicts computation to remove milliseconds in search of conflicts. task-2169447