[Issue] Moving admin export form to Ui components

[m2-assistant]

This issue is automatically created based on existing pull request: #28188: Moving admin export form to Ui components

---

Description

Admin export form (System > Export) has been moved from blocks to Ui components.

The Pull Request adds the following Ui components:

1. Magento_ImportExport::view/adminhtml/ui_component/export_form.xml
2. Magento_ImportExport::view/adminhtml/ui_component/export_filter_grid.xml

Manual testing scenarios

1. Go to the admin export page - System > Export
2. Make sure all elements of the Ui form are correctly loaded, there are no errors in the console
3. Choose Entity Type = Products, make sure grid with the product attributes is loaded without issues
4. Check the sort and filter features of the grid - all should be fine there
5. Export products through the button Continue below the grid, make sure the export was successful

Notes

• All old php classes/layouts/phtml templates were marked as deprecated
• Broken mftf selectors were fixed to make tests green
• All new php classes were covered by unit tests

[engcom-Bravo]

Hi @elevinskii,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Manual testing scenarios

• Go to the admin export page - System > Export
• Make sure all elements of the Ui form are correctly loaded, there are no errors in the console
• Choose Entity Type = Products, make sure grid with the product attributes is loaded without issues
• Check the sort and filter features of the grid - all should be fine there
• Export products through the button Continue below the grid, make sure the export was successful

We are able to export the related product CSV file.

Kindly recheck the issue in Latest Magento 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

[engcom-Bravo]

Hi @elevinskii,

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.