Bug 2277957

Summary:	Search query box of remote execution job is very small as compared to the old satellite version.
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:	medium	Docs Contact:
Priority:	unspecified
Version:	6.14.3	CC:	aruzicka, rlavi
Target Milestone:	Unspecified	Keywords:	EasyFix, MigratedToJIRA, Regression, Triaged, UserExperience
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
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:35:55 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-04-30 10:27:23 UTC

Description of problem:

Job Search query box only 20 chars are visible. This is a big risk that the query you are typing or want to review is not fully visible.
In Sat6.11 the search query box was able to show 140 chars.
This major reduction makes it very complex to review and edit the query according to the end user.


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


How reproducible:

On your satellite WEB UI -> Monitor -> Jobs -> Run Job -> Select 'Job Category' and 'Job Template -> Next tab -> There is a filter 'Host' only visible -> Select 'Search query' from the dropdown -> The search box is very small as compared to the satellite version 6.11 and 6.12.

Comment 1 Ron Lavi 2024-05-02 14:22:13 UTC

*** Bug 2277956 has been marked as a duplicate of this bug. ***

Comment 2 Eric Helms 2024-06-06 17:35:55 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.