Filter in url rewrites table in backend isn't being remembered

[hostep]

Preconditions (*)

1. PHP 7.2.15
2. Magento 2.3.0 (older versions are also affected)

Steps to reproduce (*)

1. Have a vanilla 2.3.0 installed using composer
2. Make sure you have some products in your catalog
3. In the backend, go to Marketing > URL Rewrites
4. Put a filter in one of the columns (like in the Request Path column) and apply it
5. Click on one of the filtered results
6. Click on the Back button

Expected result (*)

1. The filter you entered in the grid should still be there

Actual result (*)

1. The filter you entered in the grid is gone

Discussion

If you do the same on for example the product, customer, order, cms pages, ... grid, it remembers the applied filter. But not in the url rewrites grid unfortunately. Which is not user friendly if you have to manually change a couple of url rewrites based on a certain filter.

[magento-engcom-team]

Hi @hostep. 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 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

[magento-engcom-team]

Hi @shikhamis11. 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

• Next steps are available in case you are a member of Community Maintainers.

• 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 @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98749, MAGETWO-98750 were created

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

[magento-engcom-team]

Hi @hostep. Thank you for your report.
The issue has been fixed in #21834 by @vbmagento in 2.3-develop branch
Related commit(s):

• ae6c8bcff2d8203f7e9b36dad790a90047827b84
• d85fd44346a024cd3f4f61f28dbd50a9ba8074a1
• f75b3e9eba8192fef0116d63832aa375b22a1848
• d5a61c01cec3429d9fb93c1a56b78a264b06ba45

The fix will be available with the upcoming 2.3.2 release.

[magento-engcom-team]

Hi @hostep. Thank you for your report.
The issue has been fixed in #22069 by @amol2jcommerce in 2.2-develop branch
Related commit(s):

• d6c12e5ea2ea391221231bbee8cf6d5094b793f6
• 646200a14003f75e8be34772b9826df4b395b993
• 2a39dd308271ce1699cf64bd5f8c6c10605a0039
• c126f399f0ffc1fe382a37cdf90791beb869bbd6

The fix will be available with the upcoming 2.2.9 release.