Sales Order Grid column ordering not saved properly

[gwharton]

Preconditions (*)

1. magento 2.3-develop vanilla

Steps to reproduce (*)

1. deploy 2.3-develop

Sales -> Orders
    Enable all columns
    Open Browser Development Tools
    Filter network requests for the url string "?isAjax=true"
    Make a note of column orders
    Move a column and note new position
    Verify that there is an "?isAjax=true" call made to the server after column move
    Refresh Page
    Verify column ordering on page after refresh
    Note whether an "?isAjax=true" call is made during page reload
    Repeat Refreshing Page noting column ordering and presence of "?isAjax=true" call

Expected result (*)

1. Column ordering is maintained across page refreshes
2. "?isAjax=true" calls should only be made immediately after column move, not page refresh

Actual result (*)

1. Seemingly randomly chosen columns move on successive page refreshes (not every refresh).
2. "?isAjax=true" calls are made back to the server during page refresh (not every refresh) with incorrect column order
3. The ajax call incorrectly changes column ordering stored on the server. The page then renders the wrong order in accordance with what is set on the server.

Old Issue

magento/magento2 #17691 - Admin Grid column ordering/positioning not working

[m2-assistant]

Hi @gwharton. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@gwharton do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @engcom-Charlie. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-18662 were created

Issue Available: @engcom-Charlie, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[rajeshwebkul]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @sagarwebkul. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @sagarwebkul, here is your Magento instance.
Admin access: https://i-23889-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.