Bug 970757 - Environment dropdowns should display environment/environment content from paths in a congruent manner
Summary: Environment dropdowns should display environment/environment content from pat...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-04 19:19 UTC by Corey Welton
Modified: 2014-06-19 19:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-04 17:13:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Corey Welton 2013-06-04 19:19:16 UTC
Description of problem:
Presently, if a user has a promotion path of multiple environments (dev > qe > stage > prod), s/he is used to seeing these in a given order in the katello UI.  However, when creating a New Host Group in foreman, these show up in an alphanumeric order.

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


How reproducible:


Steps to Reproduce:
1.  Create a promotion path in katello: dev > qe > stage > prod
2.  Begin creation of a new Host Group in foreman
3.  Observe ordering of environments

Actual results:
results show up in alphanumeric order

 dev
 prod
 qe
 stage

Expected results:
results should show up in a manner consistent with users' expectations per the katello UI
 
 dev 
 qe
 stage
 prod

Additional info:
per bug #970753, i suppose it is possible that raw environments could disappear from the dropdown completely.  however, assuming there will be some method to discern which CVD exists in an org, we should still be listing things in a manner consistent with what the user is used to seeing.

Comment 4 Bryan Kearney 2014-06-04 17:13:06 UTC
Per discussions with QE, Closing this.


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