Bug 1505932

Summary:	[RFE] Show "Static Query" in Job invocations overview
Product:	Red Hat Satellite	Reporter:	Beat Rubischon <brubisch>
Component:	Remote Execution	Assignee:	Aditi Puntambekar <apuntamb>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.12	CC:	apuntamb, aruzicka, inecas, peter.vreman
Target Milestone:	6.6.0	Keywords:	FutureFeature, PrioBumpPM
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_remote_execution-1.6.6-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 12:46:42 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:
Bug Depends On:
Bug Blocks:	1122832

Description Beat Rubischon 2017-10-24 15:08:49 UTC

Description of problem:

Running the same job against different targets results in a confusing overview page. Adding the "Static Query" would give at least a hint of the targets of historic jobs.

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

Satellite 6.2.12

How reproducible:

always

Steps to Reproduce:
1. Run a job against "name = hosta"
2. Run a job against "name = hostb"

Actual results:

Both jobs look identical on the "Job invocations" list https://satellite/job_invocations

Expected results:

Additional column shows target of the jobs.

Additional info:

Comment 4 Adam Ruzicka 2017-11-08 08:54:21 UTC

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

Comment 5 Peter Vreman 2019-05-20 10:33:27 UTC

Confirmed this is fixed in already in 6.5 
Sat6.5.0 has tfm-rubygem-foreman_remote_execution-1.6.7-19.el7sat.noarch

Comment 6 Peter Ondrejka 2019-06-17 14:27:22 UTC

Verified in Satellite 6.6 snap 8, search query is now displayed in job invocations overview

Comment 9 errata-xmlrpc 2019-10-22 12:46:42 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-2019:3172