Skip to content

[19.0][MIG] purchase_order_line_deep_sort: Migration to 19.0 - #3152

Open
CarlosRoca13 wants to merge 18 commits into
OCA:19.0from
Tecnativa:19.0-MIG-purchase_order_line_deep_sort
Open

[19.0][MIG] purchase_order_line_deep_sort: Migration to 19.0#3152
CarlosRoca13 wants to merge 18 commits into
OCA:19.0from
Tecnativa:19.0-MIG-purchase_order_line_deep_sort

Conversation

@CarlosRoca13

@CarlosRoca13 CarlosRoca13 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

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

@OCA-git-bot OCA-git-bot added series:19.0 mod:purchase_order_line_deep_sort Module purchase_order_line_deep_sort labels Aug 19, 2026
@pedrobaeza

Copy link
Copy Markdown
Member

/ocabot migration purchase_order_line_deep_sort

@OCA-git-bot OCA-git-bot added this to the 19.0 milestone Aug 19, 2026
@OCA-git-bot OCA-git-bot mentioned this pull request Aug 19, 2026
80 tasks
@CarlosRoca13
CarlosRoca13 force-pushed the 19.0-MIG-purchase_order_line_deep_sort branch from f0cc302 to 39ebd10 Compare August 19, 2026 10:49

@juancarlosonate-tecnativa juancarlosonate-tecnativa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
CarlosRoca13 force-pushed the 19.0-MIG-purchase_order_line_deep_sort branch from 39ebd10 to c4d06d2 Compare August 21, 2026 06:59
@CarlosRoca13

Copy link
Copy Markdown
Contributor Author

Done @juancarlosonate-tecnativa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:purchase_order_line_deep_sort Module purchase_order_line_deep_sort series:19.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.