Select all orders selecting orders which are not visible in order grid.

[shachiarkatkar]

Preconditions (*)

1. Magento 2.2.5
2. Php 7.0

Steps to reproduce (*)

1. Go to order grid
2. Select all orders on that page
3. Place an order
4. Without refreshing page move all orders to hold or any other status
5. Check updated order status for new order

Expected result (*)

1. Only the order selected should be updated

Actual result (*)

1. All orders including those which are not visible in order grid are moved to new status.
   Order grid before updating status
   
   Order grid after putting order on hold
   

[magento-engcom-team]

Hi @shachiarkatkar. 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-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[shachiarkatkar]

@magento-engcom-team give me 2.2.5 instance

[magento-engcom-team]

Hi @shachiarkatkar. Thank you for your request. I'm working on Magento 2.2.5 instance for you

[magento-engcom-team]

Hi @shachiarkatkar, here is your Magento instance.
Admin access: http://ec2-34-228-235-121.compute-1.amazonaws.com/i-18983-2-2-5//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[shachiarkatkar]

@magento-engcom-team the error replicated on vanilla instance

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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-engcom-team 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-engcom-team 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.

Hi @shachiarkatkar thank you for you report, this issue has already fixed in 2.2-develop and 2.3-develop

branch

[shachiarkatkar]

@engcom-backlog-nazar can you give commit number here please

@shachiarkatkar might be this commit -> https://github.com/magento/magento2/pull/18377/files

@shachiarkatkar #14629

[shachiarkatkar]

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