Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1338866

Summary: Resolve ambiguity of the word "template" within the Job Template page.
Product: Red Hat Satellite Reporter: jcallaha
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: aruzicka, ehelms
Target Milestone: UnspecifiedKeywords: Triaged
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: 2018-06-18 14:07:36 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:
Attachments:
Description Flags
job template edit none

Description jcallaha 2016-05-23 14:20:54 UTC
Description of problem:
There are a number of uses of the word "template" within the Job Template page that can cause confusion to the user. 
The main pieces are called a "Job Templates" and the text within the template is also called a "Template". Additionally, the file you can upload to override the template text is called a "template".

Version-Release number of selected component (if applicable):
Satellite 6.2 Beta Snap 12.

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Hosts -> Job Templates
2. Navigate the forms on the page and determine is the use of "template" is made clear.

Comment 2 Adam Ruzicka 2018-06-18 13:58:30 UTC
Created attachment 1452650 [details]
job template edit

Comment 3 Adam Ruzicka 2018-06-18 14:07:36 UTC
It is hard for me to look at this from a new user's viewpoint, but I'm against this. I'd say the UI improved since 6.2beta snap 12 days so the rest of the comment is about the state in the coming release. 

In Satellite, template is usually "a thing that can be rendered and can be parametrized", and there are different kinds of templates (Partition Tables, Provisioning Templates, Job Templates).

Let's take a look at attachment in #2, taken from upstream (and how it will look in 6.4).

You go into Hosts > Job Templates and click on a job template's name, it takes you to the edit page for the selected job template. In the breadcrumbs bar you can see you're actually dealing with job templates and which one is currently opened. The first tab is called "Template", because there you can edit the actual "thing that can be rendered" (the same applies for the text input box). The next tab is called "Job" and over there you can configure job template specific things. The other tabs are shared among all the template kinds in Satellite.

I'm going to take the liberty of closing this as a WONTFIX. If you feel strongly about this, please feel free to reopen this BZ and we will try to figure out a solution.