#9467: Keep search paramenters and filters when editing or saving an entity
---------------------------------------------------------------+------------
 Reporter:  jacmkno                                            |       Owner:  
nobody    
   Status:  new                                                |   Milestone:  
post-1.0  
Component:  django.contrib.admin                               |     Version:  
1.0       
 Keywords:  filters admin add edit keep search listing entity  |       Stage:  
Unreviewed
Has_patch:  0                                                  |  
---------------------------------------------------------------+------------
 If you edit or add an entity using the admin tool from one of the entity
 listing pages with some filters applied, when you click the save button,
 you should be taken back to the same listing with the same filters
 applied. The fields of the Add Form should be pre-filled with the values
 taken from the filters applied on the listing.

 Here is an example situation: You have two models: books and libraries.
 Let's say that you are looking for a book that you know to be in a library
 called "Big Library" in the admin application. In the book listing you
 have a filter by library, so you click "Big Library" link in the filter
 tool bar. Currently if you edit a book of that list and click the save
 button, you are taken back to the listing with no filters applied, so the
 user gets lost.
 The expected behavior here is to be taken back to the listing with the
 same filters applied.
 Another expected behavior is that if you are in the same book listing
 filtered by the "Big Library", and you click the "add book" link at the
 top. You would expect that the book you are adding will be located at the
 "Big Library", so the fields inside the Add Form should be pre-filled
 using the matching information found in the filters applied to the
 listing.

 I fixed these issues for the 0.95 version but I want to have some feedback
 from the community before proposing an specific change.

 I think this issues are very important because the current behavior makes
 admin usage very confusing for new users.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/9467>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to