Allow ordering of models in the admin index #12699
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR allows to display the models in a specific order per app on the admin index and the app index, using a new
order_in_index
option onModelAdmin
.When left to default (None), the models are sorted alphabetically (backwards compatible).
This helps deal with a common case where there is some logical order between models that does not match alphabetical order (e.g.
Continents, Countries, Counties, Cities
is much more usable thanCities, Continents, Counties, Countries
). There is no easy way to achieve this, except by prepending verbose_name with spaces, which is not very elegant.