Bug 1271268 - JobExecutor: sorting order according Id is ignored when different filters are selected
JobExecutor: sorting order according Id is ignored when different filters are...
Status: CLOSED NOTABUG
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: Business Central (Show other bugs)
6.2.0
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Neus Miras
Pavel Kralik
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-13 09:53 EDT by Pavel Kralik
Modified: 2015-11-24 05:19 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-24 05:19:26 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pavel Kralik 2015-10-13 09:53:08 EDT
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 11:30:47 EDT
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 05:19:26 EST
Previous versions eg. 6.1 have this behaviour. Since 6.2 it is a feature. Closing bug.

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