Opened 9 years ago

Last modified 9 years ago

#16465 new New feature

Admin history view should also show history of super-object(s)

Reported by: Gertjan van Oosten Owned by: nobody
Component: contrib.admin Version: 1.3
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: yes


It would be nice if the admin history view for an object would also show the history of its super-object(s) (if your model uses inheritance).
A small and simple patch is attached.

Attachments (1)

admin-history_view.patch (1.1 KB) - added by Gertjan van Oosten 9 years ago.

Download all attachments as: .zip

Change History (4)

Changed 9 years ago by Gertjan van Oosten

Attachment: admin-history_view.patch added

comment:1 Changed 9 years ago by Julien Phalip

Patch needs improvement: set
Triage Stage: UnreviewedDesign decision needed
UI/UX: set

I'm not a fan of the approach in the attached patch, but I think that the general idea is worth considering. Similarly, it could be considered that the changes made in the child model which are relevant to the parent model would be displayed in the parent model's history. Some design discussion needs to take place around what the user's expectations would be, if it'd be worth improving the interface to highlight the changes made via a different model, etc.

comment:2 Changed 9 years ago by Gertjan van Oosten

Agreed on most of your comments. Like I said: the patch is small and simple. :-)
Also, it fits the only real-world use case I have for this, which is editing of the lowest level of subclass in the hierarchy (everything above is disabled). So quite possibly some more input is needed to see if there are other use cases and the approach needs to be generalised.

Last edited 9 years ago by Gertjan van Oosten (previous) (diff)

comment:3 Changed 9 years ago by Jacob

Triage Stage: Design decision neededAccepted

The UI here is actually the big problem, I think: how do you represent the concept of a "parent" object in a way that makes sense to the *users* of the admin? Nevertheless, this is a good idea which improves the overall usability of the admin. So if we can figure out how to successfully present the information let's do it.

Note: See TracTickets for help on using tickets.
Back to Top