Bug 2290367

Summary:	As compared to the old legacy UI the select option and modify options are very lengthy and inconvenient on the new WEB UI of satellite 6
Product:	Red Hat Satellite	Reporter:	Susmita Sen <sussen>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.14.0	CC:	aruzicka
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA
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 17:40:38 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 Susmita Sen 2024-06-04 12:35:46 UTC

Description of problem:

When the end user reruns the remote execution task on the new WEB UI, the end-user has a lengthy search query to modify so the select options are very inconvenient as compared to the old legacy UI. 

Like needs to select the options from the dropdown like Hosts, Hostgroups, and Search quesry which are difficult to understand and very inconvenient. 

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

Satellite 6.12+

How reproducible:

Steps to Reproduce:
1. On your satellite WEB UI -> Hosts -> All Hosts -> Schedule Remote Job -> Job category - Commands/Ansible Playbook/Puppet -> Job template - Run Command - Script Default/Ansible Roles - Ansible Default/Puppet Run Once - Script Default -> Next

2. On the 2nd page you can select a hostgroup or collection or search query you put a command/Custom puppet facts -> next -> Next Sumit

3. But when you re-run the task for another host group/host you want to run 'custom (puppet) facts in the search queries that select the hosts dynamic and those queries are 50-100 chars long.' which is very difficult to modify and very inconvenient according to the end user.


Actual results:

It is very inconvenient according to the end user.

Expected results:

The select options should be as simple as old legacy Ui

Additional info:

The end user is aware of the legacy UI but for future improvement to the new UI.

Comment 1 Eric Helms 2024-06-06 17:40:38 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.