Back-End issue for multi-store website: when editing Order shipping/billing address - allowed countries are selected from wrong Store View

[svejegres]

Preconditions

1. Magento 2.1.10 CE & 2.3.x
2. PHP 7.0.22
3. MySQL 5.6

Steps to reproduce

1. Create multi-stores
2. Configure different 'Allow Countries' settings for different stores (Configuration > General > Country Options)
3. Go to Admin > Sales > Orders > Go to any order view page
4. Press "Edit" near Shipping Address: you will see the different values for Country dropdown.

Expected result

1. Address Country drop-down in Admin should take values from 'Allow Countries' setting configured for the Website Store View where that order was made (e.g.: for German store with id = 7)

Actual result

1. But it's picking the 'Allow Countries' from first store View (with id=1).
2. If before steps 3 and 4 from "Steps to reproduce" go to Admin > Sales > Create New Order and when creating it select some different Store View (e.g.: Italian, with id = 10) then actual result after "Steps to reproduce" will show allowed countries for that selected Store View (with id = 10, if continue on example).

---

Similar issue was already mentioned here: #7036
And fixed here.

[magento-engcom-team]

@svejegres, thank you for your report.
We've created internal ticket(s) MAGETWO-85220 to track progress on the issue.

[ishakhsuvarov]

Hi @svejegres
We are closing this issue report now since the fix for the issue is delivered to 2.2-develop (should be released with 2.2.4).
You may check 506d500 for now to get more details on the fix.

Thank you for collaboration.

[DrewRobertson]

I'm still getting this problem on 2.3 CE, PHP 7.3

[g-anedda]

Had this on 2.1, still have this in 2.3.1.

[oleksii-lisovyi]

The issue is not fixed and still is reproducible on Magento 2.3.2.

[m2-assistant]

Hi @engcom-Charlie. 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 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. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

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

Issue Available: @engcom-Charlie, 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 @svejegres. Thank you for your report.
The issue has been fixed in #24345 by @oleksii-lisovyi in 2.3-develop branch
Related commit(s):

• d617c3ca6541d1528bf26c26738b909d55424def
• 883d9f52e1b360b5c3c3b9b9f0a7f512531dfe83

The fix will be available with the upcoming 2.3.4 release.