Sortorder on Grid filters doesn't be available or valid with diffirent type of filters: Range vs others

[tuyennn]

Preconditions and environment

• Magento version: All versions

Steps to reproduce

1. Open a ui component xml regarding to any listing grid.

2. Change sortOrder value for colums 1 for textRange and 1 for any of text, select

3. sortOrder of textRange field must be higher than the other one(For example: 100 vs 50)
   

4. Observe the columns or filter order from the grids.

Expected result

• Column or filter of textRange fields should be behind the column or filter of other fields.

Actual result

• Column or filter of textRange fields were always at first.

Additional information

• From https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Ui/view/base/web/templates/grid/filters/filters.html#L22-L23, the ranges filters were hard-coded as always be the first.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @tuyennn. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @tuyennn,

Thank you for the report and collaboration!

Could you add the screenshot of expected and actual screenshot, this will help us in assessing the problem.

[tuyennn]

@engcom-November Updated the actual screenshot. For the expected behavior you might know what I mean if those in red circle could stay behind Name or Email for example.

[engcom-November]

@tuyennn,
Thank you for quick response!

Verified this on 2.4-develop.
Added column with filter text and textRange with sortorders as below

But the filter with textRange ignores sortOrder:

Hence confirming the issue.