An issue with the sort order behaviour of the Suspect Metrics Report's "Metric" column caused the sorting icon to indicate a sort order change but the UI would not display the records correctly. For large record results (over 1000), if the user scrolled to the end of list and then scrolled to the start of the list, the sort order began to work correctly until the user left the page. The fix changes the report behaviour to allow server-side sorting on the Resource, Metric, Date/Time and Outlier fields which improves performance. The remaining fields are not sortable server-side and have client-side sorting only allowed (they are sortable after all the data has been loaded to the client).
+++ This bug was initially created as a clone of Bug #1113707 +++
Description of problem:
If you click on title to sort it and scroll to the end of list and scroll to the up again it starts working till you leave page. There are over 1000 records, if there are only a few then it works as expected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from Michael Burman on 2014-07-07 15:19:02 EDT ---
Changed the behaviour to allow server-side sorting on the Resource, Metric, Date/Time and Outlier fields. Rest of the fields are not sortable server-side and have client side sorting only allowed (they will be sortable after all the data has been loaded to the client).
Fixed in master commit 3fa0ecb.
looks like this already made it to the branch:
git cherry-pick -x 3fa0ecb
# On branch release/jon3.3.x
nothing to commit (working directory clean)
The previous cherry-pick is now empty, possibly due to conflict resolution.
Moving to ON_QA as available to test in the following brew build: