Customer Address fields - impossible to sort correctly & admin area still showing if disabled

[tomekjordan]

Preconditions (*)

1. Any Magento version 2 & 1

Steps to reproduce (*)

1. Any address related pages (checkout page, admin create order)
2. Frontend - user - to add new billing/shipping address
3. Admin user - to add new user billing/shipping address
4. Admin user - to create new order

STILL showing fields sorted by default. ADMIN area also shows disabled fields (for new order creation)

Expected result (*)

1. Proper sorting according to merchant needs and country specific
2. Fields that are disabled like Middlename -should not appear in admin area during new order creation

Actual result (*)

1. Admin > Customer > Address Templates - are not working for it

Examples: In many countires POST CODE should be placed before City, there are also other types needed to match UX or store/user expectations Not only for frontend - but for admin area.

2. Admin - Create Order - even fields are disabled - they show up when admin tries to create order. Order creating is time consuming because you see a lot of unnecceserry fields

CONCLUSION: I'm using Magento since 2013 and I still cannot belive I cannot (as a merchant) properly set and sort fields without custom coding in templates. Its 2018 now (Shopify, Saas different world) but for Magento its still like in medieval. Hope somebody could make this UX fixes. Small things - a lot of improvement for day to day activities at admin area and for customers

[magento-engcom-team]

Hi @tomekjordan. 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 $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop). For more details, please, review the Magento Contributor Assistant documentation.

@tomekjordan 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 @engcom-backlog-nazar. 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: :point_down:

• [x] 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.

• [x] 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.

• [x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [x] 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!

• [x] 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

• [x] 6. Add label Issue: Confirmed once verification is complete.

• [x] 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96277, MAGETWO-96278 were created

[sdzhepa]

Hello @tomekjordan

According to the label "Feature Request" this ticket has been moved into "community-features"

Thank you for collaboration