Bug 1271268

Summary: JobExecutor: sorting order according Id is ignored when different filters are selected
Product: [Retired] JBoss BPMS Platform 6 Reporter: Pavel Kralik <pkralik>
Component: Business CentralAssignee: Neus Miras <nmirasch>
Status: CLOSED NOTABUG QA Contact: Pavel Kralik <pkralik>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: kverlaen, pkralik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-24 10:19:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pavel Kralik 2015-10-13 13:53:08 UTC
Description of problem:
When sorting descending order according Id in the Queued tab is selected and then switched to the All tab, sorting order is lost. 

Version-Release number of selected component (if applicable):
BPMS 6.2.0.ER3

How reproducible:
Always

Steps to Reproduce:
1. Go to the Queued tab and select Id descending order.
2. Swicth to the All tab and see ascending Id order.


Actual results:
Sorting order differs filter to filter.

Expected results:
Sorting order should be the same in different tabs.

Additional info:

Comment 2 Kris Verlaenen 2015-10-13 15:30:47 UTC
Tbh, I would expect / prefer the sorting order to be independent in each tab.  While you might sort on one column in one direction on one filter, you could do something completely different on another one.

In some advanced filters (in process instance list for example) you even might end up with different columns being available in different filters, so not sure a strategy where you try to sort the same on different filter is even possible there?

Comment 3 Pavel Kralik 2015-11-24 10:19:26 UTC
Previous versions eg. 6.1 have this behaviour. Since 6.2 it is a feature. Closing bug.