Bug 2230442

Summary:	Unable to view Categories and Templates in Run Job form But Legacy Form Still works in Satellite 6.13
Product:	Red Hat Satellite	Reporter:	Omkar <onerleka>
Component:	Users & Roles	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.13.1	CC:	aruzicka, mhulan, oezr
Target Milestone:	Unspecified
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:	2023-08-09 13:14:45 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 Omkar 2023-08-09 12:51:03 UTC

Description of problem:

Scheduling Job for Content host from Host -> All Hosts does not list "Job Category" & "Job Template" for the users assigned to specific roles (See attached screenshot). But using Legacy Form user can list the "Job Category" & "Job Template"

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

6.13.1

How reproducible:

Easily Reproducible

Steps to Reproduce:

1. Log in to Satellite 6.13.1
2. Create an Internal user (Testuser)
3. Create User Roles & add filters as per attached screenshot
4. Assign the created role to the user (Testuser).
5. Login with (Testuser) then go to Hosts -> All Hosts -> Click any host --> Click on "Schedule A Job" 


Actual results:

Not able to list "Job Category" & "Job Template" But When switching to Legacy Form User can list "Job Category" & "Job Template"


Expected results:

New Job Wizard should list "Job Category" & "Job Template"

Additional info:

Comment 2 Adam Ruzicka 2023-08-09 13:14:45 UTC

This should be a duplicate of BZ2220965 . If there's something I missed and the two bugs are actually different, feel free to reopen.

*** This bug has been marked as a duplicate of bug 2220965 ***