Bug 1439911 - methods not sorted in frame on right side in automate
Summary: methods not sorted in frame on right side in automate
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: GA
: 5.9.0
Assignee: Hilda Stastna
QA Contact: Dmitry Misharov
URL:
Whiteboard:
Depends On:
Blocks: 1441647 1441648
TreeView+ depends on / blocked
 
Reported: 2017-04-06 20:02 UTC by Jeffrey Cutter
Modified: 2018-06-01 12:56 UTC (History)
5 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1441647 1441648 (view as bug list)
Environment:
Last Closed: 2018-03-06 15:40:11 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
pic of methods frame not sorted (37.67 KB, image/png)
2017-04-06 20:02 UTC, Jeffrey Cutter
no flags Details

Description Jeffrey Cutter 2017-04-06 20:02:01 UTC
Created attachment 1269479 [details]
pic of methods frame not sorted

Description of problem:

In Automate Explorer, methods displayed in the right side frame under the Methods tab are not sorted.

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

5.7.1.3.20170221135006_818f133

How reproducible:

Every time.

Steps to Reproduce:
1.  In Automate Explorer, find a class with a number of methods with different names.
2.  Click the Methods tab on the right side.
3.  Note that methods are not sorted.

Actual results:

Methods are not sorted.

Expected results:

Methods are sorted, as they are on the left pane, and as instances are.

Additional info:

Pic attached.

Comment 3 Hilda Stastna 2017-04-11 14:46:34 UTC
fixing https://github.com/ManageIQ/manageiq-ui-classic/pull/1003

Comment 6 Milan Falešník 2017-11-03 10:26:32 UTC
I can see that in 5.9.0.5 that particular location looks exactly the same as on the screenshot on the PR.


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