Bug 2255985

Summary: [RFE] Need "Reset to defaults" option for manage columns in "All Hosts"
Product: Red Hat Satellite Reporter: afrid shaikh <shmohamm>
Component: Host FormAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.15.0CC: ahumbe, dsinglet, nalfassi, rlavi
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA, Triaged
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:39:49 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:
Attachments:
Description Flags
PFA none

Description afrid shaikh 2023-12-27 14:32:15 UTC
Created attachment 2006093 [details]
PFA

Description of problem:
Need "Reset to defaults" option for "manage columns" in "All Hosts"

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

6.15.0

How reproducible:
100%

Steps to Reproduce:
1. Select most of the columns from Satellite WEB-UI --> Hosts --> "All host" --> "Manage column".

Actual results:
1. If we select all the applicable options in the managing column then it collides the host details in the host list which makes it difficult for the end user to read the host details. Also, it would be easy to revert changes made with the "restore to defaults" option.

Expected results:

If we have the "restore to default" option in the "manage column" then it will be easy to revert the changes and to list the default columns in Satellite WEB-UI --> Hosts --> "All host" 

Additional info:

Comment 1 Eric Helms 2024-06-06 16:39:49 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.