Odoo Changelog — 2019-01-04

Friday, January 4, 2019

1 change · master

Refactoring(1)

Code cleanup and technical improvements

[MERGE][REF] mail, various: rename and merge both tracking field parameters

Coremastermailaccountaccount_voucheranalyticcalendarcrmeventfleetgamificationhrhr_contracthr_expensehr_holidayshr_maintenancehr_recruitmentl10n_be_hr_payrolll10n_be_hr_payroll_fleetMEDIUM

This update simplifies how Odoo records and orders field changes shown in chatter by combining two tracking settings into one. It makes configuration easier and more consistent across many business apps, while keeping older settings compatible during the transition.

Original PR description

Track_visibility field parameter allows to track field changes in mail. Since commit c99de45 only updated values are tracked. Previously to that commit it was possible to have field values being…

Track_visibility field parameter allows to track field changes in mail. Since
commit c99de45 only updated values are tracked. Previously to that commit it
was possible to have field values being tracked whenever any other change
occurred. This feature has been removed to simplify tracking and avoid having
unnecessary values in the tracking table. In this commit we rename the
track_visibility parameter to tracking. Old parameter value is still supported
in mail for backward compatibility.

Commit ec35eca added sequence on tracking so that display of tracking values
is coherent through various chatter messages. To ease tracking configuration
it is merged with the tracking (old track_visibility) parameter. It means
tracking parameter can either be True (default sequence of 100) or an integer
giving the sequence to apply on the tracking.

Purpose of those changes is to simplify tracking configuration with studio
in mind. That way changing one parameter allow to customize the tracking of
fields in chatter.

Sequence field on mail.tracking.value model is renamed to tracking_sequence to
have a coherent namespace for tracking information. Tracking information on
ir.model.fields is also updated accordingly. To simplify manipulation boolean
value for tracking is automatically transformed into a sequence of 100.

All addons are updated accordingly.

This merge is linked to task ID 1903814 and PR #28430.

#chatter#field tracking#configuration#studio

Track_visibility field parameter allows to track field changes in mail. Since commit c99de45 only updated values are tracked. Previously to that commit it was possible to have field values being tracked whenever any other change occurred. This feature has been removed to simplify tracking and avoid having unnecessary values in the tracking table. In this commit we rename the track_visibility parameter to tracking. Old parameter value is still supported in mail for backward compatibility. Commit ec35eca added sequence on tracking so that display of tracking values is coherent through various chatter messages. To ease tracking configuration it is merged with the tracking (old track_visibility) parameter. It means tracking parameter can either be True (default sequence of 100) or an integer giving the sequence to apply on the tracking. Purpose of those changes is to simplify tracking configuration with studio in mind. That way changing one parameter allow to customize the tracking of fields in chatter. Sequence field on mail.tracking.value model is renamed to tracking_sequence to have a coherent namespace for tracking information. Tracking information on ir.model.fields is also updated accordingly. To simplify manipulation boolean value for tracking is automatically transformed into a sequence of 100. All addons are updated accordingly. This merge is linked to task ID 1903814 and PR #28430.