Bug 1716439

Summary:	[RFE] Sort/Order Component Content Views and Versions in Composite Content View Menu on WebUI
Product:	Red Hat Satellite	Reporter:	patalber
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Lai <ltran>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.5.0	CC:	bkearney, riehecky
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-09 16:56:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.