Use autocomplete_fields in list_filter for related models

[Paul Tiplady]

In Django 2.0, support for select2 AJAX autocomplete fields was added:

​https://github.com/django/django/pull/6385
https://code.djangoproject.com/ticket/14370

This makes foreign key fields much more usable in the Admin, as the full list of objects doesn't need to be loaded to populate a dropdown list (as was the old way of doing this).

This issue covers using the new vendored select2 widgets to provide similar autocomplete functionality for the list_filter UI (specifically, presumably extending/replacing RelatedFieldListFilter).

Some discussion in the Github PR 6385 suggesting that the next step would be to open an issue to track this work.

[Phil Krylov]

There is a third-party app dealing with this, although it could be improved a bit: ​https://github.com/farhan0581/django-admin-autocomplete-filter

[David]

There is an updated third party app which does this ​https://github.com/vigo/django-admin-list-filter

[Hemnath P]

Hi, I'd like to work on this ticket. Before starting, I noticed there's a maintained third-party package that already implements this: ​https://github.com/vigo/django-admin-list-filter — it adds select2/AJAX autocomplete support to list_filter using Django's built-in AutocompleteJsonView, following a similar approach to what's described here.
Given that package exists and appears to work well, is there still interest in having this in Django core, or would the recommendation be to point users to that package instead? I'm happy to attempt a patch if the team feels it's still worth including in core

[Md. Saikat Islam]

Are you working on it?
Replying to Hemnath P:

Hi, I'd like to work on this ticket. Before starting, I noticed there's a maintained third-party package that already implements this: ​https://github.com/vigo/django-admin-list-filter — it adds select2/AJAX autocomplete support to list_filter using Django's built-in AutocompleteJsonView, following a similar approach to what's described here.
Given that package exists and appears to work well, is there still interest in having this in Django core, or would the recommendation be to point users to that package instead? I'm happy to attempt a patch if the team feels it's still worth including in core