Filter does not work properly with paginated project list

Bug #1279587 reported by Vahid Hashemian
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released

Bug Description

When the project list (Admin > Projects) is paginated the filter box causes only the list in the current page to be filtered. So if a project one is looking for does not exist in the current page filter does not return any results. This can be confusing.

In my opinion, a benefit that such filter should provide is to find a project when thousands of projects are available. no matter on what result page that project is located.

To replicate:
1. Create about 20 projects (use command line for convenience: "keystone --os-username admin --os-password **** --os-auth-url http://localhost:5000/v2.0 --os-tenant-name admin tenant-create --name=proj01")
2. Login to Horizon and go to Admin > Projects
3. The list should be paginated with a default 20 projects in each page
4. Filter and type in a project name that is not in the current page list. It would not return the project you're looking for even though it's listed in the other page.

Revision history for this message
Justin Pomeroy (jpomero) wrote :

I agree this is something that is needed in general across all (or most) tables. This behavior was recently added to the admin instances table and it seems to me other tables should be updated to use it.

Revision history for this message
Vahid Hashemian (vahidhashemian) wrote :

Thank you Justin for the clarification.
Yes, I agree that the scope is beyond just the Projects table.
I suspect this bug applies to all tables that support both pagination and filtering.

Revision history for this message
David Lyle (david-lyle) wrote : addressed the particular issue, addressing the same problems in more tables should either be separate bugs or better yet a new blueprint that denotes where server side filtering could be used.

Changed in horizon:
status: New → Fix Committed
importance: Undecided → Medium
Revision history for this message
Vahid Hashemian (vahidhashemian) wrote :

Hi David,

I don't think the blueprint you mentioned and the code committed (which is already merged) addresses this issue. It appears to me that filters work only on the current page of data (projects in this case). So if the project I'm looking for is in another page, when I use the filter to look for it it comes back with an empty list.

Am I missing something?

Revision history for this message
Justin Pomeroy (jpomero) wrote :

Vahid, you are right. The code change I mentioned above does not address the issue of filtering across pages as I had thought. That change seems only to move the filtering from the browser onto the server. I am thinking about a blueprint that would fix this issue.

Thierry Carrez (ttx)
Changed in horizon:
milestone: none → icehouse-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in horizon:
milestone: icehouse-3 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.