[FIX] base: match server actions visual sort with execution#247232
Closed
jeromebelpaire wants to merge 1 commit intoodoo:masterfrom
Closed
Conversation
Contributor
|
|
C3POdoo
requested review from
a team,
rco-odoo and
rugo-odoo
and removed request for
a team
std-odoo
approved these changes
Feb 5, 2026
Contributor
|
@jeromebelpaire @std-odoo linked pull request(s) odoo/upgrade#9044 not ready. Linked PRs are not staged until all of them are ready. |
jeromebelpaire
force-pushed
the
master-imp-documents-accounting-improve-server-actions-and-demo-documents-beje
branch
from
92bb8fa to
b8856de
Compare
Contributor
|
@robodoo r+ |
Currently, the server actions Kanban view implicitly sorts records by sequence and then by ID. This behavior is triggered automatically by the web client when a field with the 'handle' widget is present and no default order is specified in the view. However, the backend execution logic for multi-actions (ir.actions.server) processes actions based on 'sequence' and then 'name' (alphabetical). This creates a discrepancy when multiple actions share the same sequence number: the user sees them sorted by creation order (ID) in the interface, but they are executed alphabetically. This leads to confusion as the visual hierarchy does not accurately represent the flow of operations. This commit ensures the view aligns with the backend model's sorting logic, so that the visual order in the frontend matches the actual execution order. Task-5075610
std-odoo
force-pushed
the
master-imp-documents-accounting-improve-server-actions-and-demo-documents-beje
branch
from
b8856de to
320891a
Compare
Contributor
|
@robodoo r+ |
robodoo
pushed a commit
that referenced
this pull request
Feb 12, 2026
Currently, the server actions Kanban view implicitly sorts records by sequence and then by ID. This behavior is triggered automatically by the web client when a field with the 'handle' widget is present and no default order is specified in the view. However, the backend execution logic for multi-actions (ir.actions.server) processes actions based on 'sequence' and then 'name' (alphabetical). This creates a discrepancy when multiple actions share the same sequence number: the user sees them sorted by creation order (ID) in the interface, but they are executed alphabetically. This leads to confusion as the visual hierarchy does not accurately represent the flow of operations. This commit ensures the view aligns with the backend model's sorting logic, so that the visual order in the frontend matches the actual execution order. Task-5075610 closes #247232 Related: odoo/enterprise#97362 Related: odoo/upgrade#9044 Signed-off-by: Stéphane Debauche (std) <std@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Feb 12, 2026
Currently, the server actions Kanban view implicitly sorts records by sequence and then by ID. This behavior is triggered automatically by the web client when a field with the 'handle' widget is present and no default order is specified in the view. However, the backend execution logic for multi-actions (ir.actions.server) processes actions based on 'sequence' and then 'name' (alphabetical). This creates a discrepancy when multiple actions share the same sequence number: the user sees them sorted by creation order (ID) in the interface, but they are executed alphabetically. This leads to confusion as the visual hierarchy does not accurately represent the flow of operations. This commit ensures the view aligns with the backend model's sorting logic, so that the visual order in the frontend matches the actual execution order. Task-5075610 closes #247232 Related: odoo/enterprise#97362 Related: odoo/upgrade#9044 Signed-off-by: Stéphane Debauche (std) <std@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Feb 12, 2026
Currently, the server actions Kanban view implicitly sorts records by sequence and then by ID. This behavior is triggered automatically by the web client when a field with the 'handle' widget is present and no default order is specified in the view. However, the backend execution logic for multi-actions (ir.actions.server) processes actions based on 'sequence' and then 'name' (alphabetical). This creates a discrepancy when multiple actions share the same sequence number: the user sees them sorted by creation order (ID) in the interface, but they are executed alphabetically. This leads to confusion as the visual hierarchy does not accurately represent the flow of operations. This commit ensures the view aligns with the backend model's sorting logic, so that the visual order in the frontend matches the actual execution order. Task-5075610 closes #247232 Related: odoo/enterprise#97362 Related: odoo/upgrade#9044 Signed-off-by: Stéphane Debauche (std) <std@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Feb 12, 2026
Currently, the server actions Kanban view implicitly sorts records by sequence and then by ID. This behavior is triggered automatically by the web client when a field with the 'handle' widget is present and no default order is specified in the view. However, the backend execution logic for multi-actions (ir.actions.server) processes actions based on 'sequence' and then 'name' (alphabetical). This creates a discrepancy when multiple actions share the same sequence number: the user sees them sorted by creation order (ID) in the interface, but they are executed alphabetically. This leads to confusion as the visual hierarchy does not accurately represent the flow of operations. This commit ensures the view aligns with the backend model's sorting logic, so that the visual order in the frontend matches the actual execution order. Task-5075610 closes #247232 Related: odoo/enterprise#97362 Related: odoo/upgrade#9044 Signed-off-by: Stéphane Debauche (std) <std@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Feb 12, 2026
Currently, the server actions Kanban view implicitly sorts records by sequence and then by ID. This behavior is triggered automatically by the web client when a field with the 'handle' widget is present and no default order is specified in the view. However, the backend execution logic for multi-actions (ir.actions.server) processes actions based on 'sequence' and then 'name' (alphabetical). This creates a discrepancy when multiple actions share the same sequence number: the user sees them sorted by creation order (ID) in the interface, but they are executed alphabetically. This leads to confusion as the visual hierarchy does not accurately represent the flow of operations. This commit ensures the view aligns with the backend model's sorting logic, so that the visual order in the frontend matches the actual execution order. Task-5075610 closes #247232 Related: odoo/enterprise#97362 Related: odoo/upgrade#9044 Signed-off-by: Stéphane Debauche (std) <std@odoo.com>
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
3 participants
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.
Currently, the server actions Kanban view implicitly sorts records by sequence and then by ID. This behavior is triggered automatically by the web client when a field with the 'handle' widget is present and no default order is specified in the view.
However, the backend execution logic for multi-actions (ir.actions.server) processes actions based on 'sequence' and then 'name' (alphabetical).
This creates a discrepancy when multiple actions share the same sequence number: the user sees them sorted by creation order (ID) in the interface, but they are executed alphabetically. This leads to confusion as the visual hierarchy does not accurately represent the flow of operations.
This commit ensures the view aligns with the backend model's sorting logic, so that the visual order in the frontend matches the actual execution order.
Task-5075610