[Issue] fix for ambigous column user_id in where clause

[m2-assistant]

This issue is automatically created based on existing pull request: #31205: fix for ambigous column user_id in where clause

---

Magento\Users\Model\ResourceModel\User\Collection addFilterToMap for user_id

Description (*)

When filtering Magento\Users\Model\ResourceModel\Users\Collection by user_id , it throws an SQL exception ( ambigous user_id in where condition )

Preconditions:

Magento version: 2.4-develop
PHP version: 7.4
ElasticSearch version: 7
MySQL version: 8.0

Manual testing scenario:

1. Add the code from the attached file
   Code_to_reproduce_31205.zip
2. Run in console: php bin/magento setup:upgrade;
3. Log in to the admin panel;
4. open URL /admin/column;

Actual Result: ✖️ 2 exceptions occur

Expected Result: ✔️ No exceptions

[engcom-Hotel]

Not able to reproduce the issue.
M2.4
Steps:

1. Create a few admin users;
2. Open admin panel and sort admin users by ID at grid "System > Permissions > All users grid"
   

Works as expected. Could you please provide additional information to reproduce the issue?
Thank you.

[m2-assistant]

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

[aleron75]

Hi @engcom-Hotel

Works as expected. Could you please provide additional information to reproduce the issue?

Same for me but I managed to reproduce it programmatically as stated here: #31205 (comment)

[engcom-Hotel]

Hello @aleron75,
Yes, it helps to reproduce the issue.
Thank you.
Detailed steps to reproduce #31205 (comment)

[magento-engcom-team]

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

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