[Django] #36706: Select all but one in admin

3 views
Skip to first unread message

Django

unread,
Nov 3, 2025, 9:51:49 AM11/3/25
to django-...@googlegroups.com
#36706: Select all but one in admin
-------------------------------+-----------------------------------------
Reporter: Julien Palard | Type: New feature
Status: new | Component: contrib.admin
Version: 4.2 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------+-----------------------------------------
Currently the "Select all {{ total_count }} {{ module_name }}" link (which
"selects" all objects across all the pages) is only a boolean if I
undertand correctly (acrossInput.value = 1; in actions.js).

It would be nice if after selecting all records from all pages one could
still navigate the pages AND unselect some records.

Currently navigating the pages, or clicking any selection checkbox, undoes
the "select all [...]".

So, say I have 402 users, so 4 pages, if I hit "Select all 402 users" I
see "All 402 users selected", I now I uncheck a single one I'm back at "99
/100 selected users", I'd prefer "401/402 selected users".
--
Ticket URL: <https://code.djangoproject.com/ticket/36706>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Nov 3, 2025, 10:16:22 AM11/3/25
to django-...@googlegroups.com
#36706: Select all but one in admin
-------------------------------+--------------------------------------
Reporter: Julien Palard | Owner: (none)
Type: New feature | Status: closed
Component: contrib.admin | Version: 4.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------+--------------------------------------
Changes (by Natalia Bidart):

* resolution: => wontfix
* status: new => closed

Comment:

Thank you for your suggestion! When suggesting a new feature for Django,
the feature idea should first be proposed and discussed with the
community. To do that, please raise this on the [https://github.com/django
/new-features/issues ​new feature tracker].

I'll close the ticket for now, but if the community agrees with the
proposal, please return to this ticket and reference the forum discussion
so we can re-open it. For more information, please refer to
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features the documented guidelines for requesting
features].
--
Ticket URL: <https://code.djangoproject.com/ticket/36706#comment:1>
Reply all
Reply to author
Forward
0 new messages