Company's Customer Group ID is not assigned to company admin's Customer Group Id when company admin is changed

[zhovnirigor]

Preconditions and environment

• Magento version 2.4.8
• B2B module is installed
• Two Shared Catalogs are created: Shared Catalog One, Shared Catalog Two
• Two Companies are created: Company One, Company Two. Company One is assigned to Shared Catalog One, Company Two - to Shared Catalog Two (in other words, Shared Catalog One is selected as Customer Group for Company One etc).
• Customer John Doe john.doe@example.com is created and assigned to Company One.
• Customer John Doe is NOT an admin of Company One (just a company user).

Steps to reproduce

1. All actions below are done in admin panel.
2. Edit Company Two (Customers -> Companies -> find and edit Company Two).
3. In Company Admin tab, Email field, enter john.doe@example.com
4. Save Company Two.

Expected result

In customer_entity table, john.doe@example.com customer has group_id which equals to Shared Catalog Two.
As a result, tier prices, category permissions etc for John Doe are based on Shared Catalog Two customer group

Actual result

In customer_entity table, john.doe@example.com customer still has group_id which equals to Shared Catalog One. It didn't change after John Doe became an admin of Company Two.
As a result, tier prices, category permissions etc for John Doe are based on Shared Catalog One customer group. There is no clue about this situation for the admin use as in the admin panel Shared Catalog Two is displayed as a John Doe's customer group, which is not true.

Additional information

It happens due to the old company being default in company_advanced_customer_entity. However, it makes sense to have the Company Two as a default one since it is the company customer is an admin of.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @zhovnirigor. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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.

[engcom-November]

Hello @zhovnirigor ,

Thank you for your report and collaboration.

We attempted to reproduce the issue in the latest 2.4-develop instances by following the provided steps and preconditions. We are able to reproduce the issue. Please refer to the attached screenshot for details.

Steps to Reproduce:
All actions below are done in admin panel.
Edit Company Two (Customers -> Companies -> find and edit Company Two).
In Company Admin tab, Email field, enter john.doe@example.com
Save Company Two.

Therefore, we are marking this ticket as "Issue: Confirmed."

Thank you!

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-14897 is successfully created for this GitHub issue.