Bug 1378138 - "Based on Template" field in Edit template dialogue does not supply the user with any useful information
Summary: "Based on Template" field in Edit template dialogue does not supply the user ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.0.4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 15:02 UTC by Natalie Gavrielov
Modified: 2022-06-27 07:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-03 12:49:49 UTC
oVirt Team: Virt
sbonazzo: ovirt-4.3-


Attachments (Terms of Use)
snapshot (144.03 KB, image/png)
2016-09-21 15:02 UTC, Natalie Gavrielov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46502 0 None None None 2022-06-27 07:22:08 UTC

Description Natalie Gavrielov 2016-09-21 15:02:51 UTC
Created attachment 1203348 [details]
snapshot

Description of problem:
Edit template dialogue shows a field: "Based on Template", it always shows the name of the template itself (it's not clear what kind of useful info is supplied to the user here)


Version-Release number of selected component:
rhevm-4.0.4.3-0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Go to: webadmin -> Templates tab
2. Mark a template, click "Edit"

Actual results:
There is a field displayed, "Based on Template", value is always the name of the template (and it's all greyed out - which is ok)

Expected results:
This field actually doesn't supply the user any useful information, it's just always the name of the template itself, so removing it will be a reasonable solution.

Additional info:
When trying to edit Blank template, this field is not displayed.

Comment 1 Michal Skrivanek 2017-08-22 07:37:45 UTC
didn't get to it in 4.1 nor in 4.2

Comment 2 Ryan Barry 2019-01-03 12:49:49 UTC
This will not be addressed in a reasonable timeframe. Please re-open if it's still important.


Note You need to log in before you can comment on or make changes to this bug.