Code

Opened 7 years ago

Closed 7 years ago

#6311 closed (duplicate)

"First name" and "Last name" in user model is too bad

Reported by: Alexandre <amartani@…> Owned by: nobody
Component: Internationalization Version: master
Severity: Keywords: first last name user model
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

The user model has fields for "first name" and "last name". In many non-English speaking countries, people are not named this way, which can lead to several problems.
See: http://rishida.net/blog/?p=100

Attachments (0)

Change History (3)

comment:1 Changed 7 years ago by semenov

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

Agreed, a framework which is designed to be internationalizable shouldn't rely on Western first/last name schema. That's a legacy shortseeing, like not using unicode in the initial django releases.

If anyone actually needs the formal person data, he might use 1:1 relation with some Person model (and put there First, Last, Title, Position, Date of Birth and other fields which shouldn't be in the "generic" User model).

comment:2 Changed 7 years ago by ramiro

See #5638

comment:3 Changed 7 years ago by Collin Grady <cgrady@…>

  • Resolution set to duplicate
  • Status changed from new to closed

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.