Bug 2180536

Summary:	[RFE] Content view dropdown should be visible but disabled until you select an environment
Product:	Red Hat Satellite	Reporter:	Jeremy Lenz <jlenz>
Component:	Content Views	Assignee:	Jeremy Lenz <jlenz>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.13.0	Keywords:	FutureFeature, MigratedToJIRA, WorkAround
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:11:22 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:

Description Jeremy Lenz 2023-03-21 17:27:35 UTC

The design of the new environment / CV selector can be confusing because the content view dropdown is invisible until you select an environment. See https://community.theforeman.org/t/new-host-ui-doesnt-allow-me-to-change-the-current-content-view/32113 

Instead, the CV dropdown should be visible but disabled.

Comment 1 Jeremy Lenz 2023-03-21 17:27:39 UTC

Created from redmine issue https://projects.theforeman.org/issues/36184

Comment 2 Jeremy Lenz 2023-03-21 17:27:40 UTC

Upstream bug assigned to jlenz

Comment 6 Bryan Kearney 2023-03-22 16:03:24 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36184 has been resolved.

Comment 7 Bryan Kearney 2023-03-22 16:03:42 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36184 has been resolved.

Comment 8 Eric Helms 2024-06-06 16:11:22 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.