-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue 9680: Use parent name for variations #9681
Conversation
Hi @PascalBrouwers! Thanks for your contribution! |
I see what you mean. Using the sku could also be intended behaviour. |
I agree with @PascalBrouwers. |
Agree with the @PascalBrouwers. To me it makes more sense for Merchants to work with names and not SKU's. Having worked merchant side for an organisation with multiple admin users across several business units it's common place for employees to know the product ranges and names as they deal with these on a daily basis however it's not as common for employees to naturally know the SKU's for products unless they were involved in a more warehousing / logistics / purchasing role. However that's just my two cents :-) |
This is breaking some tests, @vrann what are the next steps? |
This is being worked on as we speak, sorry for the late reply! |
Description
Use parent name for variations when creating configurables
Fixed Issues (if relevant)
Manual testing scenarios
Contribution checklist