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.

Sign up for GitHub

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

Jump to bottom

Merge customer name fields #1024

Closed
kassner opened this issue Feb 6, 2015 · 4 comments
Closed

Merge customer name fields #1024

kassner opened this issue Feb 6, 2015 · 4 comments
Labels
feature request Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@kassner
Copy link
Contributor

kassner commented Feb 6, 2015

Hi,

Can you guys think about merging all customer's name-related fields (prefix, firstname, middlename, lastname and suffix) into a single name field? I think this makes magento a more international product.

Motivational literature:
http://www.w3.org/International/questions/qa-personal-names
http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
http://blog.jgc.org/2010/06/your-last-name-contains-invalid.html

Thanks!
@joanhe joanhe added the CS label Feb 6, 2015
@ilol
Copy link

ilol commented Feb 9, 2015

Great idea, @kassner. I created the feature request with internal tracking number MAGETWO-33841. Please, reference to this id in further conversation.

@vpelipenko vpelipenko added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Feb 9, 2015
@vpelipenko
Copy link
Contributor

Also if you want to contribute suggested changes, your pull request is always welcome :-).

@ilol ilol removed the PROD label Feb 18, 2015
@vkorotun vkorotun removed the CS label Aug 4, 2016
@piotrekkaminski
Copy link
Contributor

Thank you for your submission.

We recently made some changes to the way we process GitHub submissions to more quickly identify and respond to core code issues.

Feature Requests and Improvements should now be submitted to the new Magento 2 Feature Requests and Improvements forum (see details here).

We are closing this GitHub ticket and have moved your request to the new forum.

magento-team pushed a commit that referenced this issue Apr 13, 2017
Merge pull request #1024 from magento-engcom/develop-prs
9224419 
Public Pull Requests:

#9221
#6772
#5367
#9210
#7506
#6385
#9084
#9103
#5742
#5043
#6443
#9165
#9131
#9112
#9062
#8824
#6910
#7900
#7464
#8462
#9215
magento-team pushed a commit that referenced this issue Dec 14, 2017
MAGETWO-85637: [Backport] #10743: Magento 2 is not showing Popular Se…
41e33fd 
…arch Terms #1024

 - Merge Pull Request magento-engcom/magento2ce#1024 from p-bystritsky/magento2:ISSUE-10734
 - Merged commits:
   1. 1f77aaa
   2. e340347
   3. 43ede3c
magento-team pushed a commit that referenced this issue Dec 14, 2017
MAGETWO-85637: [Backport] #10743: Magento 2 is not showing Popular Se…
ea58fee 
…arch Terms #1024
@gety9
Copy link

gety9 commented Jan 10, 2018

So right now Magento 2 has Full Name instead of Separate First and Last Names?

@gety9 gety9 unassigned ilol Jan 10, 2018
@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Jan 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@kassner @piotrekkaminski @vpelipenko @ilol @vkorotun @joanhe @gety9 @magento-engcom-team