Bug 1119793 - [RFE] - Support sorting on multiple columns
Summary: [RFE] - Support sorting on multiple columns
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: ---
Hardware: Unspecified
OS: Unspecified
high vote
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Lukas Svaty
Depends On: 1128842
TreeView+ depends on / blocked
Reported: 2014-07-15 14:07 UTC by Pavel Stehlik
Modified: 2020-03-12 10:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1128842 (view as bug list)
Last Closed: 2020-03-12 10:28:29 UTC
oVirt Team: UX
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

Description Pavel Stehlik 2014-07-15 14:07:34 UTC
Description of problem:
 Once we'll have sorting on columns, would be also nice to implement sorting over more of them at once. I can imagine to hold Ctrl + click on another column as adding it to filter. 
Also please consider de-select (repetitive Ctrl+click?) - will remove that column sort. Also would be nice support more than just 2 collumns, what about 3 or 4 columns? (or even all of them!)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Einav Cohen 2014-08-11 15:45:32 UTC
at least for grids that rely on server-side sorting (i.e. most of the main grids), we need support for sorting on multiple fields in the search mechanism -> opened (infra) blocking bug 1128842.

Comment 2 Yaniv Lavi 2015-04-07 08:26:42 UTC
There is no way to do this client side once the initial result set is displayed?

Comment 3 Einav Cohen 2015-04-07 15:59:13 UTC
(In reply to Yaniv Dary from comment #2)
> There is no way to do this client side once the initial result set is
> displayed?

sorting on main grids is done on the server side. it must be done on the server side because of the paging. 

a sorting performed client side can be performed only on the results of the current page (100 by default) which doesn't take into consideration the full set of objects in the system, hence produces misleading results. 

if you want to do the primary sorting on the server-side and the secondary sorting on the client-side - I assume that we can do that, but it may be extremely confusing to the user to have the primary sorting done on all items in the system and the secondary sorting done per page - so I recommend to not go in this path.

Comment 4 Sharon Gratch 2020-03-12 10:28:29 UTC
Unlikely to be fixed. Please re-open if you think it should be handled.

Note You need to log in before you can comment on or make changes to this bug.