[19.0][MIG] purchase_order_line_deep_sort: Migration to 19.0 - #3152
Open
CarlosRoca13 wants to merge 18 commits into
Open
[19.0][MIG] purchase_order_line_deep_sort: Migration to 19.0#3152CarlosRoca13 wants to merge 18 commits into
CarlosRoca13 wants to merge 18 commits into
Conversation
…er lines are created directly
Currently translated at 100.0% (22 of 22 strings) Translation: purchase-workflow-15.0/purchase-workflow-15.0-purchase_order_line_deep_sort Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-purchase_order_line_deep_sort/es/
Member
|
/ocabot migration purchase_order_line_deep_sort |
CarlosRoca13
force-pushed
the
19.0-MIG-purchase_order_line_deep_sort
branch
from
August 19, 2026 10:49
f0cc302 to
39ebd10
Compare
juancarlosonate-tecnativa
approved these changes
Aug 20, 2026
juancarlosonate-tecnativa
left a comment
Contributor
There was a problem hiding this comment.
LGTM, just a couple of minor questions: maybe the feature should go in a separate IMP for possible backports? And shouldn't it be documented in DESCRIPTION instead of ROADMAP? Thanks!
…nd note lines Section, subsection and note lines are no longer part of the automatic sorting: they stay pinned where the user placed them, and the sorting criteria is only applied to the product lines inside each block. This way the order can still be grouped in sections without the automatic sorting breaking that grouping, which is what happened so far, as sections were sorted like any other line. As a side effect, the sorting criteria is no longer restricted to stored fields: the value is now resolved through the ORM instead of relying on the column type, so computed fields can be used as well.
CarlosRoca13
force-pushed
the
19.0-MIG-purchase_order_line_deep_sort
branch
from
August 21, 2026 06:59
39ebd10 to
c4d06d2
Compare
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cc @Tecnativa TT64120
Feature added: Section, subsection and note lines are no longer part of the automatic sorting: they stay pinned where the user placed them, and the sorting criteria is only applied to the product lines inside each block. This way the order can still be grouped in sections without the automatic sorting breaking that grouping, which is what happened so far, as sections were sorted like any other line.
ping @sergio-teruel @juancarlosonate-tecnativa