This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2290367 - 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
Summary: As compared to the old legacy UI the select option and modify options are ver...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-06-04 12:35 UTC by Susmita Sen
Modified: 2024-06-06 17:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:40:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-25569 0 None Migrated None 2024-06-06 17:40:36 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.