Bug 1254981 - Child Channels not sorted when comparing Channels
Child Channels not sorted when comparing Channels
Status: CLOSED DEFERRED
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Usability (Show other bugs)
unspecified
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tomáš Kašpárek
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-19 07:30 EDT by Oliver Haessler
Modified: 2018-04-09 10:47 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-09 10:47:08 EDT
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 Oliver Haessler 2015-08-19 07:30:30 EDT
Description of problem:
When comparing 2 Channels the Child Channels are not sorted under the Parent Channel. This makes it hard to find a channel on a longer list.

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


How reproducible:
see steps below

Steps to Reproduce:
1. Click on "Channels - Manage Software Channels"
2. Select a Channel
3. Click on "Packages"
4. Click on "Compare"
5. look under "Compare to:) for the Channel to compare with

Actual results:
The Child Channels are unsorted

Expected results:
The Child Channels should be sorted

Additional info:
Comment 1 Tomas Lestach 2018-04-09 10:47:08 EDT
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.

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