Bug 1498588

Summary:	[RFE] settings page should show when non-default settings are selected
Product:	Red Hat Satellite	Reporter:	Chris Duryee <cduryee>
Component:	Settings	Assignee:	Swapnil Abnave <sabnave>
Status:	CLOSED ERRATA	QA Contact:	Perry Gagne <pgagne>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.12	CC:	mhulan, pgagne, sgraessl, tbrisker
Target Milestone:	6.4.0	Keywords:	FieldEngineering, FutureFeature, Triaged, UserExperience
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:	2018-10-16 15:28:43 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 Chris Duryee 2017-10-04 16:59:43 UTC

Description of problem:

It is difficult for a user to tell if they've selected non-default settings in Satellite on the Settings page. This can lead to issues if they've set an option to something other than the default, and then start experiencing issues but are unsure of what change was made.

I am not sure of the best way to represent that a setting was changed, perhaps by showing "(default: X)" on non-default options, or by making non-defaults bold perhaps.

Version-Release number of selected component (if applicable): 6.2.12, but also 6.3.0 snap 18

Comment 2 Marek Hulan 2017-10-09 07:53:14 UTC

Created redmine issue http://projects.theforeman.org/issues/21238 from this bug

Comment 3 Satellite Program 2017-12-04 11:22:45 UTC

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

Comment 9 Satellite Program 2018-09-06 14:07:33 UTC

Upstream bug assigned to sabnave

Comment 12 errata-xmlrpc 2018-10-16 15:28:43 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927