Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • N nm.debian.org
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Debian New Member Process
  • nm.debian.org
  • Issues
  • #22
Closed
Open
Issue created Apr 27, 2020 by Enrico Zini@enricoOwner

Replace lookup_key with username

Person.lookup_key is an old hack to generate short and user-friendly slug-type identifiers for people on the site.

Unfortunately, its value does not map to anything in the database, and even depends on an external table (like the uid from LDAPInfo when present), making things harder for import/export procedures, and introducing non-standard lookups.

An alternative can be to set that value as Person.username (which would be a supported field in the Django user model), and possibly update it in a housekeeping procedure as the user information changes.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking