Context Navigation

Changes between Initial Version and Version 1 of Ticket #17522, comment 9

-              initial
+              v1
+>
 Because the `ordering` tuple purpose is to specify the **default** ordering that the user can change afterwards by clicking on column headers. If I'm forced to embed the ordering in the `get_queryset()` method, then:
 ) I am forced to implement a get_queryset in situations where I don't need to do it, because defining additional columns via properties with `get_` methods works fine and it's convenient and consistent with `list_display`
 ) The user can't change the ordering afterwards, or I need to put logic inside `get_queryset()` to include the sorting or not depending on what the user does.
 The funny thing is that everything works as expected, if you can work around the too strict (in my opinion) validation.