Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1716439 - [RFE] Sort/Order Component Content Views and Versions in Composite Content View Menu on WebUI
Summary: [RFE] Sort/Order Component Content Views and Versions in Composite Content Vi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.5.0
Hardware: All
OS: All
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-03 14:05 UTC by patalber
Modified: 2024-10-01 16:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-09 16:56:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description patalber 2019-06-03 14:05:50 UTC 
Description of problem:
Per client:
"When selecting a version of a component content view for a composite content view, having these sorted (highest number first) would simplify the selection process.  Currently, the results are unsorted."

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

How reproducible:
100%

Steps to Reproduce:
1. Create a composite content view made up of content views with multiple versions
2. Change the version via the drop-down menu
3. Note that the results are unsorted

Actual results:
Unsorted list of version numbers

Expected results:
Sorted version

Additional info:
Comment 3 patalber 2019-06-03 14:18:41 UTC 
Another request in a similar vein (and thus included in this RFE):

"Business Case:

The component views of a composite content view are sorted by the version ID of the component view.  For simplicity, they should be sorted by content view name.

Currently, the results are unsorted.

Technical requirements:
Sort content views alphabetically by name."

Please take this into account as well as the original request.

Thank you.
Comment 4 Mike McCune 2021-06-08 21:14:31 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 5 Mike McCune 2021-07-09 16:56:30 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
Note You need to log in before you can comment on or make changes to this bug.