Bug 1378053 - RFE: Import template conflict dialogue window - request for a few changes
Summary: RFE: Import template conflict dialogue window - request for a few changes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 4.0.4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Rob Young
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 12:15 UTC by Natalie Gavrielov
Modified: 2019-01-03 12:49 UTC (History)
2 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:43 UTC
oVirt Team: Virt
ngavrilo: planning_ack?
ngavrilo: devel_ack?
ngavrilo: testing_ack?


Attachments (Terms of Use)
snapshot of Import template conflict dialogue window (136.67 KB, image/png)
2016-09-21 12:15 UTC, Natalie Gavrielov
no flags Details

Description Natalie Gavrielov 2016-09-21 12:15:39 UTC
Created attachment 1203249 [details]
snapshot of Import template conflict dialogue window

Description:
Import template conflict dialogue needs some "touch-ups"
such as removing the strange "Don't import" radio button that behaves the same as cancel (since there is already a button to do just that).

Getting to "Import template conflict" dialogue:
1. Go to: webadmin -> Storage
2. Mark an export domain, and go to Template Import tab
3. Click import.
4. Click OK


A few things bother me when looking at this dialogue window:
1. The text alignment - too close to the border (comparing to other views)
2. Most important - "Don't import" radio button, is this a new way of cancelling the operation? why not click on the cancel button? (I personally think this button should be removed)
3. "Apply to all" checkbox should be aligned under "Clone" radio button

Comment 1 Michal Skrivanek 2016-09-22 04:49:01 UTC
We need to consider the future of export domain

Comment 2 Ryan Barry 2019-01-03 12:49:43 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.