[Django] #29811: Admin: Extend the Object History to Table History

10 views
Skip to first unread message

Django

unread,
Oct 1, 2018, 10:12:53 AM10/1/18
to django-...@googlegroups.com
#29811: Admin: Extend the Object History to Table History
-----------------------------------------+------------------------
Reporter: Vlada Macek | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
Sometimes I'd like to see LogEntries for entire table or for objects
matching the current changelist filter.

What do you think about the idea of "History" button being available in
changelist too?

I guess the history view would need a pagination added + the new column
describing the object (linkable too).

Thanks.

--
Ticket URL: <https://code.djangoproject.com/ticket/29811>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Oct 1, 2018, 10:55:54 AM10/1/18
to django-...@googlegroups.com
#29811: Admin: Extend the Object History to Table History
-------------------------------+--------------------------------------

Reporter: Vlada Macek | Owner: nobody
Type: New feature | Status: closed
Component: contrib.admin | Version: master
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: 0
-------------------------------+--------------------------------------
Changes (by Tim Graham):

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


Comment:

I think it could be done (at least initially) as a a third-party package.
If it becomes popular, then you could write to the DevelopersMailingList
about including it in Django.

--
Ticket URL: <https://code.djangoproject.com/ticket/29811#comment:1>

Reply all
Reply to author
Forward
0 new messages