Daily updates from Odoo
Navigate
Branch
Friday, January 4, 2019
6 changes
Enhancements to existing features
This update aligns how unit price conversions are calculated with the existing quantity conversion behavior. It is a small internal improvement that makes unit-of-measure handling more consistent and easier to maintain.
Original PR description
Description of the issue/feature this PR addresses: Little IMP regards -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This fixes an issue where the backend interface could incorrectly use website color settings after a recent change. The update keeps editor-specific colors available while preventing website colors from overriding the standard backend look, preserving a consistent user experience.
Original PR description
Commit https://github.com/odoo/odoo/commit/52ec536cef2ec84af0b36746f19a8cdf9f23fe2a made a mistake which made the backend use the website colors. This is because the web_editor app adds its bootstrap_overridden.scss file in both backend and frontend assets as the backend needs the editor colors (alpha, beta, ...). However, the 'primary', 'secondary', etc that the backend customizes should not be overridden by the web_editor. Therefore the file contained a hack to determine if it is the backend or not... hack which did not work anymore with the new system the mentioned commit implements. Also some comments were not adapted correctly by the mentioned commit.
This fixes a small typo in the Time Off module that could cause leave records to show the wrong visual status indicator. It helps users see the correct state of leave requests more reliably, with no change to business processes.
Original PR description
A type on XML declaration that lead to incorrect decoration
Administrators can now trigger recalculation of stored custom computed fields after changing their calculation logic. This helps ensure existing records reflect the latest field rules without manual workarounds or developer intervention.
Original PR description
**Description of the issue/feature this PR addresses:** It is an helper for developper using web UI to create a custom computed stored field. When you create an custom computed stored field, stored data are computed only once at the creation. if you update the python code, there no solution to force the re-compute with the last python code. **Current behavior before PR:** -create a custom computed stored field, with good python code (no raise) -save -update the python code for any reason and save --> stored data have NOT updated with the last python code **Desired behavior after PR is merged:** Add a button to recompute.  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
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.
This update renames the configuration used to track field changes across several Odoo apps, making the setting simpler and more consistent. Existing behavior remains compatible, so businesses should see no disruption while benefiting from cleaner, more maintainable tracking setup.
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 merge we rename the track_visibility parameter to tracking and we make it a real boolean parameter. We also update all addons to use the new tracking parameter in some separate commits. Old parameter value is still supported in mail tracking mechanism for backward compatibility. Commit https://github.com/odoo/odoo/commit/ec35eca7c6b772139c8fa143b388ad1d936bc9ea added sequence on tracking so that display of tracking values is coherent through various chatter messages. To match the track_visibility renaming it is renamed to tracking_sequence to remain coherent. This merge is linked to task ID 1903814. This merge is linked to community PR https://github.com/odoo/odoo/pull/28430.