Skip to content
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

Merged
merged 1 commit into from
Jun 27, 2017

Conversation

PascalBrouwers
Copy link
Contributor

@PascalBrouwers PascalBrouwers commented May 18, 2017

Description

Use parent name for variations when creating configurables

Fixed Issues (if relevant)

  1. Adding product configurations uses sku based name #9680: Adding product configurations uses sku based name

Manual testing scenarios

  1. Create a configurable product with some configurations (simple products)
  2. Use name 'NAME'
  3. Use sku 'SKU'
  4. Create configurations and Generate products
  5. Confirm that name of the configurations (simple products) are based on the name of the parent product

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

@miguelbalparda miguelbalparda self-assigned this May 18, 2017
@miguelbalparda miguelbalparda added this to the May 2017 milestone May 18, 2017
@miguelbalparda
Copy link
Contributor

Hi @PascalBrouwers! Thanks for your contribution!
I have checked #9680 and it seems it might not be a bug entirely, but I still believe this might be interesting to merge. Would you mind adding some more info on why this should be included instead of the SKU variation of the product name? Thanks again!

@PascalBrouwers
Copy link
Contributor Author

I see what you mean. Using the sku could also be intended behaviour.
But to me it's a bug because I would expect the simples to use the parent name. For merchants it is very confusing to see the simples in the product overview based on sku and would rather see it based on name. If this PR could be merged it would help Magento to be a better product.

@PieterCappelle
Copy link
Contributor

I agree with @PascalBrouwers.

@iancassidyweb
Copy link
Contributor

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 :-)

@miguelbalparda
Copy link
Contributor

This is breaking some tests, @vrann what are the next steps?

@okorshenko okorshenko modified the milestones: May 2017, June 2017 Jun 1, 2017
@okorshenko okorshenko self-assigned this Jun 23, 2017
@miguelbalparda
Copy link
Contributor

miguelbalparda commented Jun 26, 2017

This is being worked on as we speak, sorry for the late reply!

@magento-team magento-team merged commit c198a1f into magento:develop Jun 27, 2017
@paales paales added the Partner: Reach Digital Pull Request is created by partner Reach Digital label May 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Partner: Reach Digital Pull Request is created by partner Reach Digital
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants