Bug 800026

Summary:	Order of sub tabs changes in resource view
Product:	[Other] RHQ Project	Reporter:	John Sanda <jsanda>
Component:	Core UI	Assignee:	John Sanda <jsanda>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.3	CC:	hrupp
Target Milestone:	---
Target Release:	RHQ 4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-01 10:10:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	735475

Description John Sanda 2012-03-05 16:03:12 UTC

Description of problem:
This is basically the same problem as bug 781602. I am logging it separately though since different code is involved and each can be verified independently. The order of sub tabs in the resource view is not consistent. 

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


How reproducible:


Steps to Reproduce:
1. Import RHQ server into inventory.
2. Select the RHQ server in the resource tree.
3. Click on the monitoring tab. Note the order of the sub tabs.
4. Click on the Alert Subsystem child service.
5. Now click on the parent RHQ server again in the resource tree. The order of the monitoring sub tabs is different.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mike Foley 2012-03-05 16:45:28 UTC

per triage meeting (crouch, loleary, foley).  medium.  no target release.

Comment 2 John Sanda 2012-03-07 18:52:14 UTC

A fix has been committed to master. Although sub tabs are implemented differently than top-level tabs, the solution is basically the same.


commit hash: 1765784cd847ba3fe03761202c5d7f4a3ba9a169

Comment 3 Heiko W. Rupp 2013-09-01 10:10:05 UTC

Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.