Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • concrexit concrexit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • thaliathalia
  • concrexitconcrexit
  • Issues
  • #653
Closed
Open
Issue created Jul 02, 2018 by Gijs Hendriksen@ghendriksenContributor

Ordering for event registrations in backend is lexicographically, not chronological

One-sentence description

Ordering in the events backend should be chronological when sorting based on a datetime field.

Current behaviour

When ordering on the "Registration start" field, for example, the registrations are sorted lexicographically, as can be seen in this screenshot:

registration_ordering

Expected behaviour

When ordering on a datetime field, the registrations should be ordered chronologically.

Steps to reproduce

  1. Create registrations for June 2nd and July 1st for a certain event.
  2. Go to the admin page for that specific event.
  3. Notice that the registration in July is shown before the registration in June.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking