Created attachment 1748890 [details] screenshot of 'create migration plan' form Created attachment 1748890 [details] screenshot of 'create migration plan' form Description of problem: ----------------------- The 'Create migration plan' dialog provides an option to create a new namespace in OCPv. A user could easily miss that option. See attached screenshot. In order to make it more obvious that a new namespace can be created by typing in the namespace text field while creating a migration plan in the UI,could the text be in bold and always be visible ? Other options to make it more obvious are also acceptable. Version-Release number of selected component (if applicable): ------------------------------------------------------------- MTV 2.0 Beta How reproducible: ----------------- Always Steps to Reproduce: ------------------ 1. 2. 3. Actual results: --------------- Expected results: ----------------- Additional info: -----------------
Will be fixed when https://github.com/konveyor/forklift-ui/pull/397 is merged (backport: https://github.com/konveyor/forklift-ui/pull/398) @nachandr can you take a look at the screenshots I added to this PR and tell me if that looks good and addresses the issue well enough? Also @apinnick let me know if that text "Type to search or to create a new namespace" sounds good to you.
Mike, I suggest this text: "Select or create a namespace." I think the behavior of this field makes the meaning obvious, so you can use a short and simple text. When the user clicks the Target Namespace field, a list of existing namespaces appears. When the user types text that does not match an existing namespace, the "Create ..." option appears.
That works for me. Do you agree @vconzola ?
Confirmed with Vince privately. Merged and backported.
Verified on MTV 2.0.0-beta.1.10
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 (Migration Toolkit for Virtualization (MTV) image release advisory 2.0.0-beta.1), 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/RHBA-2021:0615